Skip to main content
Managed services let your organization bring its own LLM provider API keys (BYOK). When a key is connected for a provider, every agent and workflow model call to that provider — across all projects in the organization — routes through your key instead of Luno OS’s platform credentials. Use Governance → Managed services (/settings/managed-services) in the web app to connect, rotate, and disconnect provider keys for the active organization.
Managed services are not app credentials. The credentials system (luno connect, luno credentials create) stores keys for integrations your automations call as tools — Slack, GitHub, Exa, and the rest of the apps catalog. LLM provider keys for model inference are connected here instead.

​
Supported providers

One key per provider per organization. Keys are encrypted at rest; after connecting, Luno OS only shows a non-secret key preview.

​
How routing works

Model ids carry a vendor prefix (for example openai/gpt-5.6-sol or anthropic/claude-sonnet-5.5). When a model call reaches the platform:
  1. The vendor prefix is matched against your connected providers.
  2. If a key is connected for that vendor, the request runs on your key.
  3. Otherwise the request runs on Luno OS platform credentials at the platform rate.
No code changes are needed — agents and workflows keep referencing models the same way.

​
Billing

Model usage on your own keys is not billed by Luno OS — your provider bills you directly under your own agreement. Run history still records the provider cost for reference, labeled Your API key, and the run’s Total billed only includes what Luno OS charged (run fees, sandbox time, and any usage on platform keys). Requests on platform credentials are billed at provider cost with the platform markup, and run with ZDR-only (zero data retention) routing. BYOK requests run under your provider agreement, so ZDR routing is not forced.

​
Connect a provider

Connect from the web app (Governance → Managed services) or the CLI:
Rotate or disconnect at any time:

​
Permissions

​
Next steps

Billing

Review usage and billing for the organization.

Run history

See per-run usage, including which key source served each model call.

Credentials

Store integration credentials for the tools your automations call.

Build agents

Configure models on your agents.