Skip to content

Octavo for your whole organization.

Give every engineer the same agent, and decide who signs in, which models they use and where agents run.

Govern every agent. Choose the models and tools agents can use, and the rules they follow.

  • Model and MCP allowlists for the whole organization.
  • Org-wide rules, synced from the admin dashboard.
  • Role-based admin, usage analytics and spend limits.

Keep code private. Privacy Mode is enforced across the organization by default, so no engineer has to turn it on.

  • Octavo never stores your code, and neither Octavo nor model providers train on it.
  • Model providers work under zero-data-retention agreements.
  • The index keeps embeddings and obfuscated file paths, never plain-text code.

Run agents in your own cloud. Self-hosted cloud agents run inside your VPC, with your repository, dependencies and tools.

  • Each agent runs in its own isolated VM.
  • Many agents can work at the same time.
  • Each task comes back as a pull request with test results.

Security and access controls.Enterprise includes every control below.

  • SAML/OIDC SSO

    Engineers sign in through your identity provider with SAML or OIDC.

  • SCIM provisioning

    Members are added and removed from your directory, so access ends when someone leaves.

  • Audit logs

    See who changed which setting, model or member, and when.

  • Privacy Mode

    On by default for every member, and shown as enforced in the admin dashboard.

  • Zero data retention

    Model providers handle requests under zero-data-retention agreements and keep none of your code.

  • Encryption

    Data is encrypted in transit with TLS 1.2+ and at rest with AES-256.

  • Data residency

    Keep your organization’s data in the US or in the EU.

  • Model and MCP allowlists

    Admins choose which models and MCP servers members can use.

  • Self-hosted cloud agents

    Cloud agents run in isolated VMs inside your own VPC.

How companies start. From a first call to every engineer on Octavo.

  1. 1Talk to sales

    See Octavo on work like yours.

    Request a demo. We walk your team through Octavo and answer your security team’s questions.

  2. 2Pilot

    Start with one team.

    One team uses Octavo on your repositories, with SSO and Privacy Mode enforced. Usage analytics shows how it went.

  3. 3Roll out

    Add every engineer.

    Your security team approves the build, admins invite engineers or SCIM adds them, and your policies apply from the first sign-in.

From the leaders who rolled it out.

  • Ashcombe Mutual

    “We piloted Octavo with two teams, then rolled it out across claims. Our project rules carry our logging and error-handling conventions, so pull requests from cloud agents already look like ours. Engineers start small fixes from Slack with @Octavo and watch the recording before they open the diff.”

    Adaeze NwosuSenior Engineering Manager
  • Norrhaven Bank

    “Our auditors ask where code runs and who can reach it. Cloud agents run in our own VPC, Octavo keeps our data in the EU, and SCIM removes access the day someone leaves. In CI, octavo -p reads failed builds and proposes a fix, and a platform engineer reviews it.”

    Declan ByrneDirector of Platform Engineering
  • Wexcombe Health

    “Privacy Mode, enforced for every seat, was our first requirement. Octavo Review now runs as a required check on every repository with patient records. It flagged an endpoint that returned another clinic’s appointments when the ID changed, and the comment came with a suggested fix.”

    Da-eun RyuHead of Application Security

Questions before you roll out

No. Privacy Mode is enforced across your organization by default. Octavo still keeps account, billing and usage data, and the Privacy Policy lists what it keeps.

Read the Privacy Policy

Teams includes SAML/OIDC SSO. Enterprise adds SCIM, so your directory controls who has a seat.

Connect your identity provider

Yes, on Enterprise. Admins allowlist the models and MCP servers members can use. On both plans, team rules give every agent the same instructions, and admins can add your organization’s own API keys for supported providers.

Compare models

Yes, on Enterprise. Self-hosted agents work like agents in Octavo Cloud and return the same branch and pull request.

How cloud agents work

Yes. Octavo builds a semantic index of the whole repository, monorepos included, so the agent and search find code by meaning. The index respects .gitignore and .octavoignore, so you decide which files it covers.

How context works

Your security team approves each build. Admins invite engineers by email, or SCIM adds them from your directory, and engineers install the approved build.

Invite your engineers

Both plans are bought through our sales team and invoiced under an order form. Enterprise adds pooled usage across the organization and dedicated support with an SLA.

Compare Teams and Enterprise

One agent for every engineer.