Skip to content

Roll out Octavo across your company.

Engineers get Octavo through their company: an admin invites them, and they install the build their security team approved. Most companies run a pilot with one team, then add the rest.

Start with one team. The team uses Octavo for its real work, so you decide on a rollout from what you see.

  • You choose the team, its repositories and what a good result looks like.
  • We set up your organization with single sign-on and Privacy Mode enforced.
  • We agree the length of the pilot with you before it starts.
  • At the end, we review usage analytics with you: agent runs, cloud agents and merged pull requests.

Your security team signs off. The review can run before the pilot or alongside it.

  • We answer your security questionnaire and send our security documentation.
  • We explain how Privacy Mode and zero data retention work, and which model providers process requests.
  • We sign a data processing agreement that covers the code your engineers send to Octavo.
  • On Enterprise, your security team decides which models and MCP servers are allowed, where your data stays and where cloud agents run.

Your security team can write to ours at security@octavo.me.

Connect your identity provider. Engineers sign in with SAML or OIDC, and on Enterprise your directory decides who has a seat.

  • Single sign-on works on Teams and Enterprise, with any identity provider that supports SAML 2.0 or OIDC, such as Okta, Microsoft Entra ID or Google Workspace.
  • Verify your email domains, so only your organization’s accounts can join.
  • On Enterprise, SCIM adds and removes members as your directory changes, so access ends when someone leaves.

Set policies once, for everyone. Every member and every agent run follows them from the first sign-in.

  • Privacy Mode is on by default and shown as enforced in the admin dashboard.
  • Team rules sync to every agent run.
  • Octavo Review can be a required check on the repositories you choose.
  • On Enterprise, admins also set model and MCP allowlists, spend limits, admin roles and data residency, and audit logs record every change.

Your security team approves each build. Engineers get a new version only after it is approved, so everyone runs a build you reviewed.

  • Each release reaches your admins with its release notes, signed installers and SHA‑256 checksums.
  • Installers are notarized on macOS, Authenticode-signed on Windows and signed with the Octavo release key on Linux.
  • Deploy the approved build with your device management tools, or engineers install it from their Octavo account.
  • Install the same approved build of the Octavo CLI on build servers, in container images and on CI runners.

Invite your engineers. Add teams one at a time, starting with the pilot team.

  • Admins invite engineers by email, or SCIM adds them from your directory on Enterprise.
  • Each engineer signs in with their work account and installs the approved build. Their seat and policies are already set.
  • Engineers import their VS Code extensions, themes and keybindings in one click.
  • The admin dashboard shows seats in use and usage analytics as teams join.

Platforms and system requirements. Octavo runs on macOS, Windows and Linux, in the terminal and in the cloud.

Current version: 1.6, released Sep 24, 2026.

Release notes
macOS
macOS 12 Monterey or later, on Apple Silicon or Intel. DMG installers for Apple Silicon, Intel or both.
Windows
Windows 10 version 1809 or later, or Windows 11, on x64 or ARM64. System-wide and per-user installers.
Linux
A distribution with glibc 2.28 or later, on x64 or ARM64. .deb, .rpm and AppImage packages.
Octavo CLI
The same platforms as the editor. Runs in any shell, over SSH, in containers and headless in CI.
Cloud agents
Each task runs in its own VM in Octavo Cloud, or in your own VPC on Enterprise.
Octavo Review
Pull requests on GitHub and GitLab.

Questions about rollout

No. Octavo has no public download. If your company uses Octavo, ask an admin to invite you. If it does not, ask your engineering lead to request a demo.

Request a demo

Yes. The macOS DMG, the Windows system installer and the Linux packages install without user interaction, so tools such as Jamf or Intune can deploy the approved build.

A new version reaches engineers only after your security team approves it. Until then, engineers keep the build they have.

Yes. Install the approved CLI build on your runners or in your CI image, and give each job an API key an admin creates for CI.

How the CLI works

On Enterprise, SCIM ends their access when your directory removes them. On Teams, an admin removes them in the admin dashboard, and the seat can go to someone else.

Plan your pilot with us.