Sembr
The Challenge
Chambers of commerce, trade associations and service clubs in the 75 to 400 member range are running on software built for somebody else. The established platforms sell by contract, price per member so that growing your organization costs you more, and are increasingly owned by private equity rather than by anyone who answers the phone. The alternative most small organizations actually use is a spreadsheet and a payment link.
The thing that kept surfacing in audits of real chambers was simpler and worse than pricing. The organization does not own its own data. Getting a clean member list out is a support ticket, and leaving is a project with a budget.
The Approach
Sembr is a Laravel application on PostgreSQL where every queryable row carries a tenant id and isolation is enforced by the database through row-level security, not by a developer remembering to add a condition to a query. That decision was made on the first day because it is the one thing that cannot be retrofitted later.
Dues and event payments run through Stripe Connect, so the money lands in the organization's own Stripe account rather than sitting in ours and being forwarded. Files live on Cloudflare R2. The member portal and the embeddable widgets consume the same public API the staff interface uses, which means there is no private back channel that only the vendor can reach.
The audit log is append-only and hash-chained per organization, written under a separate database role. Tampering is detectable rather than merely discouraged. Personal information never enters logs, commits or AI prompts, and a commit hook enforces that instead of a policy document asking politely.
AI features are additive and the platform is fully usable with every one of them switched off. Export everything, as JSON, CSV and SQL, ships as a feature rather than as a concession extracted by a leaving customer.
The Result
Sembr is in build, with early access applications open at sembr.co. Pricing is public and flat, with no per-member fee and a discount for nonprofits.
Five development gates are complete: audit infrastructure and role separation, then core membership, dues and events with Stripe Connect, then a compliance pass covering data subject requests, erasure and export. Embeddable widgets and the member portal are live in the current version.
It is not launched, and the remaining list is the unglamorous half: production hardening, a penetration test, and a restore that has actually been rehearsed. Membership software holds a community's contact list and its money. Shipping that early is not a growth strategy.