// Use case / Multi-cloud & multi-site

One control plane. Many places to run.

Deploy applications and services across your AWS, GCP and Azure accounts, Cloudflare-style provider runtimes, edge servers and private data centers. Let agents coordinate placement and operations without giving up network or access boundaries.

AgentDeploy provides the shared control plane, not hosting capacity. Actual placement depends on the infrastructure, nodes and provider profiles connected by your organization.

distributed application mapzero-trust paths
AgentDeployAgent-aware control planePlacement, releases, policy, status and operations
providersProvider runtimesCloudflare-style and other third-party ecosystems
cloudAWS / GCP / AzureCustomer-owned public cloud capacity
edgeEdge sitePrivate service with no inbound public port
privateData centerInternal systems and controlled egress
GatewayMeshTunnelscoped identity + policy
A shared control plane coordinates releases and policy while workloads keep the placement and network boundaries of their sites.

// Placement without a dead end

Use each site for what it does best.

Keep public entry, private services and data close to the right users or systems. Workloads can be rescheduled or switched as supported, without rebuilding the management plane around one provider.

01 /

Coordinate several sites

Observe and operate deployments across cloud, edge and private infrastructure through one organization-level control plane.

02 /

Expose services deliberately

Use Gateway, Mesh and Tunnel components so an edge service can remain private and receive traffic through an approved site or unified entry.

03 /

Grant temporary network authority

Allow an agent to request a scoped ticket or temporary policy for a pre-authorized resource, then expire or revoke it after the task.

// Task-scoped network authority

Temporary access follows the task lifecycle

01RequestAgent states the resource and intended operation.
02Scoped grantPolicy limits identity, path, action and duration.
03TaskThe authorized connection exists only for the work.
04Expire / revokeAuthority ends automatically or is withdrawn early.

// What this changes

Provider choiceCombine public cloud, provider runtimes and owned infrastructure.
No exposed edge portRoute through a controlled entry without opening inbound access at the edge.
Safer agent collaborationGive agents and agent-to-agent workflows narrow, time-bound paths.
Operational mobilityReassess placement without adopting a new control plane for every site.

// Next step

Map the sites you already have.

Identify which workloads need public entry, private data access, edge locality or a provider runtime, then define the paths between them.