Every chamber of commerce, neighbourhood association, professional group and local network needs roughly the same five things: a member list, a directory of businesses, an events calendar, somewhere to publish, and a way to collect money.

Almost none of them get all five in one place. They get a membership spreadsheet, a directory on a page somebody last edited in 2019, events on a third-party ticketing site, a newsletter tool, and payments through whatever the treasurer already had. Five systems, none of which know the others exist, and a volunteer keeping them in sync by hand.

CivUp is an AI-powered white-label community platform that puts members, business listings, events, content and billing in one stack. It is open source at github.com/phingers/lkn.page, with a live instance running at app.lkn.page, and it is made in North Carolina.

White-label is an architectural commitment

"White-label" gets used to mean a logo upload and a colour picker. Here it means something stricter, and it shapes the entire system.

CivUp supports custom domains and theme presets — directory-first, calendar-first, or hybrid — because the communities running on it are not variations of one another. A chamber of commerce is fundamentally a directory with events attached. A local arts council is a calendar with a directory attached. A professional network is a membership with content attached. Same five primitives, radically different centre of gravity.

Presets are a good answer to that. Building three separate products is unaffordable; shipping one product with a hundred configuration switches produces something nobody can set up. Presets encode the three real shapes as first-class starting points, and let a community begin from something that already resembles what they are.

Custom domains push harder on the architecture. Once a community lives at its own domain, the platform has to handle domain routing, certificates, and per-tenant identity everywhere — and every piece of tenant-scoped data has to stay tenant-scoped by construction, not by a WHERE clause somebody remembered to add. Multi-tenancy is the kind of decision that is nearly free at the start of a build and nearly impossible to retrofit.

Sixty seconds to a working community

CivUp publishes a 60-second average provisioning time — that is the product's own figure, not a Buck Ideas measurement.

The reason it matters is that it addresses the exact moment where community platforms lose their customers. The buyer is typically a volunteer or a part-time administrator evaluating options in the gaps between other work. If standing up a trial takes a scheduled onboarding call and a week of configuration, that evaluation never finishes. It is not rejected; it is simply abandoned.

A minute from decision to working instance means the buyer gets to the interesting part while they still care. Achieving that is not a marketing exercise — it requires every default in the system to be genuinely usable without customisation, which is a much higher bar than making everything configurable.

The AI is aimed at the boring problems

The AI in CivUp is not a chatbot bolted to the corner of the screen. It targets the specific tasks that consume a community administrator's week.

Moderation. The platform publishes a 99% spam catch rate for its AI moderation — again, CivUp's own published figure. Spam is the disease that kills community platforms. Not dramatically; gradually. Real members stop posting because their contributions sit among junk, and by the time anyone notices, the community is dead. A volunteer moderator cannot keep up, and an unmoderated forum is worse than no forum.

Bulk import with AI categorisation and deduplication. This solves the migration problem, which is where most platform switches fail outright. A community arriving from spreadsheets has hundreds of business listings with inconsistent formatting, no categories, and duplicates from years of manual entry. Ask a volunteer to clean that by hand and the migration stalls permanently. Categorising and de-duplicating on import is the difference between a switch that completes and one that gets abandoned in week two.

Conversational search lets members ask for what they need in plain language instead of learning a category tree — the right interface for a directory, where nobody knows the taxonomy the administrator invented.

Member matching attacks the other slow death. A member who never meets anyone is a member who does not renew, and matching is a direct, automated answer to that.

Weekly insights give the administrator a picture of what is actually happening without building reports by hand.

Each of those is aimed at work that was previously manual and previously skipped. That is a far better use of AI in a product than adding an assistant nobody asked for.

Gamification, and being careful about the number

CivUp includes built-in gamification, and publishes a figure of 24% higher quarterly retention attributed to it. That number is the product's, published on its own site.

It is worth stating the mechanism plainly, because gamification has a bad reputation earned by products that added points to things nobody wanted to do. In a community platform the underlying dynamic is real: participation is self-reinforcing, and the hardest period is the beginning, when a member has posted nothing, knows nobody, and has no reason to return. Visible progress and recognition give a reason to come back one more time — which is often all that is required for the community itself to take over.

Retention is also the only metric that matters for a subscription community. Acquisition is a one-time event; renewal is the business.

Open source, deliberately

CivUp is open source at github.com/phingers/lkn.page, with a live instance at app.lkn.page.

For infrastructure a community depends on, that is a meaningful commitment rather than a badge. A chamber of commerce putting its entire membership, directory and billing into a hosted platform is taking a real risk on that platform's future. Open source is the answer to the question every careful buyer should ask and usually does not: what happens to us if you disappear?

It is also an honest signal about the code. A repository anyone can read is a repository that has to be worth reading.

Why this is a platform

Multi-tenancy with custom domains, five interlocking subsystems, billing, AI on the critical path, and configurable presentation. Any one of those is an application. Together they are a platform in the strict sense — and, unusually, one whose complexity exists so that the communities running on it never have to think about any of it.