Run close to data and devices
Place compatible workloads in an edge site, homelab or private data center while keeping them in the same application model.
// Solution / Secure edge & private infrastructure
Use customer-side runtime software, identity-aware paths and temporary policy to deploy and operate services in edge, homelab and private data center environments.
Availability depends on registered nodes, runtime capabilities and configured identity, gateway, mesh and tunnel services.
// Private by default
Stable public entry can live at an approved gateway while edge and private services connect outward through controlled paths.
Place compatible workloads in an edge site, homelab or private data center while keeping them in the same application model.
Use an approved gateway and stable address even when the workload moves or the private site has no public inbound port.
Limit agent and agent-to-agent paths to pre-authorized resources, actions and task lifetimes.
// Next step
Define the identity, route, action and lifetime before inviting an agent into the workflow.