The stack
Multi-tenant from the first commit, because retrofitting it is a rewrite.
Tenancy, roles and billing are cheap to design in and very expensive to bolt on. The company that skipped them is the one calling for a rescue two years later.
What is specified, not assumed
- Tenancy
- row-level, from commit 1
- Auth
- self-hosted, no vendor
- Roles
- owner · admin · member
- Real-time
- websockets + presence
FIG. 1 — Web & product
What we ship in this layer
SaaS products
Multi-tenant from the first commit — auth, billing, roles and an admin surface, because retrofitting tenancy later is a rewrite.
Customer portals
Somewhere your customers answer their own questions, which is the cheapest support you will ever build.
Admin dashboards
Internal tools your team actually opens, built around the job rather than around the database tables underneath.
Marketing sites
Fast, accessible, and yours. No page-builder licence, no plugin sprawl, no theme you cannot change without breaking it.
Accounts & permissions
Roles, teams and invitations designed once and enforced everywhere — the part that becomes very expensive to bolt on late.
Real-time & collaboration
NewWebsockets, presence and live sync so two people editing the same thing is a feature rather than a support ticket.
Real-time & collaboration
Websockets, presence and live sync, so two people editing the same record is a feature rather than a support ticket and a data-loss incident.
New — and a genuine capability claim, not a roadmap item.
Say what is broken. Or what is missing.
One number and one date come back in writing, from the person who will do the work. Nothing starts, and nothing is owed, until you approve.