Drawing register

Proof, framed by what it demonstrates

A club platform is multi-tenant SaaS engineering. A drawing set becoming a priced bill is document intelligence. Read these for the engineering underneath rather than the industry on top, because the industry on top is the part least likely to be yours.

Five pieces of work: three live, one a prototype and one a proof of concept. Nothing here is described as more finished than it is. What each word means.

Sheet: A-01
Title: Work
Issued for: Information
Drawn by: Snilld

W-02Sports OS

Multi-tenant SaaS in productionSport and recreationLive

The home page of a demo swimming club: its own badge and colours, a pool drawn at rest with the time of the next session, and buttons to join or find a program. — Preview · W-024 screens

The home page of a demo football club on the same platform, in its own green, with a court drawn at rest and the time of its next session. — Preview · W-024 screens

Sheet W-02 · Multi-tenant SaaS in production · Sport and recreation

Live

Our operating system for sports academies and activity clubs: one codebase serving several fully branded tenants with isolated data and role-based access, running in production.

The swimming club’s programs: Learn to Swim for ages six to ten, with its weekly batches, their times and how many places are left in each. — 03 / 04Programs and batches, with places left

The football club’s programs on the same screen: Grassroots Football for ages six to ten, its batches and places left, in the football club’s colours. — 04 / 04The same screen, another tenant

Demo data. Every name and number is invented.

Goes in: One codebase, one deployment, one owner console
What we built: The host decides which tenant you are, and every query is scoped to it
Comes out: Four branded sites, each with its own content, roles and members
The line it does not cross: No tenant can read another tenant’s data

Note 1 · The constraint

An operator running more than one site, brand or franchise usually ends up with a separate installation per customer. Every change then has to be made several times, and the copies drift apart within a year.

Note 2 · What transfers

This is the engineering that lets one system serve many customers, branches or franchisees without forking it per customer. A vendor portal, a dealer network or a multi-site operations tool is the same problem wearing different clothes.

Tenants live: Four
Public club sites: Two, each on its own domain
Automated tests: ~1,290
Hosting: Oracle Cloud, Hyderabad
Tenant isolation: Per-tenant data scoping
Clients: Anonymised

The full write-up →A platform we operate →

Legend

How to read this register

Four status words and two rules. The words are load-bearing: each one is a claim about how finished something is, and we use them literally.

Live: Running in production and used by people who are not us. If it says live, you can look at it.
In build: Being built now, with a client, against a date. Some of what is described is working and some of it is not finished.
Prototype: Demonstrates a design rather than carrying real load. Where the stored state is simulated instead of a production database, the facts panel says so.
Proof of concept: Proves the hard part works on real inputs. It is not a product and it is not in production.
Clients: Anonymised. No client is named unless they have given written permission, so most entries describe the organisation rather than naming it. The constraint and the engineering are described exactly as they are.
Numbers: No accuracy or confidence figure appears anywhere on this page, because none has been measured under conditions we would be willing to publish.

W-02Sports OS

Note 1 · The constraint

Note 2 · What transfers

How to read this register

Two of these are platforms we operate