One operating model
Nodes, capabilities, runtimes, endpoints, and policy share a consistent lifecycle.
OrbitMesh turns your servers and managed nodes into one observable network control plane - built for Git, containers, APIs, SSH, and always-on agents.
NETWORK WORK, NOT PAGE VIEWS
01 / CONTROL PLANE
Stop hand-editing network configs across scattered machines. OrbitMesh translates user intent into runtime configuration, then keeps desired state and actual state aligned.
Nodes, capabilities, runtimes, endpoints, and policy share a consistent lifecycle.
See node reachability, runtime state, endpoint readiness, and the path traffic will take.
Nodes pull desired state and reconcile locally. The control plane never needs to SSH in.
02 / CAPABILITY MODEL
Runtime software is replaceable. The network intent, resource model, and operational workflow stay consistent.
Entry / Exit / Relay
Reliable developer access with client profiles, policy routing, health-aware paths, usage, and quotas.
Peer / Relay / Subnet
Private networking for workstations, home labs, servers, and remote environments under one identity model.
HTTP / TCP / UDP
Service ingress with domains, TLS, routing, load balancing, and runtime-backed configuration.
Private to public
Purpose-built exposure for private services, temporary shares, and relay-backed public endpoints.
03 / FROM HOST TO HEALTHY
OrbitMesh keeps product decisions in the control plane and runtime execution on the node. If connectivity drops, the last known good configuration keeps running.
Join a Linux host with one command. OrbitMesh installs the edge runtime and registers node identity.
Choose the network capability and role. The control plane compiles intent into desired state.
The node pulls configuration, applies the runtime locally, reports health, and can roll back safely.
$
curl -fsSL https://install.orbitmesh.dev | sudo env ORBITMESH_DEPLOYMENT_TOKEN=... shnode identityregistered
edge runtimeinstalled
desired staterevision 42
sing-boxhealthy
traffic.exitready
Node is online and reconciling
04 / DEVELOPER TRAFFIC
Developer connectivity is a chain of APIs, package registries, long-lived sessions, private endpoints, and automated agents. Treat it like infrastructure.
Stable paths for GitHub, Git LFS, package releases, and long-running clones.
Predictable pulls from registries, npm, PyPI, crates, and build infrastructure.
Durable sessions for coding agents, model APIs, MCP services, and remote workspaces.
Reach developer infrastructure without turning every private host into a public island.
YOUR HOSTS. YOUR PATHS. ONE CONTROL PLANE.