What we do
Eight things, and we will tell you which two are still in build. A vendor who hides the unfinished parts is telling you what their finished parts are worth.
Your SEO, in numbers you can check
Every render, every human, every city, every referrer — with a receipt behind each one.
Most SEO reports are a PDF someone typed. Yours is a query. You see total renders, the human-versus-bot split, which pages earned traffic, which cities they came from, what referred them, and what it billed — read straight from the meter rather than compiled by hand once a month. Over 19 metered days (13 June – 2 July 2026) the network served 1,900,813 renders; 62,597 of them were human. You can ask us to prove any row.
Pages that earn their place
City and product pages built from your real inventory — and only published where demand exists.
We can generate every combination of what you sell and where you sell it. We do not. Google penalises volume without substance, and a page nobody searches for is a liability. So we mine People Also Ask, study who currently ranks, and run cron jobs that harvest long-tail queries until we know what your market actually types. A page ships when it exists in your data AND real humans reached it. For our flagship tenant that meant 1,045,463 possible pages narrowed to 4,078 — 0.39% — and the rest stay unpublished until they earn it.
Found by the AIs people ask instead of Google
A machine-readable version of your business, published where the answer engines read.
When someone asks an assistant for a supplier, that assistant reads pages — it cannot be fooled by keywords or hidden text. So we publish a clean structured summary of your business at llms.txt, declare what each crawler may use, and expose a queryable endpoint so agents can read your catalogue directly. One of our tenants took a phone call from a customer who found them through ChatGPT six days after launch, before any of this was switched on.
Books that cannot be quietly edited
Append-only ledgers where every entry is hash-chained to the one before it.
Entries are added, never altered. Each one is sealed with a hash that includes the previous entry, so changing an old number breaks every number after it — visibly. You get renders, revenue, the running total and the chain head on one screen. If you are ever audited, the answer is not a spreadsheet. It is a proof.
A website with no server to rot
Rendered at the edge from your data in about a quarter of a second.
There is no WordPress install to be hacked, no plugin to break, no host to migrate off. Your site is data in a tree, addressed by your own hash, rendered on demand at the network edge in roughly 239ms anywhere in the world. Change the data, the site changes. Nothing to deploy.
Proof, published
Your site publishes its own audit trail so anyone can check our work — including you.
Every page, price and record is hash-chained: each hash is computed from the content plus the previous hash. We publish the recipe and the chain head so you — or your accountant, or a sceptical customer — can recompute it independently. 5,494 rows of our own production history verify under that formula today. We do not ask you to trust us. We hand you the means to check.
An assistant that reads your whole record
Ask it anything about your business; it loads your history from the chain each time.
It is not a model that "remembers" you — we are precise about that because the truth is better. Every prompt and every answer is written to your chain, and at the start of each session your assistant reads it back. That means the continuity is auditable: you can see exactly what it knew and when. Marked up to cover its own cost and then some, so you can use it as much as you like without us metering your curiosity.
Your data, on your machinein build
Local-first: your copy is the master, ours is the cache.
The design point is that you can walk away with everything and lose nothing. Today your data lives in our edge database and object store, and we hold what we need to render your site and bill you accurately — the privacy policy says exactly what that covers, because it is currently true. Client-side encryption is in build. Until it ships we make no stronger promise than the one the policy states, and you should be sceptical of any vendor who makes one.