
ARGENTAIR-GAPPED ON-PREMISES
Master Control System · by Nyedis
Some networks are sealed on purpose
An air-gapped network has no connection to the internet. The NIST glossary defines an air gap as an interface where two systems "are not connected physically" and data moves "only manually, under human control."¹
Organizations keep their most sensitive systems this way so that private data and intellectual property cannot leave. The engineers inside still want AI agents working on internal code and documents.
- Every agent request needs to be checked and recorded, by something that runs inside the sealed network.
- A tool that must reach a vendor's server to start, update or check in cannot be approved there.
- The evidence has to stay inside too, where the security team and the auditors can reach it.
The air-gapped on-premises option puts all of Argent on your own servers. Nothing it needs lives outside.
What runs on your servers
Argent Strategic Intelligence is the gateway between your AI agents and the AI models they use. In this option every part of it runs on hardware you own, inside the sealed network.
| Part | What it does on your servers |
|---|---|
| The gateway | Every agent that works through Argent sends its requests here. It knows which agent sent each one and which person owns that agent, checks the request against your policy, and passes it on or stops it. |
| Signed records | Each decision goes on a signed, tamper-evident record. The evidence archive sits on its own object-locked store inside the install. |
| Sensitive-data detector | Ships in the signed release with everything it needs built into its image, so it makes no outside lookup. |
| The console | Loads only from the install. Every build is scanned and fails if the console would request anything from another site. |
| The data tier | The self-hosted profile runs the database, the cache and the secrets store in your cluster, beside the evidence store. |
| The AI model | Can live inside too. Routes can point at local engines such as Ollama, LM Studio and vLLM, each turned on by an admin. |
Argent needs no AI model of its own to do its job. The few features that use one are optional, and your team picks the model, even a local one.
Two ways to install: a cluster or one server
Both come from the same signed release, so the same images run either way.
| Kubernetes cluster | Single server | |
|---|---|---|
| What it is | One Helm chart for Kubernetes 1.34 or newer, with a self-hosted profile for clusters such as k3s and RKE2 | One bundle for one Linux host, with no repository to clone |
| Before it starts | The chart refuses to render if an image is missing from the release | A host check ends in PREFLIGHT OK, or PREFLIGHT FAILED with the check that failed |
| Secrets | The self-hosted profile runs the secrets store inside your cluster | Generated on the box for each install and never printed |
| Can grow with demand | With KEDA in your cluster and autoscaling turned on, extra gateway copies start when more agents send requests and go away when things quiet down | One host |
| Good for | Production | A pilot or a single-host site |
Only two doors face the network on Kubernetes: the gateway and the console. The chart's network policies keep everything else inside the cluster, where the cluster's network plugin enforces them.
Measured: on one cloud server, the single-server bundle was 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.
Carried in, checked, then installed
No download and no update service. The release arrives as one signed bundle on removable media, and your own team runs the checks on your side.
- Carry it in. The bundle holds every container image with its signature, software bill of materials and build provenance, plus the trust keys, a checksum list, the import script, the Helm chart and the single-server bundle.
- Check the signature. The import checks the release signature against the Nyedis release key.
- Check every file. The signed release must pin this bundle's checksum list, and every file must match it.
- Check every image, then load it. Each image must match the digest the signed release pins. It is copied into your own registry and its signature is verified there. Any mismatch prints
FATAL:and stops. - Install from your registry. One setting points the install at it:
global.imageRegistryfor the Helm chart, orARGENT_REGISTRYfor the single-server bundle. - Update the same way. The next release arrives as the next signed bundle and goes through the same checks. The database migrates itself on start.
The import prints one banner per check and ends with OK: bundle verified and loaded into your registry. See the full chain on Air-Gapped Install.
What leaves the network, and who decides
NIST SP 800-53 control SC-7(5), required for US federal systems at moderate and high impact, denies network traffic by default and allows it by exception.² Argent fits that posture: its own services open no outside connection by default.
| Connection | Default |
|---|---|
| Agent requests to an AI model | Go only where your routes point: a model inside the network. |
| Model price feed | Off. Runs only if an operator turns it on, and new prices then wait for an operator to approve them. |
| Connectors (identity directory, alerts, vault) | None at install. Each exists only when an admin adds it, and an allowlist can make connector traffic deny-by-default. |
| Console | Loads nothing from another site. Fonts and the world map are bundled. |
| Certificates and tracing | A local certificate, no public certificate authority. Traces go to the collector inside the install. |
| Evidence archive | Stored inside the install, on its own object-locked store. |
Need outside AI providers as well? The same install with a controlled way out is private cloud; see model control.
Day two: records, evidence and updates
Once it runs, the sealed site works like any other Argent install, from the same console.
- Each request: its signed record, allowed or blocked, with the agent, its human owner and the reason. Local models are metered too, at a cost of zero.
- Sensitive data: a request carrying a customer's Social Security number can be masked or blocked before it reaches the model. See sensitive data redaction.
- Evidence: hand an auditor a package with one-click audit evidence, checkable on their own machine, or replay what an agent did with session replay.
- Rollout: start in watch mode, which records what Argent would have done while nothing is stopped, then turn on enforcement.
- Updates: the next signed bundle, the same checks, and the same one setting. The console shows which Argent controls are installed and running.
Where it fits, and how a team starts
Air-gapped on-premises is the strictest of the three ways to run Argent. Compare it with private cloud and public cloud VPC on the deployment options page.
- Goals: sovereign AI, compliance evidence, audit and accountability, data loss prevention and all goals.
- Use cases: AI in regulated and air-gapped environments, securing AI coding agents and controlling agent tool access.
- Industries: Public Sector, military and defense, Financial Services, utilities, Healthcare and all industries.
- Carry in and check. Bring the signed bundle across, run the import, and load your own registry.
- Install and route. Point the chart or the single-server bundle at your registry, then point your agents at the gateway and your routes at local models.
- Watch, then enforce. Start in watch mode, then turn on enforcement. Take the walkthrough or browse all capabilities.