BryanNetChoose a deployment model: local vs hosted server
Prerequisites and authority
Confirm the installed edition and release. Use the glossary and deployment record before selecting an installation path.
BryanNet can be deployed near the network it manages or on a remotely hosted server. The choice depends on the number of sites, router reachability, staff access and integrations.
| Deployment model | Best fit | Key requirement |
|---|---|---|
| Local Windows mini PC / Linux server | A small site with admins on the local network | Stable local power/network and a reachable router API |
| Local server with secure public callbacks | Small site keeping management private while enabling online payments | Stable HTTPS address for webhooks; no public database exposure |
| Hosted VPS/cloud server | Central management or remote administration | Secure routed connectivity from server to each router |
| Central multi-site deployment | Many routers across one or more internet sources/locations | Documented site addressing and reliable gateway/VPN paths |
Internet-source layout is separate from management layout
One internet source may serve several routers, and multiple sites may each have their own sources. The server location need not match any of them. Register and manage the actual routers individually, using the supported multi-router configuration.
Public connectivity without exposing everything
A local installation can keep its admin page inside the LAN and expose only what external providers need, using a stable secure endpoint. A persistent named Cloudflare Tunnel may be simpler than operating a public reverse proxy for a small installation. Temporary/quick tunnels are suitable for testing, not reliable production callbacks because their addresses are temporary.
Cloudflare Tunnel makes a web/API endpoint accessible but does not automatically connect BryanNet to remote router APIs. Remote router management requires LAN/routed VPN reachability of its own.
For Bachs, Paystack and Flutterwave, include payment-provider callback reachability in this decision. Follow Payment gateway sandbox verification to verify the chosen provider's callbacks before accepting live payments.
Choosing
Prefer the simplest deployment that meets reliability and recovery needs. A single-site installation may work well locally. A multi-site organization may benefit from central administration, but should design routing, failure domains and backup strategy first.
Continue: LAN access, firewall, DNS and HTTPS (network/HTTPS), Network architecture and router connectivity choices (topologies).
Related guides
Related guides: Deployment verification and first login, Add and bootstrap a router in BryanNet, Customer journey: register to first connection, Daily operational checks.