Security

In Nanami, identity, enrollment, and transport posture read as one security surface.

Nanami builds trust by explaining how operators see access scope, gateway mediation, route intent, and rollout posture in one clear model instead of through slogans.

Scoped
Access

People, access scopes, and permissions remain part of an inspectable ownership model.

Visible
Transport

Direct and mediated paths are not hidden from operator review.

Reviewable
Change model

Policy intent and route effect are easier to explain to a team or reviewer.

Identity and access chain

Role scope and session state gate every network action.

OperatorRole bindingWorkspace scopeNetwork policyNode accessSession + MFA

Gateway path stability

Regional gateways preserve connectivity when peer-to-peer links fail.

node-westgateway-westgateway-coregateway-eastnode-eastmobile-node
Security posture

Security is built around inspectable operator workflows.

A trustworthy security surface depends on whether the team can understand access relationships, enrollment posture, and transport behavior without jumping between different models.

Scoped access

Access relationships stay attached to the ownership boundary and remain visible beside infrastructure context.

People and access scopes stay explicit
Permissions align to ownership
Review starts with known scope

Secure enrollment

The join flow reduces chaos instead of adding hidden state and unclear steps.

Short-lived enrollment path
Guided next step surfaces
Lower blast radius at first join

Gateway mediation visibility

Teams can see when traffic is direct and when the path remains gateway-mediated.

Direct vs mediated understanding
Operational path visibility
Fewer hidden transport assumptions

Route intent

Route control lives beside the network and gateways, so the security effect is not buried in forms.

Intent close to network boundary
Policy effect easier to inspect
Operator review stays contextual
Review path

Identity review and gateway review live in one product.

The product model carries teams from role scope into session and path review without hidden transitions.

Identity and access chain

Role scope and session state gate every network action.

OperatorRole bindingWorkspace scopeNetwork policyNode accessSession + MFA

Architecture review

Inspect the entity model and control flow before making rollout decisions.

Quickstart and docs

Move from security framing into a practical rollout sequence.

Deployment choice

The pricing page helps teams choose between the Community path, SaaS Enterprise, or the contact path without changing product logic.

Next deployment step

Need a platform where security does not split into detached tabs and hidden state?

Choose the right deployment path, open rollout docs, or move into Nanami with the same inspectable security posture.

Need rollout docs?

Quickstart and docs turn the security posture into a practical deployment sequence.

Need deployment guidance?

The team can connect security review to migration, rollout, and support requirements.