Self-hosted and control
It runs where you say, at the version you chose.
Self-hosted is a word a lot of products use loosely. Here is exactly what it means here, because for most buyers this is the part that decides it.
Self-hosted, plainly
| Runs where | Your servers, your network, your storage. One signed image; the deploy verifies the digest before it starts. |
| Data at rest | Stays local. Run bundles are envelope-encrypted; credentials live in the vault, never in the image. |
| Model access | Your provider account, under your terms. Keys are injected at the egress gateway and never enter a prompt. |
| Outbound traffic | Allow-listed per vendor. Platform essentials plus the hosts the active packs declare; everything else is denied. |
| Multi-tenant | A repository, a ledger and a spending ceiling per tenant. A workspace cannot read across the boundary. |
What you hold
You hold the image.
Self-hosted is a word a lot of products use loosely. Here is exactly what it means, because for most buyers this is the part that decides it.
The software is in your hands
- You hold a copy of the signed image. It is yours to keep, in a registry you control.
- Deploys are pull-based. Your node pulls the version you point it at. Nothing we do reaches your infrastructure unless you go and get it.
- You choose when it changes. Pin a version and stay there for as long as you like; the node verifies the digest before it starts, so you know what you are running.
- No phone-home, no licence server, no remote switch. There is nothing in the product that has to reach us for it to start, and nothing that can reach in and stop it.
The work is in your hands
- Your data is on your storage. Files, plans, transcripts, deliverables and the ledger all live in your systems.
- The content store is git. Standard tooling, readable without us, portable the day you want it elsewhere.
- Model access is your account. Your contract with the provider, your terms, your spend.
- Your specialists are files. A forged specialist is a document with a hash, in your workspace, that you can read and keep.
The short version: a deployment keeps running on your terms, at the version you chose, whatever else happens. That is a property of how it is built, not a promise in a contract.
Next step
See it on your own node.
We walk the console, open the posture view against a real deployment, and answer whatever your reviewer sends back.
Write to the assistant inbox
assistant@agenticensemble.ai