Adopt agents with enterprise controls

SSO provider configuration for enterprise identity.

Trusted by developers at

The security posture has to be part of the product.

Enterprise controls make boundaries around code, credentials, prompts, telemetry, repositories, and internal tools explicit.

  • SSO, OIDC, SCIM, and organization membership.
  • Deployment boundaries for self-hosted and controlled cloud operation.
Environment starting in Ona.

Enterprise controls.

The operating layer around company-wide adoption.

Questions & answers

Is Enterprise a separate product?

It is the set of controls and deployment options needed for company-wide use.

Can we connect our identity provider?

Yes. The docs cover SSO, OIDC providers, SCIM, and identity setup.

Can we run without sending code to a public SaaS?

The self-hostable path is designed for teams that need controlled infrastructure boundaries.

Can security teams review policy?

Yes. Policies, guardrails, and deployment posture are explicit product surfaces.

Other platform pieces

The rest of the agent infrastructure layer.

BYO Agents & Inference

Any agent on your inference stack.

Integrations

Connect approved tools to agent runs.

Workflows

Schedule, trigger, and review agent runs.

Environments

Isolated workspaces with repo context.

Self-host Proliferate

Run Proliferate entirely in your VPC

Runtime Security

Control what agents can access and execute.

Governance & budgets

Policies, approvals, usage, and spend.

API, MCP, CLI

Coming soon

Programmatic access to agent workflows.

Run agents on infrastructure you control.

Start with one team, then standardize agent workflows without giving up control of code, credentials, or inference.