Team deployment

OpenCtrlC is an open-source client that runs on a developer’s machine. It is not a hosted enterprise control plane, managed model gateway, or per-seat service.

Start with a small evaluation

For a team trial:

1. Review the repository license and security requirements.
2. Choose the model providers or local models approved by your organization.
3. Configure the same provider guidance and project rules for the team.
4. Disable optional sharing unless your organization has reviewed its destination.

All source code, session history, and provider configuration remain subject to the local filesystem and the services selected by each user. OpenCtrlC does not automatically upload project code to an OpenCtrlC backend.

Provider and data boundaries

OpenCtrlC sends model requests through the provider configuration that you choose. Each provider may have different retention, training, residency, and security policies. Teams should review those policies and use an internal gateway or local model when required.

The optional share feature sends an explicitly selected conversation to the share service configured for the deployment. Set it to disabled when sharing is not approved:

openctrlc.json

{
  "$schema": "https://openctrlc.pages.dev/config.json",
  "share": "disabled"
}

Read more about sharing.

Self-managed conventions

OpenCtrlC does not currently provide an enterprise pricing plan, hosted SSO, central policy service, or a guaranteed internal deployment package. Teams can still manage the open-source client with their existing device management, secret management, network controls, and internal documentation.

For implementation questions or to discuss a contribution, use GitHub Discussions.