# Running agents air-gapped
2026-10-28. How Hexel Studio runs in networks sealed from the internet: one signed offline bundle you verify, an offline licence, local models and a record you can check.
Source: https://www.hexelstudio.com/blog/running-agents-air-gapped
Published 2026-10-28 · By Hexel Studio
Some networks never touch the internet. How Hexel Studio gets in, runs and keeps an honest record there, without a single call home.
An air-gapped network is the simplest security policy there is: nothing gets in or out over a wire. It is also the hardest place to run modern software, because so much of it assumes a connection. Licences call home to check themselves. Installers pull images from the internet. Models live behind someone else’s API. Audit logs ship to someone else’s cloud.
Running agents in a sealed network means removing every one of those assumptions, and replacing trust in a connection with trust you can check by hand.
## One bundle, carried in
Titan and Atlas each ship as a single offline bundle. It holds every container image the install needs, each an exact copy pinned by its digest, along with the chart or manifests, the installer and a record of every image in the release. Nothing is fetched at install time.
Atlas’s bundle brings its own dependencies: Qdrant for vectors, Neo4j for the graph, PostgreSQL, Kafka and Redis, and, when you want models inside the wall, vLLM to serve them and TEI for embeddings. Titan’s brings its services and its install tool. Either way, the bundle is the whole of what crosses the gap.
## Verify it before it crosses
A bundle you can’t verify is a bundle you have to trust, so every one can be checked with standard tools. The checksums of every file are signed keyless with Sigstore by our release workflow, and you check them with cosign before anything is unpacked. The installer then checks the release record and the digest of every image.
Images carry their own signatures and SBOMs, so you know exactly what software, at what version, you are about to run. The bundle is reproducible, so the one you verified is the one that runs. Then the images go into your own registry and the install is rendered against it. From that point on, your cluster pulls only from inside.
## A licence that never calls home
Licensing is often the quiet phone-home in enterprise software. Titan’s offline licence is a file we sign, naming the organizations it covers, the edition, an expiry and what it permits. Your install checks the signature locally, against keys built into the software. There is no licence server and no periodic check-in.
Usage leaves the same way. Atlas packs its local usage log into a file that you export and hand over, on your schedule. Nothing is sent.
## The record stays inside, and stays true
An air gap doesn’t excuse anyone from knowing what their agents did; it usually raises the bar. Titan’s Agent Ledger is hash-chained: each entry carries the digest of the one before it, so a changed or missing entry breaks the chain, and anyone with the entries can check it.
For long-term retention, Titan’s audit sink writes to storage you hold: S3 with object lock, or append-only, hash-chained files on a write-once volume, with every batch sealed by a signed checkpoint. A public key verifies the whole store, offline, years later. And if the sink stops accepting entries, side effects stop rather than run unrecorded. In a sealed network, an action without a record is worse than no action.
## Models inside the wall
Agents need models, and in a sealed network the models have to live there too. The Atlas bundle can carry vLLM and a text-embeddings server, so the same pipeline that parses, embeds and searches your documents in the cloud does it on hardware you own. Atlas points at your models, your object storage, your keys and your identity provider, set in its values, and reaches nothing else.
## Not a separate edition
None of this is a cut-down product. Titan’s on-prem install starts from the same template as the dedicated instances we run in our own cloud, and changes only what a customer’s cluster needs. The policy engine, the ledger, the grants and the kill switch are the ones every other install uses.
What changes is where the trust comes from: not from a connection to us, but from signatures you check yourself. The steps fit on a card. Verify the bundle, push the images to your registry, write your values and secrets, apply. Everything after that happens inside your walls.
---
Hexel Studio · https://www.hexelstudio.com · Index for agents: https://www.hexelstudio.com/llms.txt