// how the factory works

The how, for anyone who wants to see it

One factory. One standard. Four things it makes.

This page is the how, for anyone who wants to see it. What you get is under Solutions, and who it fits is on the who-it's-for page. This is how everything is built, run, and kept yours: from one proven spine, checked before it ships, and looked after with you long after. We do not build and leave.

Built once, fitted to you

One blueprint. Many builds.

The blueprint is built and tested once, then fitted per client with the parts their trade needs and wrapped in their brand. Different on top, the same proven machine beneath, which is what lets us build many and hold every one to the same standard.

A site
Your public face. Light, fast, and stores nothing sensitive. The window the world sees.
A hub
Your engine room. Runs the whole organisation from the inside, with an assistant that knows your work. Running at Simone's Kitchen and Zuidgeluid.
A product app
A standalone product the public signs up to and pays for, with its own assistant. Live today as Know Thyself.
An assistant
A specialist work tool for one job, beside a client's existing systems: analysis, grant dossiers, accounting prep. Grounded in the client's own material, and a person approves every output.
One repositorythe blueprintSitepublic faceHubengine roomProduct apppublic productAssistantspecialist lanestatusback up

One repository holds the blueprint. Four kinds of project are built from it, each its own to keep.

One spine, your skin

This whole page just changed brand. Nothing under it moved.

Everything you're looking at sits on one shared spine. The same layout, the same working parts, the same tested code behind every AI Smith site. Your brand goes on top as a skin: your colours, your type, your feel. Try it. The buttons below reskin this exact page live.

You're viewing the forge skin.

Fixes reach you for free

When we improve the spine (speed, security, a new feature), every site on it gets the improvement. You never pay to rebuild what everyone shares.

Live in days, not months

The hard engineering is already done and proven on other sites. We fit your skin on top, so you launch with something battle-tested from day one.

Still unmistakably yours

A shared spine underneath doesn't mean a templated look on top. Your skin is yours alone, and it's yours to keep, like everything else we build you.

The stack, in plain terms

Built on a proven spine, not vibe-coded.

Every build starts from one foundation we have built, tested, and secured once, on the same dependable open technology the largest software runs on, and proven on real systems today. Nothing is generated fresh and hoped over each time. A proven way of building, not a lucky one.

PostgreSQLSupabaseServer-rendered webRow-level securityStandard open formats
Proven
The same primitives that run banks and governments, tested once and running in production behind real clients, not assembled anew per project.
Secure
Locked down with row-level security on every table, and checked against one standard at a gate before anything ships.
Portable and owned
Open formats and your own database, so leaving is a transfer, never a rebuild. The full promise is on the ownership page.

The engine room, step by step

How a hub is built.

The Core is built once and reused. Per client we add the parts their kind of work needs and fit their brand, then lock it down on every table and score it against the standard before a person ships it. Sites, product apps, and assistants follow their own shorter paths, the same way.

step 01
Scope the parts
step 02
Build the Core
step 03
Add the parts
step 04
Apply the brand
step 05
Lock it down
step 06
Verify & ship

We do not build and leave

Build it, then run it, watch it, and grow it with you.

A proven system is the start, not the finish. Four parts look after every build over time, and a person signs off every change to anything live. They read freely and write only behind a human, so nothing reaches your system without someone deciding it should.

Builder: builds it
Assembles a new site or hub from the proven spine. It must pass the check before it goes anywhere.
Inspector: checks it
Scores every build against the one standard. It is the gate, and nothing ships until it passes.
Caretaker: maintains it
Makes the changes a live system needs, content and fixes and improvements, each one signed off by a person.
Watchman: watches it
Keeps an eye on everything running for drift, and flags what needs attention. It never quietly fixes itself.
Watchmanwatches it, never fixesBuilderbuilds itInspectorchecks it · the gateThe live systemRUNNINGCaretakermaintains it · via a person

The rules it runs by

Why every build behaves the same underneath.

Propose, don't dispose
The automation proposes a change. A person decides whether it happens. The machine never has the last word on a live system.
Separate seeing from touching
The parts that watch cannot change anything. Watching and changing are kept apart, and changing is always a human call.
You can always leave
Portability is built into how it is owned, not promised about us. The system runs without us if it ever has to.

That is the how. The what starts from your trade.

One standard, one promise: built to fit on a proven spine, run and improved with you, and yours to keep. Tell us what you run and we'll show you the build closest to yours.