Government and public sector
Accountability for citizen data does not transfer to a supplier, so neither can the platform.
The operating reality #
A public body remains answerable for where citizen data lives, who processed it and why a decision went the way it did. Procurement adds a second constraint that is easy to underestimate: capability has to be explainable, auditable and exitable, not a standing dependency on one supplier's roadmap and pricing.
The dependency is worth naming precisely, because it is a mechanism rather than a mood. Adoption is cheap while it is optional. Integration deepens until the data model, the identity estate and the skills are all shaped around one set of interfaces. Only then is the price set, and by then leaving is quoted as a rebuild rather than a migration. A state that has arranged its administration this way has handed a commercial supplier, operating under another country's law, a say in whether it can govern.
The consultancy version of the same trap is quieter. An engagement that ends with the supplier holding the knowledge, the code and the operating capability has not transferred anything. It has sold a subscription that looks like a project.
At the same time, the delivery backlog is usually the real blocker. Services that citizens need are years out because there is no capacity to build them, and hiring cannot close a gap of that size. The interesting question is not whether AI can draft a letter. It is whether the department can ship the service that letter belongs to, and own it afterwards.
An exit strategy that exists only in a contract is not an exit strategy.
What that requires of the platform #
- Residency is a deployment choice rather than a support request: sovereign cloud, your own cloud account, your own datacentre or on-premises.
- Federate the identity provider you already run, and keep membership current automatically through directory synchronisation, including Microsoft Entra and Google directories.
- Every access decision resolves through one audited authorisation path, so an audit trail is a property of the platform rather than a reporting project.
- The interfaces you build against are standards, which is what makes an exit strategy credible instead of contractual.
- An autonomous software factory turns a small team's intent into shipped, tested services, so delivery capacity is transferred to your department rather than rented back to it indefinitely.
Read next #
AI software delivery
How intent becomes shipped, tested and observed software without a hiring round.
Enterprise search and RAG
One question answered from everything you hold, under the asker's own permissions.
Where it can run
The UK sovereign cloud, and the on-premises model everywhere else.
Deployment patterns
Every pattern compared, including who operates what in each one.
Start with the service you cannot staff
Bring a service that is years out because there is no capacity to build it, plus the residency rule and the identity estate it has to fit inside. We will map what the platform looks like around it.
Agentycs is pre-revenue and signing its first deals with its first customers. There are no departmental references to show yet, and we would rather say so than write a sentence designed to imply otherwise.