The code
your GitHub
Yours from the first line, in your own repository — not handed over at the end as a favor.
fire us tomorrow, the app keeps running
Your customer list. Your salaries. Your contracts. Every one sitting in a database belonging to somebody you have never met, protected by a security team you did not hire and cannot inspect.
It’s time to take back control.
your GitHub
Yours from the first line, in your own repository — not handed over at the end as a favor.
fire us tomorrow, the app keeps running
your servers
Register a cluster of your own and everything deploys there instead of here.
invite-only todaythe data never leaves your building
your storage
Your bucket, your region, your encryption key — switched on only once a real test round-trip succeeds.
documents sit where your lawyers said they must
your directory
People arrive and leave through the staff directory you already run.
someone leaves at 4pm, out everywhere at 4pm
your account
Ours, your own account with OpenAI or Anthropic, or a model running on a machine you own.
a vendor you can replace cannot set your terms
All of it.
Most leaks are not break-ins. They are a well-meaning person putting the wrong thing in the wrong place on a Tuesday afternoon. A rule in a handbook does not stop that.
So we split the two: the record is always on and you never had to ask for it. The blocking is a decision about your own business, so it waits for you to make it — and it turns itself on the moment you tell us you handle regulated data.
Not only the AI. Every email your software sends, every text message, every payment, every file that goes to another company. What went out, who received it, when — and what was taken out of it first, once you have said what should be. From the day you started to the app still running a year later.
Why that matters: one day somebody will ask what left your company and where it went. A customer, a regulator, your own board, or a lawyer after somebody else was breached. You answer with a list, not a shrug — and the list is the form they already use, with no limit on how far back it goes.
The last few years added one more company to everybody’s list, and most places have no say over which one it is. Here you do. Use ours. Use your own account with OpenAI or Anthropic, so the questions go under your contract and your bill. Or point it at a model running on a machine in your own building, in which case nothing leaves at all. We do not sell you the AI, so we have no reason to care which one you use.
Why that matters: a vendor you cannot replace is a vendor who sets your terms. If a price triples, a model gets worse, or a company you would rather not deal with buys one — you change that one part in an afternoon and nothing else moves. The app does not notice. You are not tied to anybody, including us.
Your work does not arrive all at once, and it does not have to move all at once. Each contract ends on its own date — no big-bang cutover — and what that company was doing for you becomes an app you own. The few you genuinely cannot replace, like your bank, stay where they are and connect in.
A company has never been able to hold itself in its own head. What it knows lives in people — and people leave, forget, take holidays, and work in a different building from each other.
This is the return on one boundary: not only that less of your business sits in other people’s databases, but that for the first time all of it is somewhere a question can actually reach.
“The Riverside order is late again. What do we do about it?”
What we are owed when they are late — clause 11.4
The customer already called twice about it
We paid this supplier early, in full, in June
They slipped the same way before — we used Harlow instead
usually lostand the 2023 note is gone, because the buyer who wrote it left in April.
Claim under 11.4, call the customer before they call a third time, and get a quote from Harlow — who we already know delivers when these people do not.
one company, one memory
Three moments where a person, not a machine, has to agree. You choose which of them apply to you — a company of four can switch them all off, and a hospital can switch them all on.
Names, card numbers and addresses come out of a question before it leaves. Your judgment does not. If you ask a model about a problem, the model sees the problem — that is what asking is, and anyone who tells you otherwise is selling you something.
What you actually get to control is who sees it, whether they keep it, and whether you can prove either. That is the whole of what we sell. We are not going to pretend it is more.
Take the code — it is already in your own repository. Take the data — it is ordinary Postgres, export it and walk. Take the files — they can be in your own storage from day one. Run the whole thing on your own servers. Use your own AI account.
Every company selling you independence would like you to depend on them instead. Ours is the shorter list: the things you would have to take with you are already yours.