Skip to content
Docs menu

Products

Every Venom product in one page, what each is for, its MCP endpoint and whether it is an add-on, from the workspace apps to the CLI, the orchestrator, the desktop daemon and the editor clients.

View .md

Venom is the agent-native operating layer you own: one workspace for your team, priced on usage and outcomes instead of seats, running on models and machines you choose, and still working when a provider fails or raises its prices. It runs in Venom Cloud, in your cloud or on your servers, and the products on it share one set of things underneath: roles and policy, memory, model routing, budgets, and an audit trail. People and agents work in the same apps, so an agent that files a task, answers a ticket or rolls out a flag does it under the same permissions as a person, and the action lands in the same log.

Where you run it decides where the data lives. See Choose how to run Venom.

Workspace apps

The apps share one rail and one ⌘K search (see the workspace). Each has its own MCP server, so an agent connects only the products it needs and its context holds only their tools. Every endpoint is https://cloud.usevenom.dev/workspace/mcp/<name> on Venom Cloud, and the same path on your own deployment. The MCP overview covers sign-in and scopes.

Every app here can also be built on: each has MCP tools, REST routes and webhook events, listed on its developer page in Build with Venom.

Add-ons are products an organisation switches on. While an add-on has no price set on a deployment it is in preview: every organisation has it and there is nothing to buy.

Notes (Venom Notes)

Shared markdown notes with [[wikilinks]], databases, a graph, sharing and publishing. MCP: /workspace/mcp/globe. Add-on. Docs.

Tasks

Issues, projects, cycles and views for people and agents, with work delegated to an agent. MCP: /workspace/mcp/tasks. Add-on. Docs.

People and Funnel

People is your own relationships: who someone is, how you met, when you last spoke. Funnel puts deals, pipelines and a forecast on top of it. MCP: /workspace/mcp/people and /workspace/mcp/funnel. Not add-ons. People, Funnel.

Support

A shared inbox for customer email and form requests, with notes and replies drafted from your notes. MCP: /workspace/mcp/support. Not an add-on. Docs.

Chat

Team chat where people and agents are both members: channels, direct messages, threads. MCP: /workspace/mcp/chat. Not an add-on. Docs.

Forms

A form builder with logic, links to share, and responses sent where the team works. MCP: /workspace/mcp/forms. Add-on. Docs.

Flags

Feature flags with environments, targeting and percentage rollouts, each change reviewed before it saves. MCP: /workspace/mcp/flags. Add-on. Docs.

Experiments

A/B tests on flags, with sequential results, sample ratio checks and guardrails. MCP: /workspace/mcp/exp. Add-on. Docs.

Incidents and Status pages

Incidents is error tracking for your own apps, grouped by cause, with the flag and the release in hand, plus alerts and on-call. MCP: /workspace/mcp/incidents. Add-on. The Status page publishes uptime from your own checks, with maintenance windows and subscribers. MCP: /workspace/mcp/status. Incidents, Status page.

Comms and Venom Line

Comms is one API for SMS, WhatsApp, RCS, Telegram and phone calls through your own provider account, with opt-outs and quiet hours. Venom Line is an AI voice agent that answers your number. MCP: /workspace/mcp/comms. Not an add-on. Comms, Venom Line.

Calendar

Your calendars and booking pages: .ics feeds, schedules, event types, free times, booking links and bookings. MCP: /workspace/mcp/calendar. Docs.

Org and Admin

Org is the organisation's teams and subteams with their members and roles, shared by every product. Admin is the console's admin pages (members, keys, budgets, routing, webhooks, audit and more) as tools. MCP: /workspace/mcp/org and /workspace/mcp/admin. Teams, Build on Admin and the mesh.

Voice

Speak to venom and have it answer, through your own speech models or cloud ones, behind one OpenAI-shaped audio API. No MCP endpoint. Docs.

Agents and builders

The venom CLI and its harness

The venom terminal coding agent, with a permission engine, an OS sandbox on macOS and Linux, subagents and plan mode. The harness is the same agent as a library (@venom/harness) for your own app. Free and MIT licensed. CLI, harness.

venom serve

The harness sessions over HTTP and Server-Sent Events, so an app in any language can create sessions, stream events and answer approvals. Docs.

Editor and browser clients

  • VS Code: a chat panel over venom serve, with approvals and per-hunk undo. Docs.
  • Zed and other ACP editors: venom acp serves venom as an Agent Client Protocol agent on stdio. Docs.
  • Chrome and Edge: venom --chrome-extension lets the agent use your own logged-in browser through an extension. Docs.
  • Claude Code: a plugin that sends each finished session, redacted on your machine, to your own cloud. Docs.

Infrastructure

The orchestrator and gateway

A self-hosted OpenAI-compatible gateway in Go in front of vLLM, SGLang, llama.cpp, Ollama and the cloud providers you allow, with fallback, session-sticky routing and usage kept in SQLite. Docs.

The desktop daemon and the mesh

venom-daemon runs the orchestrator on a desktop or GPU box without Docker. In mesh mode it dials out to Venom Cloud, so your GPUs serve your team while provider keys stay on the machine. Daemon, Mesh.

Plans

Billing is a flat fee per organisation plus metered usage, never per seat. See Organisation settings for the plans and what is metered.