United Kingdom
The United Kingdom is the one place Agentycs operates the cloud itself.
What this means #
The United Kingdom is where Agentycs operates a sovereign cloud of its own. An instance placed there has its accelerators, database tier, object storage and model artefacts in the UK, and requests are routed to it, served by it and recorded by it. There is no upstream model host in another jurisdiction quietly completing the work.
United Kingdom government and the organisations that serve it are who we build for first, and that sets the standard the rest of the platform is held to. Placement is only the first half of the decision; authority is the second. You choose whether we operate the instance or you do, whose identity provider authenticates people, whose vault holds the secrets, and whether tenant policy permits a request to leave the cluster at all.
What you decide #
- Operator
- Managed by us in our UK cloud, run by you on infrastructure of your own, or run by you with our platform team alongside under access you grant.
- Deployment pattern
- All eight, from a managed sovereign instance through private cloud and on-premises to fully air-gapped and the six-litre micro server.
- Zones
- Single-zone to start, expanding in place to multiple zones for replication and survivable site loss.
- Storage backend
- Platform-operated S3-compatible storage, or your own S3-compatible bucket, chosen per tenant.
- Key custody
- The instance's own vault, or brokered access to a vault you already operate.
- External model access
- Off by default. Enabled per tenant, per provider, if and when you want it.
What follows from it #
These are consequences of the placement rather than promises about it, which is the difference that matters under review.
Data rests where you put it #
Tenant datasets rest in the storage backend and zones you nominated. Hot writes are buffered in the instance's own database and flushed to its own lakehouse, both inside the same boundary.
Inference runs in the United Kingdom #
Models are served from accelerators in the instance. Whether an external provider may ever serve a request is a per-tenant policy decision, enforced before dispatch and recorded either way.
Identity stays yours #
Sign-in federates to your own OIDC provider. Sessions, bearer tokens and capability tokens are minted by the instance, and membership is provisioned and de-provisioned from your directory.
Every access is on the record #
A redacted audit ledger correlates each read and privileged action to the identity and query behind it, so a question about who saw what has an answer rather than an estimate.
Where to go next #
Choose a deployment pattern
Managed, private cloud, on-premises, air-gapped, edge, multi-site, hybrid or a box.
Continue →Deploy it in your own country
What in-country sovereign deployment looks like outside the UK, starting with Europe.
Continue →Trust and assurance
The controls behind isolation, key custody, provenance and audit, and how they are assured.
Continue →