Ágora
Member directory, dues, chapters and events in one platform — on a codebase you own, instead of Wild Apricot's per-contact subscription.
Ágora is a community operating system for member organizations — professional associations, alumni networks, NGOs, chambers of commerce and clubs.
Renewals arrive on time without anyone chasing a spreadsheet in December.
Most associations lose more money to administration than to churn. Dues are tracked in a spreadsheet, renewals go out as a personal email from whoever remembers, and the people who quietly lapse are discovered months later during a board meeting. The volunteer treasurer becomes a bottleneck for an organization of thousands, and nobody wants the job next year. What it costs is rarely counted honestly: the lapsed members who would have renewed if asked once, and the hours of unpaid work that go into asking everyone else.
- Member dues + recurring billing
- Governance console (/org-admin/)
The platform fee and the member's dues stay separate at every step.
An association platform moves money in two directions at once: the organization pays to run the software, and its members pay the organization. Conflating them is the failure that ends the relationship — a refund issued from the wrong side, a chargeback landing against the wrong account, a ledger nobody can reconcile at audit. It looks like an accounting detail right up to the moment a treasurer has to explain it to a board, and by then the trust is gone rather than the money.
- Member dues + recurring billing
- Paid event ticketing
A regional branch runs its own roster, events and posts without seeing the rest.
Associations are almost never flat. There are regional branches, special-interest committees, graduating classes — each with its own leadership, its own calendar, its own idea of who belongs. Software that models only one flat membership pushes all of that into side channels: a chapter Facebook group, a committee mailing list, a spreadsheet a volunteer maintains. Participation splinters across tools the organization does not control and cannot archive, and the national body loses sight of where its membership is actually active.
- Chapters / committees
- Chapter analytics
That filtering is a design decision rather than a later optimisation: an unfiltered feed in an organization of several thousand members is noise, and noise is what makes a community product go quiet.
A chapter lead governs one chapter: its posts, its events and its roster. The scope is enforced by looking up chapter membership on each request, so a lead cannot reach a chapter they do not belong to.
Chapter-level analytics — participation and activity within a chapter — is a gated capability on the higher tiers.
You receive this. It ships behind a feature flag and sits on the Community+ tier as configured, so it is revenue you can reserve for your own paying customers.
You receive this. It ships behind a feature flag and sits on the Community+ tier as configured, so it is revenue you can reserve for your own paying customers.
Two capabilities aimed at professional associations specifically, both gated to the higher tiers:
You receive this. It ships behind a feature flag and sits on the Professional+ tier as configured, so it is revenue you can reserve for your own paying customers.
Two capabilities aimed at professional associations specifically, both gated to the higher tiers:
You receive this. It ships behind a feature flag and sits on the Professional+ tier as configured, so it is revenue you can reserve for your own paying customers.
You receive this. It ships behind a feature flag and sits on the Professional+ tier as configured, so it is revenue you can reserve for your own paying customers.
You receive this. It ships behind a feature flag and sits on the Enterprise tier as configured, so it is revenue you can reserve for your own paying customers.
Both planes carry the same three capabilities:
Capacity is enforced atomically. A ticket is issued only while capacity remains, using a conditional update that returns zero rows when the event is full. Simultaneous buyers cannot oversell a sold-out event.
A ticket is confirmed only when payment is confirmed server-side — never on the buyer's redirect back from the provider, which is a signal a browser can forge or simply lose. Confirmation is idempotent: a repeated or duplicated provider callback issues at most one ticket.
You receive this. It ships behind a feature flag and sits on the Community+ tier as configured, so it is revenue you can reserve for your own paying customers.
Refunds are processed through the provider within the organization's own policy window.
You receive this. It ships behind a feature flag and sits on the Community+ tier as configured, so it is revenue you can reserve for your own paying customers.
You receive this. It ships behind a feature flag and sits on the Professional+ tier as configured, so it is revenue you can reserve for your own paying customers.
Search runs on trigram matching, so partial and misspelled names still resolve.
Every custom member-facing entity exists on two planes: the organization-scoped surface an organization administrator uses, and a cross-organization mirror the installation's operator uses to view and operate across every tenant.
Identity verification is not a substitute for it: confirming who somebody is does not confirm that they hold a professional credential.
You receive this. It ships behind a feature flag and sits on the Enterprise tier as configured, so it is revenue you can reserve for your own paying customers.
You receive this. It ships behind a feature flag and sits on the Professional+ tier as configured, so it is revenue you can reserve for your own paying customers.
The platform underneath the product — counted in this product's own source, not claimed from a template. Where a row carries a list, open it to read the names behind the number.
Coinbase
dLocal
Flutterwave
Komoju
Mollie
NOWPayments
Opn
Paystack
ActiveCampaign
Customer.io
Segment
Canny
Amplitude
Custom Head Scripts
Pushover
Twilio SMS
Crisp
Tawk.to
Monday.com
fal.ai
Axiom
hCaptcha
Freshsales
Pipedrive
Pabbly Connect
AWS S3
MuxHover a table to isolate what it touches; click one to read its relationships. The big nodes are what everything else hangs off. organizations is referenced by 63 tables because every single record in this product belongs to an organization, and that is what makes tenant isolation a property of the database rather than something the application has to remember on every query.
all 76 tables, as text
active_boosts · admin_notifications · analytics_daily · analytics_events · analytics_funnels · announcement_dismissals · announcements · api_key_logs · api_keys · assistant_actions · assistant_conversations · assistant_messages · assistant_usage · audit_logs · automation_log · automation_templates · ce_credits · ce_requirements · chapter_memberships · chapters · credit_balances · credit_transactions · currencies · data_exports · data_imports · discussion_groups · dues_payments · event_registrations · events · faq_categories · faq_items · feature_flags · group_memberships · inbound_webhook_events · inbound_webhooks · job_applications · job_postings · languages · marketing_audience_members · marketing_audiences · member_applications · member_newsletters · member_profiles · member_subscriptions · membership_audit · membership_tiers · notification_log · notification_rules · notifications · org_membership_settings · organization_limit_overrides · organizations · plans · platform_secrets · platform_settings · post_comments · post_reactions · posts · product_purchases · products · provider_prices · push_devices · report_templates · resources · roles · scheduled_tasks · seo_meta · subscriptions · theme_page_sections · theme_section_library · theme_sections · translations · user_sessions · users · webhook_logs · webhooks
The chassis, and anything particular to this product. 5 required, 1 optional.
No platform lock-in.
Postgres with row-level security, applied by the shipped migration scripts.
Configured by the operator in the integrations panel, not in code. Both billing planes ride it.
Dues reminders, dunning sequences, approvals and event confirmations.
Recurring dues runs and the dunning sequence are scheduled work. Without it charges are not raised on schedule and failed payments are not recovered.
Applied across routes, including the public join and event surfaces.
Already built — plug and play
Every provider integration in this list ships wired into the product. You bring your own keys, connect them in the admin, and go live — there is no integration code to write. Nothing is resold through us: the ongoing cost is whatever these providers charge you. Capabilities marked plan-gated elsewhere on this page unlock by plan, not by extra code.
What exactly do I receive after purchase?
The complete source repository behind the live demo — 142,103 lines across the application and its database, 76 tables defined by 84 migrations that the shipped scripts apply for you, plus the seed data, the demo accounts and the setup documentation. Not a subset and not a scaffold: the same code that runs the demo you just used.
Is the live demo the same product whose source I receive?
Yes. The Ágora demo runs the delivered release (v1.0.0), and the build figures on this page are measured from that same source — not from a showcase build kept separately.
Can I test every account role before buying?
Yes — all 5 of them: Member, Chapter lead, Association owner, Prospect, Platform admin. Each one is seeded in the live demo and reachable from the role board above, so you can inspect the product from the customer's side, the agent's side and the administrator's side before you decide.
Is this a complete product or a starter template?
Complete. 101 page modules and 320 HTTP operations, with authentication, roles, billing, an administration panel, background jobs and seeded demo data all wired and running. A template gives you the shape of an application; this is one you can deploy and start operating.
Can I rebrand and modify it?
Yes, without asking. The name, identity, copy, styling and code are yours to change. Rebranding and operating it as your own service is exactly what the licence is for.
What does the licence allow?
A perpetual, worldwide, non-exclusive, non-transferable licence to the product you bought and to every update released for it. The Standard licence covers one business — yours. If you deploy for clients, the Client licence covers up to five. You can modify it, rebrand it, deploy it and charge your own customers.
Can I resell the source code?
No. Reselling, redistributing, sublicensing or giving away the source itself is not permitted under either licence. You build and deliver products with it — the code stays with you.
What services and ongoing costs are required?
You bring your own accounts, so we never mark anything up and there is no ongoing cost to us beyond the purchase. Required: Node host, Supabase, A payment provider, Email provider, A job queue, Rate limiting. Optional: none. The table above says exactly what stops working without each one; most have usable free tiers at low volume.
How difficult is deployment?
Two ways, and most buyers use the first. The installer in your saascode dashboard walks it: you create free accounts at Vercel and Supabase, connect them, and it provisions the database, applies 84 migrations, seeds the data, deploys and verifies the result — you watch the steps go green. Or take the source and do it yourself with the shipped scripts and docs, which is the same sequence run by hand.
What updates and support are included?
Updates to that product for as long as we maintain it — no renewal fee and no expiry date on your access. Support covers download problems, defects in the code as shipped, questions about what the product does and how it is structured, and licence questions. It does not cover debugging your own modifications, building features for you, or setting up your hosting and third-party accounts.
Why does a complete codebase cost $349?
Because it was built once and is distributed many times. SaaSCode builds each product and ships the same finished release through the catalog, so the price reflects repeatable distribution — not a reduced codebase, an unfinished template, or what the same work would cost commissioned.
Do I need to be a developer?
No, for the normal path. You create free accounts at Vercel and Supabase, connect them to the installer in your saascode dashboard, and it does the deployment for you — provision, migrate, seed, deploy, verify. What it asks of you is creating two accounts and copying a token, not writing code. If you would rather deploy it yourself, or host it somewhere else, the full source and the scripts are yours to do that with. Running the product day to day needs no technical skill at all: that happens through its own interface, which is what the demo shows.