Our multi-tenant SaaS foundation — organisations, roles, billing and audit logging wired up before a line of product code is written.
Most SaaS builds spend their first month rebuilding the same substrate: sign-up, organisations, invitations, role checks, a billing integration and somewhere to read the audit trail. We got tired of rewriting it, so we factored it out. The kit ships row-level tenant isolation enforced at the query layer rather than in application code, so a missing "where organisationId" cannot leak another tenant's data. Roles are checked in one place and the check is the same on the server action and the API route. Stripe subscriptions, seat counting and proration are handled, including the parts teams usually discover late — failed payment dunning, plan downgrades that exceed the new seat limit, and webhook replay. We start most product engagements from this kit. It is the reason a client's first working, deployable, authenticated build is usually days rather than weeks.
