enterprise

The same agent, with the controls an organisation needs.

Single sign-on, audit logs, roles, a private deployment — and a policy that refuses by default on every engineer's machine, set in one place.

teams running rovecode

Placeholder names, until the first customers agree to be listed.

identity and control

Who may run what, and a record of what ran.

The four policy layers already stand in front of every tool call. Enterprise adds the layer above them: your directory, your roles, your logs.

01
Single sign-on
SAML and OIDC against your identity provider — Okta, Entra ID, Google Workspace. Social logins switch off the day SSO switches on.
02
SCIM provisioning
Accounts appear when people join and vanish when they leave, from your directory, without a ticket.
03
Audit log export
Every session, tool call and approval with who, when and from where — as JSONL with a hash chain, or streamed to your SIEM.
04
IP allow-lists
Restrict the web app and the API to the networks you name; everything else is refused before it authenticates.
05
Custom roles
Members, admins and the roles in between: who may change policy, who may see credits, who may only read.
06
Policy for the whole organisation
The deny-default rules on every engineer's machine come from one place, and no one can loosen them locally.

deployment

The agent runs on the engineer's machine on every plan. What moves is the service around it.

01
Self-hosted
The agent already runs from source on your machines. Put the hosted service on your own servers and nothing about it changes.
$ git clone https://github.com/9Code-Labs/rovecode && cd rovecode && bun install && bun link
02
Private cloud
A single-tenant deployment in your cloud account and region, with your keys, reachable only from your network.
03
Hosted by us
The plans on the pricing page, with the enterprise controls switched on and a contract around them.

support

01
A named contact
One engineer who knows your setup, on email and a shared channel — not a queue.
02
A response-time commitment
Hours, not days, for anything that stops work — written into the contract, measured, reported.
03
Onboarding and training
Policy design for your repositories, a session with each team, and a playbook that stays yours.

in their words

Review moved into the terminal and the approval card became the conversation. We ship the same amount with a third of the back-and-forth.
Aylin Demirci
Head of Platform · Northwind Robotics
The deny-default policy is the reason security signed off. Every tool call is a line in a log we already read.
Marcus Oyelaran
Staff Engineer · Harbourline Payments
Twelve people, local models, no vendor in the loop. It runs where our clients' code is allowed to run.
Inés Ferrer
Founder · Meridian Studio

Illustrative quotes from fictional teams, written for the page — real ones replace them before launch.

talk to us