About Nanami
Built for teams who need private networking they can actually operate.
Nanami was created to remove the operational drag of VPN sprawl. The goal is not to hide networking complexity behind black boxes, but to make it understandable and manageable for real infrastructure teams.
Philosophy
Product principles
How Nanami makes design tradeoffs for infrastructure operators.
Clarity over hidden automation
Infrastructure operators should be able to explain why traffic flows a certain way. Nanami prioritizes explicit models and readable state.
Security as a baseline
WireGuard transport, key-based identity, and scoped enrollment are core assumptions, not optional add-ons.
Design for day-two operations
The product is optimized for ongoing operation: onboarding, troubleshooting, ownership handoff, and growth across teams.
Current focus
What the team is investing in right now.
- Reliable control-plane and gateway lifecycle
- Clear tenant/group/network operational model
- Practical onboarding paths for nodes and gateway infrastructure
- Transparent roadmap labels for incomplete workflows
Roadmap themes
Coming soon
Planned direction, not hidden promises.
- Shared transport gateways (DERP-like) for fallback connectivity
- Multi-hop routing chains and policy-based paths
- Gateway high-availability redundancy (2+ per network)
- Audit and compliance-oriented operational reporting
- Richer policy composition and role template workflows
- Expanded managed client platform coverage