One person. A whole platform.
It is the genuinely theirs promise made runnable. Client sites live on infrastructure their operator owns outright, edited by their owners, with no per-seat rent and no vendor who can turn the lights off.
- The Brief
The industry default hands a client a sub-account on somebody else’s platform. When the subscription lapses, the storefront goes with it - and the client never owned the thing they paid for.
- Diagnosis
Rent commodity substrate; own everything that touches product logic and data. Hosting, DNS and payment rails are swappable commodities. The schema, the auth, the modules and the tenant model are not.
- The Build
01 · A monolith with a module law
One deployable API, but every feature lands as a self-contained module touching the core in exactly two lines. One person can hold a monolith in their head; the law keeps it holdable as it grows.
02 · Schema drift fails a test, not a customer
The table count is hard-asserted in the test suite, every migration ships hand-written, and the full suite runs before merge. The one time the check was skipped it cost a debugging cycle, and the lesson became a rule with teeth.
03 · Production scars become written law
A deploy once died because a locally built artifact vendored the wrong architecture onto the host. The operating file now prescribes exactly how each half deploys, and every deploy verifies its own health before promotion.
04 · White-label is a feature to earn
Reseller mode is being built deliberately - a scoped role first, a hand-tailored pilot before any general partner layer. The platform grows at the speed of real demand.
- Artifacts Delivered
- 01Multi-tenant platform: site editor, agency CRM, pipeline, accounting, commerce
- 02Self-built authentication with admin, tenant and agency scopes
- 03Custom-domain routing and per-tenant sender identity
- 04Two live tenant businesses in production
- Outcome
Two real businesses run on infrastructure their operator owns outright, at no per-seat cost, with their content editable by them and their data in a database with no vendor SDK in the path.
- Receipts
- 886test functions run before any merge reaches a tenant
- 76tables, the count asserted by a test so drift fails loudly
- $0per-seat rent charged to a tenant
- Not yet known
- —Uptime over a measured window
- —Hours saved per tenant versus a rented builder
- —What the platform costs to run at ten tenants
There is no formal uptime monitor on the tenant surfaces - health is checked on deploy and by hand, which is honest for two tenants and inadequate for twenty. The cost curve is modelled rather than observed. Both become real numbers at the tenant count that justifies the instrumentation.
"Cheaper, better, and genuinely theirs requires somewhere for theirs to live. This is that place."