title: Current status and coming soon description: Transparent roadmap: what is available, in progress, and planned.
This roadmap is intentionally explicit. Items are marked by current delivery state.
Status legend
- Available: usable now.
- In progress: active implementation.
- Planned: committed direction, not complete yet.
Platform status
| Area | Status | Notes | | --- | --- | --- | | Core control-plane resources (workspaces/groups/networks/nodes/gateways) | Available | Backed by API and WebUI surfaces | | Gateway manager + gateway daemon registration and state reporting | Available | Join-key workflows and observed-state loops are in place | | WireGuard config generation for nodes | Available | Exposed through node/config endpoints | | Community and SaaS app modes | Available | Shared conceptual model | | Multi-daemon orchestration depth | In progress | Desired-state fan-out and conflict-safe apply paths are maturing | | RBAC and policy UX templates | In progress | Under active refinement | | Audit-friendly access change history | Planned | Priority ops/compliance track | | Advanced traffic analytics and telemetry exports | Planned | Expanding observability phase | | Expanded managed client coverage (Windows/macOS/mobile/Kubernetes) | Planned | Linux-first paths available today | | High-availability control-plane topology guidance | Planned | Self-host and enterprise deployment maturity track |
Coming soon focus areas
Access and governance
- richer permission assignment UX,
- role templates and clearer delegation flows,
- audit-oriented review paths.
Connectivity operations
- broader managed client platform support,
- deeper gateway orchestration controls,
- stronger analytics for routing and traffic behavior.
- enterprise isolation mode (
InterfacePerNetwork=true, VRF/namespaces). - enterprise port pools / port profiles for platform-managed SaaS deployments.
Planning-only fallback transport groundwork
- extend the current shared-region groundwork into a future fallback transport runtime,
- preserve policy boundaries between routing gateways and shared fallback transport,
- keep any shared transport pool explicitly future-only until the current routing baseline is complete.
Routing evolution
- multi-hop routing chains and policy-based paths,
- gateway redundancy policies (2+ per network),
- safer rollout controls for large network fleets.
Deployment maturity
- more HA-oriented deployment references,
- stronger production runbooks and validation tooling.
What is intentionally not promised yet
- Exact delivery dates for planned items.
- Feature parity claims before implementation lands.
When a feature is incomplete, it should remain clearly labeled as coming soon.