Devices
Enrollment, monitoring, inventory, and device lifecycle management.
Networking
Mesh networks, VL1 overlay, peer connectivity, and network topology.
Policies
Network and DNS policy actions, scoping, and evaluation order.
Edge Endpoints
Promoted mesh nodes with anchor, relay, egress, DHCP, and print server capabilities.
DNS & DDNS
DNS resolution, policy-based routing, mesh-assisted DNS, and dynamic DNS updates.
Identity & Access
Users, groups, SSO, and authentication configuration.
Security
Key management, trust chain, TUF, and compliance.
Jobs & Scripts
Remote execution, ScriptPack management, and job lifecycle.
Monitoring
Telemetry, alerts, health endpoints, and observability.
Billing & Plans
Subscription plans, usage, and billing management.
Frequently Asked Questions
Quick answers to common questions.
The ORBTR agent supports macOS, Linux, and Windows. On Linux it runs as a systemd service, on macOS as a launchd service, and on Windows as a Windows Service.
No. ORBTR uses UDP hole-punching via the VL1 overlay for direct P2P connections. If hole-punching fails, traffic is relayed through edge endpoints with relay capability. No static IPs or port forwarding are required.
The agent uses TUF (The Update Framework) for secure, verified updates. Artifacts are signed with root/targets keys and verified before installation. Updates are staged by channel (stable, beta, canary) with automatic rollback on failure.
Yes. Edge endpoints with DHCP Server capability can issue IP addresses to non-mesh devices on a local network adapter and bridge their traffic into the mesh network.