
Community Hub
Spaces, posts and a question-and-answer board with reputation, saved items and a moderation queue that records every decision.
Next.js · TypeScript · PostgreSQL · MDX
Member overviewMember1 / 6
Membership bodies lose people quietly. A card expires, a renewal email lands in spam, and somebody who would happily have stayed is gone. This build treats lapse as the number that matters rather than headline membership.
Next.js · TypeScript · PostgreSQL · Auth.js
Inside the app
23 connected functions on one schema, spanning three permission levels. Everything below is in the template before a line of customisation.
Your membership renews in 34 days and two benefits go unused each year.
What you hold, since when, and what it entitles you to.
What your grade entitles you to, and what you have actually used.
What you have paid, and what is collected next.
The register, by grade and standing.
Who renews when, and whose payment will fail before they do.
Who left, when, and whether anybody asked why.
Grades, what they cost, and what they entitle a member to.
Every grade change, fee change and lapse. Retained for seven years.
Permissions
A member sees their own record and benefits. A membership officer sees the register, renewals and lapse. An administrator sets grades and fees. Lapse is surfaced to the officer while the member is still a member.
The build
23 functions, all of them live in the preview. Nothing on this list is a mockup or a roadmap item.
What you get
Professional bodies, trade associations and clubs with 500 to 100,000 members.
Access and evidence
Headline membership hides the churn underneath it. A body recruiting 800 and losing 750 looks stable and is quietly failing, and most of those 750 left because something administrative broke, not because they decided to.
Related

Spaces, posts and a question-and-answer board with reputation, saved items and a moderation queue that records every decision.
Next.js · TypeScript · PostgreSQL · MDX

Donations, appeals, regular giving and restricted funds, with donor consent kept straight.
Next.js · TypeScript · PostgreSQL · Recharts

Courses, lessons, quizzes, assignments, a gradebook, live classes, cohorts and certificates, with completion records that survive an audit.
Next.js · TypeScript · PostgreSQL · MDX
Questions
Yes. The repository, application code, database schema, migrations, seed data and deployment configuration, is transferred to your organisation on delivery. There is no licence key and nothing that calls home.
Pricing does not change with member count. For a membership body that matters more than usual: per-member pricing means your software bill grows exactly as fast as your income, which is a poor trade for a subscription organisation.
It records what is owed, what was collected and what failed, and drives the renewal and dunning chase. Collection goes through your payment provider or direct debit bureau, which is a standard integration in a fitted build. We do not sit in the money flow.
Because it is the strongest available predictor of lapse. A member paying happily but using nothing is far more likely to leave than one who pays late and attends everything. Surfacing that while they are still a member is the whole point.
That is the usual route. A fitted build sets up your grades, eligibility rules, fee structure and instalment options, benefit entitlements, renewal and grace periods, branding and up to two integrations, typically in one to three weeks.
Hosting only, paid to your own cloud provider, roughly $50 to $200 a month regardless of how many members you hold.
A fitted build adjusts fields, stages, roles and integrations to how your team already works. One scoping call, a fixed price, one to three weeks.
