All key operator capabilities are organized as one operating workflow.
Nanami brings day-one onboarding, day-two operations, and combined transport plus access control into one operator workflow.
Marketing, docs, and app now move through the same product language.
First-run flows lead into network creation, enrollment, and policy instead of dead empty screens.
Control, routing, and observability stay inside one operating path.
Policy application path
Intent rolls from workspace policy to concrete gateway behavior.
Capabilities are explained through working models rather than disconnected promises.
Capabilities are grouped around real operator jobs.
Nanami is organized around clear layers: operational clarity, data-plane resilience, security by default, and team workflows.
Operational clarity
Organize infrastructure with teams, environments, and reusable network policy patterns.
Data-plane resilience
Build resilient paths using gateway nodes and region-aware topology controls.
Security by default
Enforce secure enrollment and reduce blast radius with layered permissions.
Team workflows
Enable platform, SRE, and security teams to collaborate with less friction.
Deployment flexibility
Run Community or SaaS Enterprise with a unified product model and UX.
Operational confidence
Move from reactive fixes to proactive operations with integrated visibility.
The feature set is anchored to concrete operator patterns.
The feature set resolves into inspectable workflows: policy application, gateway path stability, and identity-aware access review.
Policy application path
Intent rolls from workspace policy to concrete gateway behavior.
Gateway path stability
Regional gateways preserve connectivity when peer-to-peer links fail.
Identity and access chain
Role scope and session state gate every network action.
Each capability points to the next useful step.
Teams can move from feature evaluation into docs, architecture, security review, or a live environment without losing context.
Quickstart
Inspect the first production-shaped flow from network creation into node enrollment.
Architecture
Review the ownership, topology, and routing model before the first rollout.
Security review
Check how identity, gateways, and route intent become one inspectable security surface.
Need a platform that does not split into disconnected subsystems?
Move into rollout planning, open the docs, or launch Nanami with the same product language you see here.
Need the Community path?
Community docs keep the same product model and a truthful operator path.
Need rollout guidance?
Pricing and direct contact help teams choose the right Community, SaaS Enterprise, or planning path.