Membership software adapted to your association.
When Core and standard add-ons are not enough, association-specific extensions can handle custom rules, digital-card logic, approval flows or supported integrations — without creating a separate fork of Aurora.
What can be customised?
Membership rules
Age-based groups, role-specific logic, organisation statuses, eligibility and internal classifications.
Digital card logic
Card templates and data that differ by age, role, member category or other approved attributes.
Internal workflows
Special approvals, reminders, registration steps, internal processes and automation not part of public Core.
Integrations
Connections to third-party services or internal systems where a standard add-on is not enough.
A tailored extension, not a fork.
Aurora Core remains the common foundation. Reusable features can stay generic while your association’s own configuration remains in its extension. This supports safer Core updates and clearer maintenance.
For example: a junior-member digital card and an adult card can share a generic mapping engine while retaining separate age thresholds and templates.
How the work proceeds
- Discovery: define requirements and expected results.
- Architecture: separate reusable features from association-specific logic.
- Development and testing: verify the agreed workflow.
- Go-live: deploy and maintain supported integrations within the agreed scope.
Transparent starting prices.
Association Extension
Licence, updates and compatibility maintenance from €149/year within the agreed scope.
Best for targeted membership rules, card logic and smaller organisation-specific features.
Advanced Integration
Maintenance from €299/year, with pricing confirmed after a short technical review.
Best for data exchange, broader custom logic and more complex supported services.
Standard add-on licences, third-party services and external subscriptions are separate unless a quotation explicitly includes them. Managed Setup is a distinct onboarding service and does not include custom development.
Frequently asked questions.
Does an extension replace Core?
No. Core remains the foundation and is maintained independently.
Will we need other Aurora add-ons?
Only when the requested feature depends on them. Any required Pro, Commerce or Digital Cards licence is separate unless included in the quotation.
Can a custom function later become a public feature?
Yes, where it makes sense, a reusable capability may become part of the general engine while keeping private rules and mappings separate.
Are new features covered by the annual maintenance fee?
Not automatically. Maintenance covers the agreed licence, updates and compatibility scope. Major additional development is quoted separately.
Can the extension use our association name?
With permission, a dedicated plugin can be presented as an Aurora extension for your organisation. Organisation names and trademarks are used only with authorisation.