# Ágora

> Member directory, dues, chapters and events in one platform — on a codebase you own, instead of Wild Apricot's per-contact subscription.

Source page: https://saascode.ai/products/agora
Machine-readable record: https://saascode.ai/products/agora.md

One-time purchase · full source code · self-hosted by the buyer.

Price: $349 (one-time)

## How to read this document

Written for a model auditing this product on a buyer's behalf. Two labels
appear throughout and they mean different things:

- **measured** — produced by a script reading the product's own source tree
  or database at the stated date. The method is named beside each number.
- **stated** — written by the seller. True or not, it is a claim, and this
  document does not ask you to treat it as evidence.

The live demo is the strongest verification available from outside: it runs
the same source a buyer receives. Nothing to sign up for — the public side is
open, and the seeded credentials below get you into each role.

## What it is

Ágora is a community operating system for member organizations — professional associations, alumni networks, NGOs, chambers of commerce and clubs.

## Live demo

Two doors into the same running instance, and the same source a buyer
receives. There is no account to create; the public side is open, and the
seeded credentials below sign you into each role.

- **Guided (recommended):** https://saascode.ai/demo/agora — our shell, with a role switcher and
  the credentials in the menu. Best for a person.
- **Direct:** https://agora.saascode.ai — the product on its own, no chrome.
  Best when you are relaying steps to someone, or fetching a page.

5 roles seeded on the demo (of the 6 the schema defines — the build data below counts them all). Credentials are published deliberately: these
are demo accounts on a public demo instance, and a reviewer who cannot get
in cannot verify anything.

- **Member** (`member`) — `user@demo.com` / `demo123`
  The member app, on an active dues subscription.
- **Chapter lead** (`chapter_lead`) — `chapter-lead@demo.com` / `demo123`
  Leads the Northeast Chapter and its members.
- **Association owner** (`org_admin`) — `org-admin@demo.com` / `demo123`
  Runs the governance console for the organisation.
- **Prospect** (`prospect`) — `prospect@demo.com` / `demo123`
  Applies to join — the flow before membership starts.
- **Platform admin** (`super_admin`) — `admin@demo.com` / `demo123`
  The backend: every organisation, plans and settings.

Or open a role directly: https://saascode.ai/demo/agora?role={role}

## Measured build

*measured — each number names the method that produced it.*

- **roles: 6** — distinct roles accepted by the role CHECK constraint: admin, chapter_lead, member, org_admin, prospect, super_admin
- **tables: 76** — distinct CREATE TABLE statements across every applied migration
- **migrations: 84** — .sql files in supabase/migrations
- **page modules: 101** — files named page.tsx under src/app, excluding node_modules and .next
- **source lines: 142,103** — lines of code (comments and blank lines excluded) across 1006 TypeScript files (127,991) and 111 SQL files (14,112); node_modules and .next excluded
- **api route files: 237** — files named route.ts under src/app/api
- **http operations: 320** — exported HTTP method handlers across those files, de-duplicated per file, OPTIONS excluded as CORS preflight
- **schema graph: 76 tables, 140 relationships** — parsed from the applied migrations

A large number here is scope, not quality. It says the product models a
real domain rather than a CRUD skeleton; it says nothing about code
quality, duplication, test coverage or maintainability, and should not be
read as if it did.

Release: v1.0.0 · built 2026-07-23

## Complete capability inventory

19 capabilities. Each summary is *stated* — selected from the
product's own buyer documentation, or written by the seller where marked.

### Community & chapters

- **Community feed + reactions/comments** — A post stream with reactions and comments, filtered by group and chapter from the first version rather than presented as a firehose. A member of three chapters sees those three chapters; a member of one sees one.
- **Discussion groups** — Topic groups within an organization, separate from chapters. A member joins the ones relevant to them, and group activity flows into their feed.
- **Chapters / committees** — Chapters are the organizational sub-layer — a regional branch, a special-interest committee, a graduating class. Each has a roster, its own posts and its own events.
- **Announcements (platform)** — Announcements are organization-wide notices. Member newsletters are a gated capability that lets an organization administrator send to the whole organization, to a membership tier, or to a single chapter — the same audience segmentation the rest of the product uses.
- **Member-only resource library** — A gated document library backed by object storage, with access governed by membership tier and chapter. It is the standard answer to "where do the bylaws, the templates and the recordings live" without publishing them to the open web.
- **Member newsletters** *(seller-authored)* — Lets an administrator send a formatted newsletter to the whole organization, to one chapter, or to a single membership tier, so the message reaches the people it concerns instead of everyone every time.
- **CE credits (NEW)** — Both follow the same two-plane pattern as every other custom entity: a member-facing surface, an organization-scoped management surface, and a cross-organization mirror for the operator.
- **Job board (NEW)** *(seller-authored)* — A member-facing job board with an organization-scoped surface for managing postings. It gives an association the thing members most often renew for: opportunities they cannot find anywhere else.
- **Chapter analytics** *(seller-authored)* — Per-chapter figures on membership, activity and events, so a regional branch or committee can be evaluated on its own numbers rather than folded into the organization total.
- **Direct messaging** — Member-to-member messaging is a gated capability, defaulting off in this version. An organization turns it on deliberately, since a community with private messaging has a moderation surface that one without does not.

### Dues, events & ticketing

- **Member dues + recurring billing** — The payment provider is configured by the operator in the integrations panel, as managed platform secrets. It is never hardwired into the code and never lives in environment files, so the provider can be swapped without a code change.
- **Free events + RSVP** — Every organization gets events with RSVP on every tier. Free events do not depend on the paid ticketing capability — RSVP stands alone and ticketing extends it.
- **Paid event ticketing** — A gated capability, and the part with the most exacting requirements.
- **Events waitlist** — When an event is full, buyers join a waitlist. A cancellation promotes the next person in line and notifies them.
- **Programmatic + agent API** — For organizations automating intake, a gated agent-facing API exposes the multi-step operations as single calls: apply for membership, approve a member, assign a member to a chapter, and register for an event. Each declares its step plan, the events it emits, and writes a single audit record. The event registration verb carries the same atomic capacity check and idempotent payment confirmation as the interface does.

### Members & directory

- **Member directory + profiles** — A searchable member directory with per-member profiles. Visibility is governed by a privacy structure on the profile plus the organization's own rules, so a member can be listed to their chapter, to their membership tier, or to the whole organization.
- **Governance console (/org-admin/)** — An organization administrator works from a console scoped to their own organization, covering member approval and verification, chapters, events, the dues ledger, reports, and the organization's branding and dues settings.
- **Credential verification (Checkr)** — An optional hard credential check — a lookup against a professional licensing board, for example — is available through a pluggable provider and ships feature-gated off. It exists for regulated forks.

### Other

- **Member verification rules**

## What each system gives the operator

*stated.*

- **Community & chapters** — Members find each other and stay reachable without the board running a mailing list.
- **Dues, events & ticketing** — Dues and ticket money arrive on schedule, in the right direction, without manual chasing.
- **Members & directory** — Applications become verified members through a documented path, not an inbox.

## The problems it was built to solve

*stated — the seller's argument, given in full so you can judge it.*

### 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.

### 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.

### 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.

## What it takes to run it

*stated — external services the buyer supplies and pays for directly.*

- **Node host** (required) — No platform lock-in.
- **Supabase** (required) — Postgres with row-level security, applied by the shipped migration scripts.
- **A payment provider** (required) — Configured by the operator in the integrations panel, not in code. Both billing planes ride it.
- **Email provider** (required) — Dues reminders, dunning sequences, approvals and event confirmations.
- **A job queue** (required for dues) — Recurring dues runs and the dunning sequence are scheduled work. Without it charges are not raised on schedule and failed payments are not recovered.
- **Rate limiting** (required) — Applied across routes, including the public join and event surfaces.

## FAQ

**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.

## Licence

The buyer receives the complete source and may deploy, modify and operate it
as their own SaaS, charging their own customers. The source itself is not
resold or redistributed: you build and deliver **with** it, you do not sell **it**.

## What this document cannot tell you

Stated plainly because a review that misses it is not a review:

- code quality, duplication, or architectural consistency
- test coverage
- query performance under load
- security posture beyond what the stack implies
- how maintainable it will be in a year

Scope is measurable from outside; implementation quality is not. Anyone
evaluating this should say so rather than infer quality from size.

## Written about it

- [Road to Ágora](https://saascode.ai/inside/road-to-agora.md)
- [Hivebrite vs Ágora vs Tendenci — an honest comparison](https://saascode.ai/inside/hivebrite-vs-gora-vs-tendenci-an-honest-comparison.md)
- [Membership Management Software Buyer's Guide 2026 — Organized by What Growth Costs the Association](https://saascode.ai/inside/membership-management-software-buyer-s-guide-2026-organized-by-what-gr.md)

## Links

- Catalog page: https://saascode.ai/products/agora
- Product record: https://saascode.ai/inside/products/agora
- Live demo: https://agora.saascode.ai
- Every product: https://saascode.ai/llms.txt