Tell us what you are building and we will help you choose the right rollout path.
The contact page helps operators understand when to stay in docs and when it is better to discuss rollout, architecture, or compliance constraints directly with the team.
Deployment planning, migration approach, and product-fit discussion.
Commercial and architecture inquiries stay direct instead of anonymous.
Routes into docs, architecture, and app stay visible nearby.
Describe your topology, rollout goals, and constraints.
The more precisely a team describes its current connectivity model, expected scale, and constraints, the faster a useful response can be.
Talk to the Nanami team
We respond to product, architecture, and migration questions. Enterprise inquiries usually receive a same-day reply.
What to include
This helps the team move from form intake to a useful answer faster.
How the team can help
The contact path ends in a clear next step.
Not every visit to the contact page means a call is needed yet.
Often the next step is quickstart, architecture review, or a direct move into the product.
Quickstart
If you are still in evaluation mode, docs will often answer the question faster than the contact route.
Architecture review
If the question is about ownership, topology, or routing model, the architecture page is usually the right first stop.
Launch the app
If the team is ready to try the product, the app entry stays close and unambiguous.
Need a faster path into docs, architecture, or a working environment?
Use the entry point that matches your stage: docs for evaluation, architecture for model clarity, or the app for a direct start.
Need a guided evaluation path?
Docs and quickstart continue the same product-family structure.
Need deeper model clarity?
The architecture route explains the product architecture before a direct conversation.