Hosting BryanNet on a VPS

Prerequisites and authority

Local installation authority, a complete approved release package, working Docker and access to the deployment record are required. Preserve existing data before installation/update/removal.

Deploy on a VPS

A remote host centralizes management across sites. Customer internet can still break out through each site's internet source; it does not need to transit the BryanNet VPS simply because the management application is hosted there.

Choose a release-supported host with persistent SSD storage, adequate resources, controlled SSH/administrator access and a backup destination independent of the VPS. Verify the platform and Docker requirements before purchasing or provisioning a production host.

1. Establish secure host administration and time synchronization.
2. Install Docker and the selected BryanNet release using Installing BryanNet on Linux or the supported OS guide.
3. Configure HTTPS names for application access.
4. Establish a routed VPN from the VPS to every managed router or site gateway.
5. Restrict router API access to the management source addresses.
6. Verify connectivity from the API runtime, not only an interactive host shell.
7. Complete setup, test customer access and configure off-site backups.

Keep host backups distinct from BryanNet encrypted application backups. A provider snapshot is useful but does not replace a tested application restore procedure.

For multiple sites, allocate non-overlapping management networks and use Internet sources and multi-site network topology. Record DNS, tunnel configuration, restore prerequisites and license transfer requirements in the deployment record. Losing the VPS must not also remove the only backup and its recovery key.

Related guides

Related guides: First-deployment walkthrough and success checklist, Deployment verification and first login, Back up BryanNet and validate backups, Restore BryanNet safely, Product updates, compatibility and rollback.