# Enterprise

The same platform your engineers already want, with the deployment model, compliance posture, and controls your security team signs off on.

## Scale

- **~50%** of pull requests produced by Replicas
- **3M+** minutes running coding agents
- **50k+** coding agents ran

## Platform

- **Isolated compute per task:** Every task boots its own Linux VM. Agents share nothing with the run beside them, and the machine is destroyed when the work is done.
- **Environments admins control:** Warm hooks, credentials, MCP servers, and skills are configured once at the organization level, then inherited by every agent your team starts.

## Security and deployment

### Cloud, dedicated, or self-hosted
Start on Replicas cloud, move to a dedicated single-tenant deployment, or run the platform inside your own infrastructure.

- Replicas cloud
- Dedicated single-tenant
- Self-hosted in your infrastructure

### Control where your code lives
Decide what is kept after a workspace sleeps, which agents and models are allowed, and where inference is billed.

- Turn workspace history retention off
- Bring your own Bedrock, Foundry, or provider keys
- Sync secrets from Doppler or Infisical

### Governance built in
The controls a security review asks for are part of the product, not a services engagement.

- SCIM user provisioning
- Audit log of every config change
- Data Processing Agreement

## FAQ

### Can we self-host Replicas?
Yes. Enterprise customers run Replicas in our cloud, in a dedicated single-tenant deployment, or self-hosted inside their own infrastructure. Contact sales and we will scope the model that fits your review.

### Are you SOC 2 compliant?
Replicas is SOC 2 Type I, with Type II in progress. Our Trust Center publishes the current report, monitored controls, and subprocessors.

### Where does our source code run?
Inside a per-task Linux VM that is isolated from every other workspace and torn down after the run. Admins can turn workspace history retention off so chat, Canvas files, and repository changes are not persisted after a workspace sleeps.

### Can we use our own model credentials?
Yes. Claude Code runs on Claude OAuth, an Anthropic API key, AWS Bedrock, or Microsoft Foundry. Codex runs on OpenAI or Foundry, and Opencode, Pi, and Cursor accept your own keys — so inference stays on contracts you already hold.

### How do we manage access and prove what changed?
SCIM provisioning keeps membership in sync with your IdP, roles limit who can change organization settings, and the audit log records every configuration change across your organization — which resource changed, what action was taken, who took it, and when.

### How does enterprise pricing work?
Unlimited manual and automated workspace minutes, unlimited automations, custom API and rate limits, and a shared Slack channel, priced per contract. Contact sales for a quote.

## Links

- Contact sales: https://tryreplicas.com/contact-sales
- Book a demo: https://cal.com/connor-replicas/30min
- Trust Center: https://app.vanta.com/replicas.dev/trust/t8qlw1u4i067lqg7b4lh6q
- Pricing: https://tryreplicas.com/pricing