Pre-launch · sovereign IT
A whole IT department. Owned, not rented.
SovereOS builds and runs the IT a mid-sized company actually needs — devices, network, identity, files, mail and an AI-native workplace — on foundations the company owns. Managed by us, operable without us, with the way out written down before anything starts.
- Hardware to workplace
- Identity you control
- Exit written in the contract
Most companies do not have IT, they have subscriptions
Three things that are true of a great many forty-person companies, none of which anybody decided.
The continuity plan is one person
One person knows the admin passwords, which supplier does what, and why that server exists. Nothing is written down, because writing it down was never anybody's priority. That person leaving is a bigger risk than any of the ones on the risk register.
Nobody can price the exit
Ask what leaving the current suite would cost — in money, in weeks, in data that does not come out cleanly — and there is no answer. A cost nobody can state is a cost nobody is managing.
AI arrived without a policy
Staff are already pasting quotes, contracts and customer data into consumer tools, because it helps and nobody told them not to. There is no boundary, no record of what left, and no realistic way to put it back in the box by banning it.
Audit, rebuild, operate
Three phases, and the point of the first two is to make the third one boring.
- 01
Audit
What you run, what it costs, who can actually operate it, and what leaving each piece would take. Written down and handed over, including the parts that argue against changing anything.
- 02
Rebuild
Devices, network, identity, files, mail and the workplace, moved onto foundations you own — in an order chosen so the risky parts happen while there is still a way back.
- 03
Operate
Managed support with response times you can hold us to, a named engineer who knows your environment, and documentation good enough that your own people take more of it over each year.
The whole estate, not a layer of it
The gaps between suppliers are where most IT problems in a mid-sized company actually live.
Devices and hardware
Procurement, imaging, enrolment, repair and end of life. Managed centrally, wiped remotely, and specified so a laptop lasts five years instead of the three a leasing plan assumes.
Network and access
Segmented so the warehouse tablet cannot reach the finance server, remote access that does not depend on one appliance, and a documented map of what talks to what.
Identity you control
The directory, the sign-in, the groups and the leaver process — running on infrastructure you own. This is the single most locked-in part of a modern company and the one nobody thinks about until they try to move.
Files, mail and collaboration
The everyday things, on open formats and portable protocols, so the archive stays readable and the migration path stays open. Boring on purpose.
An AI-native workplace
Assistance over your own documents, mail and processes, running where you decide, with a written policy and a log of what was asked and answered. The alternative is not no AI; it is unrecorded AI.
Managed support with an SLA
Response times by severity, a named engineer rather than a queue, and maintenance on a schedule. The obligations are in the contract, next to the exit terms.
What sovereign means for a forty-person company
Nothing political and nothing about hosting flags. It is four practical properties, and a company either has them or it does not. Most do not, and most have never checked — which is the reason the audit is the first thing we do and the reason it is worth having even if you then decide to change nothing.
- You can run it. Someone in your organisation could operate it, using documentation that exists, with credentials you hold.
- You can see the bill. What each part costs, what it would cost at twice the headcount, and what is being paid for twice.
- You can replace us. Another supplier could take over from what is written down, without archaeology.
- You can leave. With your data, your configuration and your identity directory, in a defined window and at a defined cost.
The AI part, without the pitch
An AI-native workplace is not an assistant bolted onto what you already have. It is the mail, documents and processes being structured well enough that an assistant can be useful over them — and the assistant running somewhere you chose, under rules you wrote. The uncomfortable half is that your staff started without waiting for either.
- Shadow use is the current state. Banning it produces the same usage with worse visibility, which is how most policies fail.
- A boundary beats a ban. Approved tools, defined data classes, and a written answer to what may leave the building.
- A log or it did not happen. What was asked, what was used to answer, and by whom — because the first serious incident will require reconstructing it.
- Drafts, not decisions. Anything reaching a customer or a payment stays a draft until a person approves it.
No client environments yet
An IT partner with no clients should say so, especially one asking to take over the systems a company runs on.
- Now
Our own estate, run properly
Everything described here, running for us and for a small number of reference environments, so the first client is not the first attempt.
- Next
First transformations
A few companies, chosen for fit rather than size, starting with the audit — including the ones where the honest recommendation is to change less than they expected.
- Later
Hardware and partners
The device side at proper scale, and other engineers trained on the same stack — because one supplier being the only source of support is the dependency we are arguing against.
Frequently asked questions
What is SovereOS in one sentence?
An IT partner that builds and runs the whole estate for a mid-sized company — devices, network, identity, workplace and support — on foundations the company owns rather than rents.
Does this replace our IT person?
No, and if a supplier tells you it does, ask who they expect to call them. The usual outcome is that the person stops being the only one who knows anything and starts doing the work only somebody inside the company can do.
Is this anti-Microsoft, or anti-cloud?
No. Plenty of arrangements with large vendors are perfectly portable, and plenty of self-hosted setups are not. The question is whether you could run it, price it, replace us and leave — which some products allow and some do not.
What happens to the licences we already pay for?
The audit prices them, including what you are paying for twice and what is being used by four people. Sometimes the conclusion is to keep them. A supplier whose audit always concludes replace everything is selling the conclusion, not the audit.
Where does our data actually live?
Wherever you decide — your own hardware, your own cloud account, or a provider you picked. What matters is that the decision is yours, recorded, and reversible, which is not true of most current arrangements.
What does an AI-native workplace mean in practice?
Assistance over your own material rather than a general chatbot: drafting from your documents, finding things in your archive, preparing routine work. Running where you chose, logged, with anything outbound staying a draft until somebody approves it.
What will it cost?
Not published yet, because quoting managed services before the first engagement would be a number invented to look credible. What is decided is the shape: priced per company and per scope rather than per user, so that hiring is not a licensing event.
Can we leave?
Yes, and how is written into the contract at the start: what we hand over, in what format, in what window and at what cost. On an estate this deep that clause matters more than any other, which is why it is agreed before the work begins.
Start with the audit, not the migration
The waitlist form goes live soon. Until then the blog explains what we would look at first, and when the answer is to leave things alone.
No form yet, no data collected — just come back.