Skip to main content
Choose the right configuration approach for your organization. Most teams start with SaaS for quick deployment, while enterprises with complex requirements opt for self-hosted infrastructure.

Configuration Paths

SaaS Provider Configuration

Quick Setup via Web Console

✅ No infrastructure required
✅ 5-10 minute configuration
✅ Web-based admin console
✅ Automatic updates
✅ Simplified credential management
Best for:
  • Small to medium teams (5-50 developers)
  • Quick deployment needs
  • Limited DevOps resources
  • Standard security requirements
  • Single region deployments

Self-Hosted Configuration

Full Infrastructure Control

✅ Your own AWS/GCP/K8s
✅ VPC endpoints & private connectivity
✅ Multi-account setups
✅ Advanced compliance & audit
✅ GitOps workflows
Best for:
  • Large enterprises (50+ developers)
  • Complex security requirements
  • Existing cloud infrastructure
  • Multi-region deployments
  • Custom compliance needs

Detailed Comparison

Feature Comparison

FeatureSaaSSelf-Hosted
ConfigurationWeb UIYAML + Helm/Kubernetes
InfrastructureNone requiredFull AWS/GCP/K8s
VPC EndpointsBasicFull private connectivity
Multi-Account
IAMStandard RBAC rolesStandard RBAC roles
ComplianceStandardCustom frameworks
GitOps
MaintenanceManaged by ClineSelf-managed
UpdatesAutomatic (extension)Automatic (extension) + Infrastructure control

Security & Compliance

CapabilitySaaSSelf-Hosted
Network EncryptionHTTPS/TLSHTTPS/TLS
NetworkPublic internetPrivate VPC endpoints
Access ControlStandard RBACStandard RBAC
Audit LogsOpenTelemetry tracesOpenTelemetry traces + Infrastructure logs
Data ResidencyCline-managed deploymentCustomer-controlled deployment

Cost Structure

Cost CategorySaaSSelf-Hosted
Cline SubscriptionFixed enterprise feeFixed enterprise fee
Inference Provider CostsUsage-basedUsage-based
Infrastructure✅ None requiredKubernetes, networking, storage
Personnel✅ None requiredDevOps team needed
Total Cost ProfilePredictable and simpleVariable based on scale

Migration Path

Most organizations start with SaaS configuration for quick deployment, then migrate to self-hosted later as requirements grow. This minimizes risk and ensures your infrastructure meets actual usage patterns.

Getting Started

Need Help Deciding?