Skip to content

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 Cloud
    In 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 account
    In 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-gapped
    On 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

The workspace, the console and the endpoint, from one installer, Docker Compose, Kubernetes or a CloudFormation stack.

Your Postgres

Workspace data, request logs and provider keys sealed under your own master key.

Daemons and models

vLLM, SGLang, llama.cpp or Ollama on your GPUs. With no cloud key set, no request leaves.

A cloud provider

Only with your key and a routing rule that allows it.

Venom Cloud

Only if you connect a daemon to it. The daemon dials out and opens no inbound port.

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?
On your own cloud or servers, nothing, unless you connect a daemon to Venom Cloud yourself. On Venom Cloud, the workspace data you put in it and your request logs, because they live in its database. Prompts pass through in relay mode and go straight to your daemon in direct mode, and provider keys you give a daemon never leave it.
How do updates reach a self-hosted install?
You choose when. The desktop daemon has an auto-update switch that is off until you turn it on, and it makes one request for a checksum file per check. For servers, you pull a new release and roll it out the way you roll out any service.
Is the source open?
The workspace and the control plane are the product you run or buy: their source repository is private today, and you run the released builds. The venom CLI is free and MIT licensed.
Does it work with no internet at all?
Yes, with local models. Build the air-gapped bundle on a connected machine, carry it across, and bring your own model files. The venom CLI and the orchestrator then make no outbound calls.
How do I leave?
On your own cloud or servers there is nothing to leave: it keeps running, and your data is in your database. On Venom Cloud, the console and the admin API export your data.

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.