Four ways through the site, in the order that actually helps.
This is a reading order rather than a library. Pick the path that matches the decision in front of you and read it top to bottom; each stop assumes the one before it, which is the whole reason for putting them in an order.
If you are assessing security or assurance #
Read these three, in this order
Start with how control is enforced, because it decides how much the rest matters. Then see how the boundary between what we operate and what you operate moves with the deployment pattern, and where the platform physically runs.
-
Trust and security
The four claims that carry most of a review, the structural properties behind them, what you are still holding if you leave, and the certifications we hold.
-
Deployment models
Where the line falls between what Agentycs operates and what your team does, pattern by pattern. Read it second, because it changes who owns which control.
-
Regions and residency
The one cloud we operate, where it is, and what sovereign deployment means everywhere else. This is the residency answer a review will ask for in writing.
If you are deciding where it can run #
Work outwards from the hardest constraint
Start at the extreme rather than the middle. If the platform holds with no connectivity at all, every less demanding pattern is a simplification of a case you have already understood.
-
Air-gapped
Fully disconnected operation, including model serving and software delivery, with the trade-offs each one carries stated rather than glossed.
-
Edge and remote sites
Inference next to the data, still governed by a core it may not always be able to reach, and what happens in the window where it cannot.
-
Agentycs in a Box
A six-litre micro server on 400 watts, carried in a backpack, running the whole platform on a full 96GB accelerator. Read it for sites where the infrastructure has to arrive with the team.
-
Managed sovereign cloud
The least demanding end of the range, read last: we run it, and you keep the control plane, the data and the models.
If you are going to build on it #
The shortest route to something you can run
The interfaces first, because they tell you how much of your existing tooling survives contact with the platform. The framework after, because that is the part that changes how you work.
-
APIs and protocols
PostgreSQL wire, Arrow Flight SQL, graph, REST, WebSocket and MCP, with a worked federated query rather than a feature list.
-
OpenAI-compatible API
Point the SDKs and agent frameworks you already use at models running on your own accelerators. Usually the fastest thing to prove.
-
Application Framework
Declare an application and have the platform generate, sign, attest and run it. Read once the interfaces make sense.
-
Architecture
The five layers underneath all of it, for when you need to know why a constraint exists rather than just what it is.
If you are still working out what Agentycs is #
Three pages, about twenty minutes
Most people arrive knowing the problem and not the shape of the answer. This is the shortest honest orientation, and it does not require you to learn seven product names first.
-
Solutions
Organised by the outcome you are buying rather than the component that delivers it. Start here if you can name the problem.
-
The platform
What each part does and how they compose into one system. Second, once you know which parts you care about.
-
Company
Who builds it, where, and how. Short, and the fastest way to work out whether we are a supplier you would take to a board.
Something a reading order cannot answer
Most evaluations reach a question that depends on your estate: a regulator, a datacentre, an existing model contract, a migration you cannot pause. Those are worth a conversation rather than a page, and you will be talking to the people who own the answer.
- Industries
- The operating constraints that shape a deployment in defence, government and regulated enterprise.
- Why we build this
- Ownership, sovereignty and independence from rented capability, and what we will not trade away to make the product simpler.
- Who builds it
- Two founders, and an account of how the software is written, reviewed and verified by a workforce of agents.