mirror of
https://github.com/cline/cline.git
synced 2026-09-24 23:20:16 +08:00
1be314dfed
* enterprise docs * tested for accuracy * Reorganize Enterprise docs structure - Consolidate member management under team-management/ - Unify all configuration under configuration/ with two clear paths: - remote-configuration/ for simple cloud-based setup - infrastructure-configuration/ for advanced enterprise features - Create comprehensive overview pages explaining the differences - Update all internal links to reflect new paths - Preserve all existing content while eliminating redundancy - Maintain clear separation between admin and member documentation * removed trailing backslash * fix docs.json * enterprise docs reformat * monday update * tidied up managing members section * fixed deployment guide * simplify rules * workflow cleanup * rules tweak * Update docs/enterprise-solutions/configuration/overview.mdx Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com> * fix other features * fixed provider docs * fixed monitoring * fix providers * updated cta and rbac * fix enterprise overview * enterprise-docs * hid self-hosted section for now * addressed format fixed * docs: restructure monitoring navigation and move telemetry - Remove unnecessary OpenTelemetry dropdown wrapper in Enterprise navigation - Move Cline Telemetry from control-other-cline-features to monitoring section - Update all internal documentation links to new telemetry path - Simplify Control Other Cline Features section to focus on Yolo Mode only - Group related monitoring features (overview, telemetry, opentelemetry) together This creates a more cohesive navigation structure where telemetry-related features are adjacent and eliminates unnecessary nested dropdowns. * docs: rename Basic Telemetry to Cline Telemetry and add link - Rename all instances of 'Basic Telemetry' to 'Cline Telemetry' for consistency - Add href link to Cline Telemetry card in Monitoring Options section - Update section headings and subheadings to use 'Cline Telemetry' - Ensures consistent naming across monitoring documentation * docs: restructure Enterprise YOLO Mode to focus on administrator controls - Change title from 'Yolo Mode' to 'YOLO Mode' for consistency - Add reference link to /features/yolo-mode for general documentation - Remove duplicate content about basic YOLO Mode functionality - Focus exclusively on Enterprise administrator configuration and controls - Add comprehensive policy recommendations by organization size - Include security implications, monitoring requirements, and compliance considerations - Provide detailed technical implementation guidance - Update overview.mdx card description to reflect enterprise focus * docs: hide self-hosted/infrastructure configuration references - Remove choosing-your-deployment from Enterprise navigation - Remove self-hosted references from enterprise-solutions/overview.mdx - Remove self-hosted comparison and warning from remote-configuration/overview.mdx - Remove Info boxes linking to infrastructure config from provider pages (AWS, Google, LiteLLM) - Remove Self-Hosted OpenTelemetry Collector section from opentelemetry.mdx - Remove self-hosted deployment section from control-other-cline-features/overview.mdx All self-hosted/infrastructure configuration documentation remains intact but is no longer navigable or linked from SaaS provider configuration pages. This allows easy restoration when features become available. * clarified domain and seat info * fixed getOpenTabs function * Update getOpenTabs.ts * Update package.json * Revert package-lock files to main --------- Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com> Co-authored-by: Juan Pablo Flores <juan@cline.bot>
96 lines
4.3 KiB
Plaintext
96 lines
4.3 KiB
Plaintext
---
|
|
title: "Cline Enterprise"
|
|
sidebarTitle: "Overview"
|
|
description: "Enterprise security, governance, and observability for the coding agent millions of developers trust"
|
|
---
|
|
|
|
Cline Enterprise brings centralized governance to the same open-source architecture that millions of developers already use. Your code stays in your environment, you use your own inference at your negotiated rates, and you get the security and observability capabilities that platform teams need for org-wide deployment.
|
|
|
|
<Card title="Learn More About Enterprise" icon="building" href="https://cline.bot/enterprise">
|
|
Visit our website for detailed information about enterprise features, pricing, and deployment options.
|
|
</Card>
|
|
|
|
## What You Get
|
|
|
|
It delivers five core capabilities that platform teams need for production deployment. Each addresses a specific requirement for scaling AI coding across your organization.
|
|
|
|
### Security by Design
|
|
|
|
Your code never leaves your environment. Cline processes everything locally - no uploads, no indexing, no training on your data.
|
|
|
|
<CardGroup cols={2}>
|
|
<Card title="Client-side execution" icon="computer">
|
|
All processing happens within your environment
|
|
</Card>
|
|
|
|
<Card title="No data exfiltration" icon="shield-check">
|
|
Code and context never transmitted externally
|
|
</Card>
|
|
|
|
<Card title="No codebase indexing" icon="database">
|
|
Repositories are never indexed or cached
|
|
</Card>
|
|
|
|
<Card title="No model training" icon="ban">
|
|
Your code and prompts aren't used for training
|
|
</Card>
|
|
</CardGroup>
|
|
|
|
### Bring Your Own Inference
|
|
|
|
Use your existing cloud contracts and negotiated rates. Most AI tools force you to buy inference through them with markup. Cline connects directly to your providers.
|
|
|
|
Connect to any inference provider:
|
|
- AWS Bedrock
|
|
- Google Vertex AI
|
|
- Azure OpenAI
|
|
- Anthropic direct
|
|
- OpenAI direct
|
|
- Cerebras
|
|
- Any OpenAI-compatible endpoint
|
|
|
|
Switch models instantly as new ones release. Use Claude Sonnet 4.5 as your daily driver, GPT-5 for complex refactoring, open-source models for simple tasks. Your existing cloud credits and startup program contracts now cover AI coding. We handle the agent loop. You handle the inference. No markup, no vendor lock-in.
|
|
|
|
### Governance at Scale
|
|
|
|
Platform teams need central control when thousands of developers use AI. Individual API keys scattered across laptops create security risks and cost overruns.
|
|
|
|
Enterprise governance provides:
|
|
- **SSO authentication**: Corporate credentials instead of personal API keys
|
|
- **Role-based access control**: Three-tier hierarchy (Member/Admin/Owner) with organization-scoped permissions
|
|
- **Model and tool controls**: Govern which models and tools each team accesses
|
|
- **Remote configuration**: Manage settings for all developers from one dashboard
|
|
- **Usage tracking and observability**: OpenTelemetry integration for monitoring usage, costs, and performance with selective audit logging for administrative operations
|
|
|
|
Configure once, deploy everywhere. Developers work how they prefer while you maintain control.
|
|
|
|
### Complete Observability
|
|
|
|
Export logs to your existing observability stack. Track usage, costs, and performance across all teams.
|
|
|
|
- **OpenTelemetry export**: Direct integration with Datadog, Grafana, Splunk
|
|
- **Real-time analytics**: Track adoption, performance, and patterns
|
|
- **Cost breakdown**: See exactly what each team spends on which models
|
|
- **JSON output**: Build custom dashboards in your existing tools
|
|
|
|
The same observability standards you require for production systems.
|
|
|
|
## Deployment
|
|
|
|
Cline Enterprise connects securely to your infrastructure. Deploy in cloud environments. Configure to work with your existing security policies and compliance requirements.
|
|
|
|
Rolling out to your organization:
|
|
1. Configure Cline Core to connect to your infrastructure
|
|
2. Set SSO, RBAC, and governance policies
|
|
3. Deploy to developers via your existing software distribution
|
|
4. Monitor usage through your observability tools
|
|
|
|
## Next Steps
|
|
|
|
- Review security architecture
|
|
- Configure [cloud provider setup](/provider-config/aws-bedrock/api-key) (AWS Bedrock, Vertex AI, Azure)
|
|
- Set up [MCP servers](/mcp/mcp-overview) for custom tooling
|
|
- Add [custom instructions](/features/cline-rules) for your codebase
|
|
|
|
Schedule a walkthrough to see how Cline Enterprise fits your infrastructure. We'll work with your security and compliance requirements to deploy in your environment.
|