
Run Argent where your data lives
Argent Strategic Intelligence installs inside an environment you control: on your own servers with no internet, in your private cloud, or in your own AWS, Azure or Google Cloud account. One signed release, the same controls, three ways to run it.
One product, three places to run it
Argent is the gateway between your AI agents and the AI models they use. It checks each request, records it on a signed record, and stops what your policy forbids. In every option below, that gateway runs inside your environment, and so do its records.
Where AI runs is now a buying question in its own right. Gartner forecasts worldwide sovereign cloud infrastructure spending of $80 billion in 2026, up 35.6% from 2025 (Gartner, February 2026).
- [Air-gapped on-premises](/platform/deployment/air-gapped-on-prem/): your own servers, a network with no internet. The release is carried in on removable media.
- [Private cloud](/platform/deployment/private-cloud/): infrastructure only your organization uses, in your data center or a dedicated cloud, connected where you allow it.
- [Public cloud VPC](/platform/deployment/public-cloud-vpc/): your own AWS, Azure or Google Cloud account, inside a network you define, with the cloud's managed services if you want them.
The three options side by side
Pick the column that matches your network. The checks Argent runs on each request are the same in all three.
| Air-gapped on-premises | Private cloud | Public cloud VPC | |
|---|---|---|---|
| Where it runs | Your servers, in a sealed network | Your data center or a dedicated cloud | Your AWS, Azure or Google Cloud account |
| Internet | None | Where you allow it | Where you allow it |
| How the release arrives | One signed bundle on removable media, checked and loaded into your registry | From the Nyedis registry with signatures checked, or from your own mirror | From the Nyedis registry, or mirrored into your cloud registry |
| Install with | Helm chart (self-hosted profile) or the single-server bundle | Helm chart (self-hosted profile) or the single-server bundle | Helm chart with a profile for Amazon EKS, Azure AKS or Google GKE |
| Database, cache, secrets, evidence | All inside your install | All inside your install | In your cluster, or your cloud's key service and locked storage (plus Aurora and ElastiCache on AWS) |
| AI models | Local engines such as Ollama, LM Studio and vLLM | Local engines, plus outside providers you approve | Cloud providers such as Amazon Bedrock, Azure OpenAI and Google Gemini, plus any you approve |
| Updates | The next signed bundle, by media | The next signed release | The next signed release |
What is the same in every option
Every way of running Argent is built from one signed release manifest, so the image digests agree and no form factor ships different bytes.
- The same gateway. It knows which agent sent each request and which person owns that agent, and checks every request that works through Argent against your policy.
- The same signed records. Each decision is written to a signed, tamper-evident record, and the archive is kept on object-locked storage you choose.
- The same console. It loads only from your install.
- The same rollout. Start in watch mode, where Argent records what it would have done while nothing is stopped, then turn on enforcement area by area.
- No provider keys in agents. The gateway holds the real keys, resolved from your vault, and agents carry only an Argent key, in a public cloud they can carry none at all and sign in with their own cloud identity. See keyless agents.
- Two doors. On Kubernetes only the gateway and the console face the network; the chart's network policies keep everything else inside the cluster, where the cluster's network plugin enforces them.
- Evidence anyone can check. An auditor checks the evidence package on their own machine, with no call to Nyedis. See one-click audit evidence.
How to choose
Four plain questions settle it.
| If your answer is... | Start with |
|---|---|
| The network has no internet, by design | Air-gapped on-premises |
| We run our own Kubernetes or servers, and keep data in our own data center | Private cloud |
| Our workloads and AI models already live in AWS, Azure or Google Cloud | Public cloud VPC |
| We want a quick pilot on one machine first | The single-server bundle, in any of the three |
Every option installs the same signed release, so a pilot on one machine and a production cluster run the same images.
How long an install takes
These are measured runs, start to every service ready.
| Where | Measured |
|---|---|
| AWS, fresh account | Eleven runs took 17.7 to 35.1 minutes, a median of 28.9 |
| Azure | Every service ready at 16.5 minutes (one run) |
| Google Cloud | 21 and 23.4 minutes from creating the project to ready (two runs) |
| One server | Serving 100 seconds after unpacking, with images already in a private registry |
An air-gapped install adds the time it takes to carry in and load the bundle.
Where to go next
Each option has its own page. These take it further.
- Options: air-gapped on-premises, private cloud and public cloud VPC.
- Capabilities: Air-Gapped Install, Model Control, Sensitive Data Redaction, Keyless Agents and all capabilities.
- Goals: sovereign AI, compliance evidence, see all AI in your company and all goals.
- Use cases: AI in regulated and air-gapped environments, securing AI coding agents and rolling out copilots and chat safely.
- Industries: Financial Services, Public Sector, Healthcare and all industries.
- Connects to: your AI providers, identity directory and vault. Browse our integrations.
- See it yourself: take the walkthrough or download the data sheets.
Download files
- PDFArgent Air-Gapped On-PremisesOne-page data sheet: what runs on your servers, how the signed bundle is checked, and how a team starts.
- PDFArgent Air-Gapped InstallOne-page data sheet on the air-gapped install capability.
- PDFArgent Sovereign AIOne-page data sheet: keep the checkpoint, the data and the evidence where you put them.
Want this running on your own use cases?
All downloads