> ## Documentation Index
> Fetch the complete documentation index at: https://mintlify.com/anomalyco/opencode/llms.txt
> Use this file to discover all available pages before exploring further.

# 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.
</Note>

## Getting Started

To get started with OpenCode Enterprise:

<Steps>
  <Step title="Run an Internal Trial">
    Do a trial internally with your team. OpenCode is open source and does not store any of your code or context data, so your developers can simply [get started](/introduction) and carry out a trial.
  </Step>

  <Step title="Contact Us">
    [Contact us](mailto:hello@opencode.ai) to discuss pricing and implementation options.
  </Step>
</Steps>

## Data Security

<CardGroup cols={2}>
  <Card title="No Data Storage" icon="shield-check">
    OpenCode does not store your code or context data. All processing happens locally or through direct API calls to your AI provider.
  </Card>

  <Card title="Code Ownership" icon="scale-balanced">
    You own all code produced by OpenCode. There are no licensing restrictions or ownership claims.
  </Card>
</CardGroup>

### Data Handling

**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.

### 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 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.

We recommend you disable this for your trial.

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

[Learn more about sharing](/share).

## 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](mailto:hello@opencode.ai).

## Deployment

Once you have completed your trial and you are ready to use OpenCode at your organization, you can [contact us](mailto:hello@opencode.ai) to discuss pricing and implementation options.

<CardGroup cols={2}>
  <Card title="Central Config" icon="gears">
    Set up OpenCode to use a single central config for your entire organization that integrates with your SSO provider.
  </Card>

  <Card title="SSO Integration" icon="fingerprint">
    Integrate with your organization's SSO provider for authentication to obtain credentials for your internal AI gateway.
  </Card>

  <Card title="Internal AI Gateway" icon="server">
    Configure OpenCode to use only your internal AI gateway and disable all other AI providers.
  </Card>

  <Card title="Self-hosting" icon="house">
    Self-host share pages on your infrastructure to ensure your data never leaves your organization.
  </Card>
</CardGroup>

### 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, [let us know](mailto:hello@opencode.ai).

## FAQ

<AccordionGroup>
  <Accordion title="What is OpenCode Enterprise?">
    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.
  </Accordion>

  <Accordion title="How do I get started with OpenCode Enterprise?">
    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 [contact us](mailto:hello@opencode.ai) to discuss pricing and implementation options.
  </Accordion>

  <Accordion title="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. For further details, [contact us](mailto:hello@opencode.ai) for a custom quote based on your organization's needs.
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="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, such as JFrog Artifactory, Nexus, or similar, ensure developers are authenticated before running OpenCode.

    To set up authentication with your private registry:

    ```bash theme={null}
    npm login --registry=https://your-company.jfrog.io/api/npm/npm-virtual/
    ```

    This creates `~/.npmrc` with authentication details. OpenCode will automatically pick this up.

    <Warning>
      You must be logged into the private registry before running OpenCode.
    </Warning>

    Alternatively, you can manually configure a `.npmrc` file:

    ```bash ~/.npmrc theme={null}
    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.
  </Accordion>
</AccordionGroup>