Skip to content

Everything a team works in, and what runs it

Add-ons are in preview and included until they have a price.

The workspace

What your team works in. Each product has its own MCP server, so an agent connects only the ones it needs.

The full list, with MCP endpoints and add-on status, is on the Products page of the docs.

Your data stays where you put it

The same software runs in our cloud, in yours, or on your own servers. Nothing leaves without a key and a routing rule you set.

How sovereignty works

  • Run it where you choose

    Venom Cloud, your own AWS account from one CloudFormation stack, a Kubernetes cluster, or a Linux server from one command.

    docs/getting-started/choose-how-to-run
  • Air-gapped if you need it

    Build the bundle on a connected machine, check it by checksum and signature, and install it where there is no network.

    docs/deploy/airgap
  • No telemetry, and tested that way

    No update checks or analytics, and the test suites run with the network cut so a new outbound call fails the build.

    docs/cookbook/offline-ollama
  • Every action on the record

    A map of every host a session reached, a signed log of every command and file write, and keys sealed in your vault.

    docs/security/audit

Your models and any provider, behind one endpoint

The workspace's agents and your own apps call one OpenAI-compatible URL. Behind it sit your GPUs and the providers you choose, and when one fails, the next target in the route answers.

Your clients

Any OpenAI SDK, the venom CLI, editors and agents.
  • /v1/chat/completions
  • /v1/responses
  • /v1/embeddings

One endpoint

Venom Cloud, or the orchestrator on your own server. It keeps a session on the backend that holds its prompt cache, checks each key's budget, logs every request and moves to the next target before the first byte when one fails.

Your GPUs

Daemons that dial out from your machines.
  • vLLM
  • SGLang
  • llama.cpp
  • Ollama

Providers on your keys

Several keys per provider, tried by priority.
  • OpenAI
  • Z.ai
  • Qwen
  • TypeSafe

Public nodes you allowlist

Optional. Checked by audits and measured on real jobs.

Run your own model meshOr put your idle GPUs on the public mesh

Your team grows. Your software bill doesn't have to.

From $249 a month for the organisation, with unlimited collaborators and agents. On top you pay for the inference, messages and storage Venom supplies; your own keys and GPUs add nothing. Start free with 2 daemons and 10,000 requests a month, no card needed.

Questions people ask first

What is Venom, in one line?
A workspace for your team (notes, tasks, chat, calendar, CRM, support, forms and incidents) that people and agents both work in, on a model layer you control, priced per organisation and by usage, never by the seat.
What is open source?
The venom CLI is free and MIT licensed, and it builds on pi, which is MIT too. More on the CLI. The workspace and the control plane are the product you run or buy: their source repository is private today, and Community, the self-hosted tier, has no licence fee.
What can Venom see?
On Venom Cloud, the workspace data you put in it and your request logs, because they live in its database. Provider keys you give a daemon never leave it. On your own cloud or servers, Venom sees nothing unless you connect a daemon to Venom Cloud yourself.
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, and any OpenAI client only needs a different base URL.
Can I get paid for hosting GPUs?
Not yet. The cloud already counts what a public node earns at its listed price, but payouts to hosts are a later phase. Join the host waitlist on the hosting page and we will tell you when they open.

Start with one team and one tool

Sign up free, bring one tool's data over, and invite the people and agents who use it. Running a larger organisation? Talk to us.