Skip to content
Showcase Ecosystem Source Code Docs

Enterprise

Enterprise

Using OpenCode securely in your organization.

OpenCode Enterprise is for organizations that want to ensure that their code and data never leaves their infrastructure. It can do this by using a centralized config that integrates with your SSO and internal AI gateway.

[!NOTE] OpenCode does not store any of your code or context data.

To get started with OpenCode Enterprise:

  1. Do a trial internally with your team.
  2. Contact us to discuss pricing and implementation options.

Trial

OpenCode is open source and does not store any of your code or context data, so your developers can simply get started and carry out a trial.

Data handling

OpenCode does not store your code or context data. All processing happens locally or through direct API calls to your AI provider.

The only caveat here is the optional /share feature.

Sharing conversations

如果用户启用了 /share 功能，对话及相关数据会被发送到 opencode.ai 的分享页面服务。

// 禁用分享功能（推荐用于企业试用） opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "share": "disabled"
}

Code ownership

You own all code produced by OpenCode. There are no licensing restrictions or ownership claims.

Pricing

We use a per-seat model for OpenCode Enterprise. If you have your own LLM gateway, we do not charge for tokens used.

For further details about pricing and implementation options, contact us.

Deployment

Once you have completed your trial and you are ready to use OpenCode at your organization:

Contact us to discuss pricing and implementation options.

Central Config

// 中心化配置概述 We can set up OpenCode to use a single central config for your entire organization.

This centralized config can:

  • Integrate with your SSO provider for authentication
  • Ensure all users access only your internal AI gateway
  • Enforce organizational policies across all users
  • Simplify onboarding for new developers

SSO integration

Through the central config, OpenCode can integrate with your organization’s SSO provider for authentication.

Benefits:

  • Users authenticate with existing corporate credentials
  • OpenCode obtains credentials for your internal AI gateway through SSO
  • No separate credentials to manage
  • Centralized access control

Internal AI gateway

With the central config, OpenCode can also be configured to use only your internal AI gateway.

// 限制只使用内部 AI 网关的配置示例 opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "provider": {
    // 只允许内部网关 provider
  },
  "disabled_providers": ["anthropic", "openai", "openrouter"],
  "enabled_providers": ["your-internal-gateway"]
}

Benefits:

  • All AI requests go through your organization’s approved infrastructure
  • Full control over data retention and logging
  • Compliance with organizational security policies
  • Cost management through internal billing

Self-hosting

While we recommend disabling the share pages to ensure your data never leaves your organization, we can also help you self-host them on your infrastructure.

This is currently on our roadmap. Let us know if you’re interested.

FAQ

What is OpenCode Enterprise?

OpenCode Enterprise is for organizations that want to ensure that their code and data never leaves their infrastructure. It uses a centralized config that integrates with your SSO and internal AI gateway.

How do I get started with OpenCode Enterprise?

  1. Simply start with an internal trial with your team - OpenCode by default does not store your code or context data.
  2. Contact us to discuss pricing and implementation options.

How does enterprise pricing work?

We offer per-seat enterprise pricing. If you have your own LLM gateway, we do not charge for tokens used.

Contact us for a custom quote based on your organization’s needs.

Is my data secure with OpenCode Enterprise?

Yes. OpenCode does not store your code or context data. All processing happens locally or through direct API calls to your AI provider. With central config and SSO integration, your data remains secure within your organization’s infrastructure.

Can we use our own private NPM registry?

OpenCode supports private npm registries through Bun’s native .npmrc file support. If your organization uses a private registry (JFrog Artifactory, Nexus, or similar), ensure developers are authenticated before running OpenCode.

# 登录到私有 registry
npm login --registry=https://your-company.jfrog.io/api/npm/npm-virtual/

Alternatively, manually configure .npmrc:

~/.npmrc

registry=https://your-company.jfrog.io/api/npm/npm-virtual/
//your-company.jfrog.io/api/npm/npm-virtual/:_authToken=${NPM_AUTH_TOKEN}

[!CAUTION] Developers must be logged into the private registry before running OpenCode to ensure packages can be installed.

What SSO providers are supported?

OpenCode Enterprise can integrate with major SSO providers including:

  • Okta
  • Azure AD
  • Google Workspace
  • Ping Identity
  • Custom SAML/OIDC providers

Can we audit AI requests?

With an internal AI gateway, you can:

  • Log all AI requests
  • Monitor usage patterns
  • Set rate limits per user or team
  • Generate compliance reports

What about offline/air-gapped environments?

OpenCode can be configured for offline environments:

  1. Install from local packages
  2. Configure internal mirrors for updates
  3. Use internal AI gateway for all model access
  4. Self-host share functionality (roadmap)

Security best practices

  1. Disable sharing - Prevent data from leaving your infrastructure
  2. Use internal gateway - Route all AI requests through your approved infrastructure
  3. Enable SSO - Centralized authentication and access control
  4. Configure policies - Set organizational policies through central config
  5. Regular audits - Monitor usage through your internal AI gateway logs