Cercano is the interface · Cercloud is the control plane
One neutral policy, identity, routing, and audit layer across local runtimes, partner backends, and frontier APIs.
The problem
Most teams rebuild the same layer from gateway glue, environment variables, request logs, and spreadsheets. Cercloud turns that accidental infrastructure into one deliberate control plane.
Product / Enterprise
Developers keep the tools and models that make them effective. The organization gets a legible, enforceable system around them.
Approved connections, per-task routes, and shared skills become signed policy, not tribal knowledge.
Admins publish immutable revisions. Each enrolled Cercano host fetches a short-lived signed bundle and evaluates it before inference, failing closed when the lease expires.
Keep frontier models for the work that needs them. Move routine and sensitive tasks to cheaper or local destinations.
Cercloud governs a mixed estate instead of forcing it into one vendor. Cercano optimizes at the source; the control plane applies policy across the fleet.
Drive spend down through better decisions, not a race to mark tokens up less.
Route routine work to efficient models and providers, reserve frontier models for the tasks that need them, and reduce the context each request carries through compaction and caching. Then put budgets, quotas, showback, and chargeback around the whole fleet.
Identity turns policy into permission, usage into attribution, and an audit event into an accountable action.
Connect Google Workspace over OIDC or integrate through SAML 2.0, SCIM 2.0, and LDAP. Cercloud binds organization membership, directory groups, roles, and enrolled hosts to permissions—then attributes every governed action to the person behind it.
Tie every governed action to a person, device, team, model connection, task, and policy revision.
Turn usage, latency, and cost into something finance, security, and engineering can act on—without asking developers to reconstruct the story from logs.
How it works
Register approved providers, endpoints, local runtimes, and model connections.
Set routes and shared skills by organization, team, task, and connection.
Signed policy is verified by Cercano before each inference request runs.
Activity returns with identity, device, task, route, and revision attached.
The Trust Layer
One inspectable policy surface connects identity, model access, data handling, deployment boundaries, and the audit trail behind every request.
One family / Three tiers
The agent developers choose and the control plane the organization needs, designed as one system.
The open-source agent developers live in.
The same agent, persistent and connected.
The managed control plane for the whole AI estate.
The control plane
Cercloud gives regulated teams a governed path to local and cloud AI: enterprise identity, enforceable policy, cost controls, and a complete audit trail without another token reseller in the middle.