docs: enterprise

This commit is contained in:
Jay V
2025-10-29 19:07:41 -04:00
parent 950b608c4d
commit e6132fc6a4
3 changed files with 189 additions and 153 deletions

View File

@@ -1,15 +1,18 @@
---
title: Enterprise
description: Using OpenCode in your organization.
description: Using OpenCode securely in your organization.
---
import config from "../../../config.mjs"
export const email = `mailto:${config.email}`
OpenCode does not store any of your code or context data. This makes it easy for
you to use OpenCode at 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.
To get started, we recommend:
:::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. **<a href={email}>Contact us</a>** to discuss pricing and implementation options.
@@ -18,13 +21,16 @@ To get started, we recommend:
## Trial
Since OpenCode is open source and does not store any of your code or context data, your developers can simply [get started](/docs/) and carry out a trial.
OpenCode is open source and does not store any of your code or context data, so your developers can simply [get started](/docs/) 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.
**OpenCode does not store your code or context data.** All processing happens locally or through direct API calls to your AI provider.
This means that as long as you are using a provider you trust, or an internal
AI gateway, you can use OpenCode securely.
The only caveat here is the optional `/share` feature.
@@ -32,7 +38,7 @@ The only caveat here is the optional `/share` feature.
#### Sharing conversations
If a user enables the `/share` feature, the conversation and the data associated with it are sent to the service we use to host these shares pages at opencode.ai.
If a user enables the `/share` feature, the conversation and the data associated with it are sent to the service we use to host these share pages at opencode.ai.
The data is currently served through our CDN's edge network, and is cached on the edge near your users.
@@ -51,7 +57,54 @@ We recommend you disable this for your trial.
### Code ownership
**You own all code produced by opencode.** There are no licensing restrictions or ownership claims.
**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, **<a href={email}>contact us</a>**.
---
## Deployment
Once you have completed your trial and you are ready to use OpenCode at
your organization, you can **<a href={email}>contact us</a>** 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 and ensures all users access only your internal AI gateway.
---
### SSO integration
Through the central config, OpenCode can integrate with your organization's SSO provider for authentication.
This allows OpenCode to obtain credentials for your internal AI gateway through your existing identity management system.
---
### Internal AI gateway
With the central config, OpenCode can also be configured to use only your internal AI gateway.
You can also disable all other AI providers, ensuring all requests go through your organization's approved infrastructure.
---
### 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. If you're interested, **<a href={email}>let us know</a>**.
---
@@ -60,59 +113,37 @@ We recommend you disable this for your trial.
<details>
<summary>What is OpenCode Enterprise?</summary>
OpenCode Enterprise provides self-hosted deployment options with enhanced security, SSO integration, and dedicated support for organizations that need to maintain full control over their development environment.
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.
</details>
<details>
<summary>How do I get started with OpenCode Enterprise?</summary>
Simply start with an internal trial with your team. OpenCode by default does not store your code or context data, making it easy to get started.
Then **<a href={email}>contact us</a>** to discuss pricing and implementation options.
</details>
<details>
<summary>How does enterprise pricing work?</summary>
Enterprise pricing is based on team size and deployment requirements. Contact us at <a href={email}>{config.email}</a> for a custom quote based on your organization's needs.
We offer per-seat enterprise pricing. If you have your own LLM gateway, we do not charge for tokens used. For further details, **<a href={email}>contact us</a>** for a custom quote based on your organization's needs.
</details>
<details>
<summary>What deployment options are available?</summary>
<summary>Is my data secure with OpenCode Enterprise?</summary>
We offer cloud-hosted, on-premises, and air-gapped deployment options. Each includes SSO integration, private package registry support, and customizable security configurations.
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.
</details>
<details>
<summary>Is my data secure with enterprise?</summary>
<summary>Can we use our own private NPM registry?</summary>
Yes. OpenCode does not store your code or context data. All processing happens locally or through direct API calls to your AI provider. Enterprise deployments add SSO protection and can be fully air-gapped for maximum security.
</details>
<details>
<summary>Can we integrate with existing tools?</summary>
Yes. OpenCode supports private npm registries, custom authentication providers, and can be integrated into your existing CI/CD pipelines and development workflows.
</details>
---
## Deployment
Once you have completed your trial and you are ready to self-host opencode at
your organization, you can **<a href={email}>contact us</a>** to discuss
pricing and implementation options.
---
### SSO
SSO integration can be implemented for enterprise deployments after your trial.
This will allow your team's session data and shared conversations to be protected
by your enterprise's authentication system.
---
### Private NPM
opencode supports private npm registries through Bun's native `.npmrc` file support. If your organization uses a private registry, such as JFrog Artifactory, Nexus, or similar, ensure developers are authenticated before running opencode.
OpenCode supports private npm registries through Bun's native `.npmrc` file support. If your organization uses a private registry, such as JFrog Artifactory, Nexus, or similar, ensure developers are authenticated before running OpenCode.
To set up authentication with your private registry:
@@ -120,11 +151,11 @@ To set up authentication with your private registry:
npm login --registry=https://your-company.jfrog.io/api/npm/npm-virtual/
```
This creates `~/.npmrc` with authentication details. opencode will automatically
This creates `~/.npmrc` with authentication details. OpenCode will automatically
pick this up.
:::caution
You must be logged into the private registry before running opencode.
You must be logged into the private registry before running OpenCode.
:::
Alternatively, you can manually configure a `.npmrc` file:
@@ -134,11 +165,6 @@ registry=https://your-company.jfrog.io/api/npm/npm-virtual/
//your-company.jfrog.io/api/npm/npm-virtual/:_authToken=${NPM_AUTH_TOKEN}
```
Developers must be logged into the private registry before running opencode to ensure packages can be installed from your enterprise registry.
Developers must be logged into the private registry before running OpenCode to ensure packages can be installed from your enterprise registry.
---
### Self-hosting
The share feature can be self-hosted and the share pages can be made accessible
only after the user has been authenticated.
</details>