Skip to main content
SaaS Provider Configuration allows administrators to centrally configure inference providers for their entire organization through the Cline hosted admin console. This approach ensures consistent provider access, security policies, and cost management across all team members without requiring individual developer setup or infrastructure deployment.

How Remote Configuration Works

Remote configuration operates through Cline’s hosted service at app.cline.bot, where administrators can:

Centralized Setup

Configure providers once for the entire organization through the web-based admin console.

Automatic Enforcement

Team members automatically receive the configured provider settings when signed into their organization.

Simplified Onboarding

New team members get instant access to inference providers without complex individual configuration.

Consistent Experience

Ensure all team members use the same models, regions, and settings organization-wide.

Supported Providers

Cline supports remote configuration for the following inference providers:
ProviderUse CaseConfigurationMember Setup
ClineOrganizations using Cline’s native provider with centralized API key managementAPI provider selection, model accessNo individual API keys needed - fully managed by organization
Amazon BedrockOrganizations using AWS infrastructureRegion selection, VPC endpoints, cross-region inference, prompt cachingAWS credential configuration in VS Code
LiteLLMOrganizations requiring multi-model access through a unified proxyProxy endpoint, authentication, model routingAPI key or endpoint configuration in VS Code (or centralized with Master Key)
Google Vertex AIOrganizations using Google Cloud PlatformProject ID, region selection, model accessService account or credential configuration in VS Code

Configuration Process

The typical remote configuration process follows these steps:
1

Administrator Setup

Access the Cline admin console and configure the desired inference provider with organization-wide settings.
2

Automatic Distribution

Provider configuration is automatically distributed to all organization members signed into Cline.
3

Member Credential Setup

Team members add their individual credentials (API keys, AWS profiles, etc.) to connect to the configured provider.
4

Immediate Access

Once credentials are configured, members can immediately start using the inference provider through Cline.

Benefits of Remote Configuration

For Administrators

  • Centralized Control: Manage all provider settings from one location
  • Security Compliance: Ensure consistent security policies across the organization
  • Easy Updates: Change provider settings organization-wide instantly

For Team Members

  • Simplified Setup: No need to research provider configuration options
  • Consistent Experience: Same models and features available to everyone
  • Quick Onboarding: Get started immediately with pre-configured providers
  • Focus on Development: Spend time coding instead of configuring inference providers

Getting Started

To get started with provider remote configuration:
  1. Choose Your Provider: Select the inference provider that best fits your organization’s needs and existing infrastructure
  2. Admin Configuration: Follow the provider-specific admin configuration guide
  3. Member Onboarding: Have team members complete the provider-specific member configuration
  4. Start Developing: Begin using Cline with centrally managed inference provider access
Select your provider below to begin the configuration process: