NetSeed App
Install on supported user devices that need to consume authorized Nodes, Services or an Exit.
Deployment planning
Place each component where its job belongs.
Run the App on user devices, use ns on servers and terminals, manage identity and Space configuration through NSD, and place only the NSGW roles your connection paths require.
EndpointsControl serviceRole-based gateways
Deployment mapPlanned by role
Appuser devices
nsservers · terminal
NSDidentity · Space · configuration
NSGWonly required roles
Your resourcesoffice · cloud · IDC
Component placement
Start from responsibilities, not labels.
The right topology follows the users, resources and connection paths that actually exist.
ns
Install where a server joins a Network, provides a Node or declared Service, or where terminal automation is required.
NSD
Provides sign-in and the Organization, Network, member, Grant, resource and gateway configuration model.
NSGW
Place Relay, Service Egress, Internet Exit or Public Ingress where that role is required. Each role has its own readiness.
Operating model
Managed, self-operated or hybrid are planning choices to confirm.
These categories describe possible ownership boundaries, not automatic entitlements. Confirm the supported topology, responsibility split, updates and operating process for the actual delivery arrangement.
Reduce the platform work your team owns
Define which control and gateway services are operated for you, which endpoints remain yours and how changes are coordinated.
Keep agreed components in your environment
Confirm supported infrastructure, upgrade ownership, monitoring, backup and recovery before treating this as the target model.
Split ownership by component or location
Document exactly who operates NSD, each NSGW role and every endpoint group instead of assuming one label explains the topology.
Rollout checklist
Make the desired path explicit before deployment.
A small inventory prevents a broad platform diagram from hiding the decisions that affect the first working connection.
1 · Spaces
List the Organizations and Networks, their owners and which users should enter each Space.
2 · Resources
Identify Nodes, protocol-host-port Services, company Exits and any public applications.
3 · Gateway roles
Map only the Relay, Service Egress, Internet Exit and Public Ingress roles each Network needs.
4 · Operations
Assign configuration, upgrades, observability, incident response and recovery ownership for every component.
Plan from real requirements
Confirm the topology before promising the outcome.
Use the product documentation to inventory components, roles and prerequisites for your first production path.