Kiln Cloud — Multi-tenant Laravel SaaS

A B2B SaaS foundation: tenancy, Stripe billing, team invites, and an operator console before the second customer arrived.Kiln needed to stop demoing a single-tenant prototype. We shipped tenancy, plans, and a support console so they could onboard two paying teams without SSH.The prototype was one database with no tenant key. Billing was a fake toggle. Support meant opening tinker. Investors asked how a second customer would be isolated — there was no answer.We wrote the tenant model first (single DB, tenant_id, with the isolation tradeoff on paper), then plans, Stripe webhooks, team invites, and a Filament-style operator console. The public marketing site stayed on a separate Next.js route map.

What we built

Tenancy, billing, and onboarding shipped before vanity charts. Each tenant gets teams, seats, and a 30-day cancel-and-keep-data rule. Operators can impersonate a tenant without production SSH.

Stack and boundary

Laravel API and jobs; React for the product UI. See Laravel SaaS development and Laravel + React. Marketing pages used Next.js so SEO routes were not client-only.

What we cut from v1

Chat, a mobile app, and custom report builders. Two real tenants in private beta were the acceptance test.