Skip to content
OrbitMeshProgrammable connectivity
Open Console

Agent-native. Infrastructure-owned.

Programmable connectivity.For agents and infrastructure.

Connect agents, services, servers, and edge nodes through one control plane. Route traffic, build private networks, expose services, and manage network paths across the infrastructure you control.

Deploy your first nodeSee how it works
Bring your own nodes Pull-based control Safe local rollback
LIVE TOPOLOGY
fra-entrytraffic.entry
tokyo-edgetraffic.exit
home-labmesh.node
ORBITMESHcontrol planeintent -> desired state
PATH / AI-APISfra-entry -> tokyo-edge
48 msHEALTHY
3 nodes2 active rolesrevision 42desired state / synced

Work that happens without a browser

Coding agentsCI runnersModel APIsMCP serversPrivate services

01 // Why OrbitMesh

Agents don't live in one network.

A single task may need the Internet, a private database, a remote GPU, an MCP server, and a public callback endpoint. Most teams stitch those paths together with separate proxies, VPNs, gateways, and tunnels.

OrbitMesh gives agents and workloads one programmable network model instead of five disconnected systems.

02 // Capability model

One control plane instead of four networking tools.

Traffic routing, private mesh, service ingress, and public tunnels share the same nodes, identity, health model, policy, and lifecycle.

01Available now

Traffic

Entry / Exit / Relay

Give workloads a reliable path to model APIs, Git, package registries, crawlers, and regional egress.

02Available now

Mesh

Peer / Relay / Subnet

Let agents reach databases, GPUs, NAS devices, servers, and private services without making them public.

03Available now

Gateway

HTTP / TCP / UDP

Give APIs, MCP servers, agent endpoints, and internal applications a stable way in.

04Available now

Tunnel

Private to public

Expose local services, preview environments, callbacks, and agent runtimes only when they need to be reachable.

03 // Automated workloads

Built for work that happens without a browser.

Coding agents, CI runners, model clients, package managers, crawlers, remote runtimes, and long-lived services need connectivity that software can declare and observe.

01

Git and releases

Stable paths for GitHub, Git LFS, package releases, and long-running clones.

02

Containers and packages

Predictable pulls from registries, npm, PyPI, crates, and build infrastructure.

03

AI APIs and agents

Durable sessions for coding agents, model APIs, MCP services, and remote workspaces.

04

SSH and private services

Reach developer infrastructure without turning every private host into a public island.

Runtime plugins
sing-boxTailscaleTraefikratholeTailscale DERPEasyTierEnvoy
Agent-native, not an agent platform.

OrbitMesh manages connectivity. Third-party agent platforms manage runtimes, environments, task execution, and agent lifecycle on top of that network layer.

04 // How it works

Declare the path.Let every node do the work.

Stop hand-editing network configs across scattered machines. OrbitMesh compiles user intent into runtime configuration, then keeps desired state and actual state aligned.

One operating model

Nodes, capabilities, runtimes, endpoints, and policy share a consistent lifecycle.

Health you can act on

See node reachability, runtime state, endpoint readiness, and the path traffic will take.

Control without intrusion

Nodes pull desired state and reconcile locally. The control plane never needs to SSH in.

User intentSend AI traffic through US West
Control planeCompile policy and desired state
Edge runtimeApply, probe, report, reconcile
Network pathEntry, relay, healthy exit

05 // Edge runtime

Control centrally. Reconcile locally.

OrbitMesh keeps product decisions in the control plane and runtime execution on the node. If connectivity drops, the last known good configuration keeps running.

01

Enroll

Join a Linux host with one command. OrbitMesh installs the edge runtime and registers node identity.

02

Declare

Choose the network capability and role. The control plane compiles intent into desired state.

03

Reconcile

The node pulls configuration, applies the runtime locally, reports health, and can roll back safely.

edge-01 / enroll
$ curl -fsSL https://install.orbitmesh.dev | sudo env ORBITMESH_DEPLOYMENT_TOKEN=... sh

node identityregistered

edge runtimeinstalled

desired staterevision 42

runtime bindings4 converged

capabilities4 ready

> node online. reconciling

Runtime plugin modelsing-box, Tailscale, Traefik, and rathole run behind one stable control-plane contract.

06 // Private networking and exposure

Private networks and public paths. One model.

Traffic, Mesh, Gateway, and Tunnel run on the same nodes, identity model, and desired-state workflow.

Available now

Mesh

Peer / Relay / Subnet

A private overlay for the machines you already own — workstations, home labs, servers — reachable under one identity, with nothing exposed to the internet.

  • Peer-to-peer paths: DIRECT connections, DERP relay fallback.
  • Subnet routing brings a whole network behind one node.
  • SSH, file sync, and internal services without public endpoints.
$ orbitmesh mesh join --subnet 192.168.1.0/24
Available now

Gateway

HTTP / TCP / UDP

Service ingress on your own nodes: domains, TLS, and routing compiled from intent — no managed load balancer required.

  • Automatic TLS issuance and renewal per domain.
  • Weighted, health-checked upstreams with failover.
  • HTTP, TCP, and UDP routing from one declaration.
$ orbitmesh gateway route api.example.dev --upstream api-eu,api-us
Available now

Tunnel

Private to public

Expose a private service to the public internet on purpose — scoped, relay-backed, and revocable at any time.

  • One command from localhost to a public URL.
  • Relay-backed endpoints keep the origin address private.
  • Time-boxed shares that expire on their own.
$ orbitmesh tunnel share localhost:3000 --expires 2h

07 // Where it runs

Runtimes first. Clients when you need them.

Machines, runtimes, workloads, and agents are first-class network participants. Human clients connect through the same identity and policy model.

Workloads and runtimes

Install the Edge Runtime where services and automated workloads already run.

Linux

daemon + cli

Available now

Cloud VM

edge runtime

Available now

Docker

container runtime

Available now

NAS

user-owned edge

Available now

Edge Device

remote node

Available now

Agent Environment

automated workload

Available now
Human clients

Use native clients when a person needs access to the same network resources.

macOS

network extension

Available now

Windows

system proxy

Available now

iOS

network extension

Available now

Android

full vpn

Available now
EDGE RUNTIME$ curl -fsSL https://install.orbitmesh.dev | shLINUX/AMD64LINUX/ARM64

Servers, VPSes, home NAS - enroll, converge, and stay reconciled.

Your nodes. Your network. Programmable by software.

Make networking programmable.

Open OrbitMesh ConsoleExplore documentation