Your data stays where you put it.
Run the whole of Venom, the workspace and the model endpoint, in your own cloud account or on your own servers, with the network unplugged if you need it. Nothing leaves without a key and a routing rule you set.
Community, the self-hosted tier, has no licence fee at any size.
What it looks like today
- Legal won't sign off on a tool that sends prompts and customer records to a vendor's servers.
- Your notes, tickets and contacts live in five clouds, under five sets of terms that can change.
- Nobody can say which hosts an AI agent talked to last week, or prove what it did.
- The site that matters most has no internet connection at all.
Three ways to run it
The software is the same in all three. Where you run it decides where the data lives.
- Venom CloudIn Venom Cloud's database, one organisation apart from another. Your GPUs stay yours: a daemon dials out and keeps its models and provider keys on your machine. Docs
- Your cloud accountIn your own database, in your AWS account from one CloudFormation stack, or on any Kubernetes cluster with the Helm chart. It keeps running if you stop paying. Docs
- Your servers, or air-gappedOn hardware you control, from one installer or Docker Compose. The air-gapped bundle is built once on a connected machine, checked by checksum and signature, and carried across. Docs
Everything inside your boundary
The control plane, the database and the models run on your side. The only ways out are a cloud provider you give a key to, and Venom Cloud if you connect a daemon to it. Both are off until you open them.
Your network or cloud account
Control plane and apps
Your Postgres
Daemons and models
A cloud provider
Venom Cloud
What is true today
Each line links the page of the docs that shows it.
- One command checks a Linux server, generates the secrets and starts Venom Cloud with HTTPS, backups and upgrades.docs/deploy/install-server
- The air-gapped bundle installs with checksum and signature checks on a machine with no network.docs/deploy/airgap
- No telemetry and no update checks. The daemon's auto-update is a switch that stays off until you turn it on.docs/getting-started/choose-how-to-run
- The test suites run in a container with the network cut, so a new outbound call fails the build.docs/cookbook/offline-ollama
- Every host a session reached through bash, the browser, web tools and MCP, with new ones flagged.docs/security/egress
- A hash-chained audit log you can verify, a signed log of every command and file write, and offline audit exports.docs/security/audit
- Secrets the agent uses by name without ever seeing the value, each bound to the origins it may reach.docs/security/secrets
- Single sign-on with Okta, Entra ID, Google or any OIDC or SAML provider, groups mapped to roles, and SCIM.docs/cloud/console-sso
Security on Venom Cloud too
If you use the hosted cloud, it routes and keeps metadata, and the rest stays where you put it.
Daemons only dial out
A daemon opens a connection to the cloud and takes work over it. No inbound ports, no VPN, and its provider keys stay on the box.
Keys sealed at rest
Provider keys in the vault are sealed with AES-256-GCM under a per-organisation key derived from rotatable master keys, and opened only on the server to serve a request.
Content logging is yours to turn on
By default the cloud keeps who, which model, where, tokens, cost and latency. Prompt and response logging is off unless the operator turns it on, at most 90 days, sealed, with every read audited.
Organisations kept apart
Every console query is filtered by your organisation, every action checks one permission matrix, and tests cover cross-organisation access being refused.
No telemetry
The venom CLI turns off update checks and telemetry, the orchestrator calls only the upstreams you configure, and this site loads no analytics.
Guardrails in layers
Content, routing, model, tool, spend and answer rules at the organisation, key group and member level, plus a prompt-injection shield.
A licence that costs nothing to start
Community is the self-hosted tier: you run the workspace and the orchestrator yourself, at any size, with your own models, and pay no licence fee. A paid plan buys support and governance, and if you want it, someone to operate your deployment for you.
- BYOC, managed by Venom in your AWS, GCP or Azure account: from $999 a month on top of the plan
- Private or on-prem, managed with the access you grant: from $2,500 a month on top of the plan
- Your cloud or hardware bill stays yours, paid directly
Questions people ask first
What can Venom see?
How do updates reach a self-hosted install?
Is the source open?
Does it work with no internet at all?
How do I leave?
Run it on your side of the line
One command on a Linux server, a CloudFormation stack in your AWS account, or the air-gapped bundle.