EnterpriseCompany workspaces

One AI control plane for the whole company.

Give every team one governed way to reach every model, with roles, spending limits, staged rollouts, and an audit trail your platform team controls.

Team and roles

The right hands on the right controls.

Invite your team into a company workspace and give each person one of three roles. Developers build; operators run routes and providers; admins own people, billing, and policy.

Can Developer Operator Admin
Read request logs and usageYesYesYes
Create, rotate, and delete credentialsYesYesYes
Publish, schedule, and roll back routesNoYesYes
Connect providers and switch keys or routes offNoYesYes
Use the Playground and add creditsNoYesYes
Invite members and change rolesNoNoYes
Set privacy mode, guardrails, branding, and domainNoNoYes
Export or erase workspace dataNoNoYes

Rollouts

Change routing like you ship code.

Schedule a route version for later, start it as a canary on part of the traffic, then promote or cancel. Every publish is a numbered version you can roll back.

  • Drafts stay drafts until someone publishes them.
  • Switch off a key or a whole route instantly if something goes wrong.
  • A note on each publish says why it changed.

Audit trail

A record of who changed what.

Route publishes and rollbacks, credential changes, provider key rotations, member changes, and domain events are recorded with the person and the before-and-after state.

  • Pull it from the API as JSON, or include it in a workspace export.
  • Switches are audited: turning a key or route off leaves a trace too.

Custom domain and branding

Your name on the dashboard.

Serve the LatentKit dashboard on your own hostname with a managed certificate, and show your logo, color, and company name to your team.

  • Point a CNAME at LatentKit; we verify and activate it with you.
  • Branded invites: new members land on your name, not ours.

Spend and security

Controls your security team will ask about.

Answers to the first questions in any review, already built in.

Spend you can predict

A monthly limit on every credential. Your own provider contracts with no markup. Prepaid credits for Platform Access. Usage by key, model, provider, and purpose.

Keys that can't leak back out

Provider keys sit in an encrypted vault and are write-only. LatentKit API keys are stored as hashes and shown once.

Data you decide to keep

PII scrubbing for stored logs, a zero-retention mode that keeps metadata only, prompt guardrails that block or redact, and self-serve export and erase.

Read the security posture

Company plan

Priced and sized with you.

Everything in Starter, plus:

  • Team members with Admin, Operator, and Developer roles
  • Limits set for your workloads, not a fixed tier
  • Scheduled publishing with canary rollouts
  • Dashboard on your own domain, with your branding
  • Audit trail and data export
  • Onboarding and support from our team
Can we keep our existing provider contracts?

Yes. Connect providers with your own API keys. That usage is billed by the provider directly, with no LatentKit markup.

Where are our provider keys stored?

In an encrypted vault. Keys are write-only: nobody can read them back in the dashboard, and they are never written to request logs.

Do you support single sign-on?

Not yet. Members sign in with email and password, Google, or GitHub. If SAML or SCIM is a requirement, tell us and we will share where it stands.

How does a company workspace get set up?

Talk to us. We set up the company workspace, its limits, and pricing with you. Your team then connects providers, publishes routes, and issues keys from the console.

Bring every team onto one route.

Tell us how your company uses AI today. We'll show you the workspace that fits.