How BryanNet works: components and network flow

Prerequisites and authority

Confirm the installed edition and release. Use the glossary and deployment record before selecting an installation path.

BryanNet separates management decisions from network enforcement. It stores customer and subscription state, communicates with routers, and presents information through operator and customer interfaces.

Core components

Component	Role
BryanNet backend and database	Customer, plan, subscription, payment, configuration and operational records
Administrator dashboard	Operator tasks such as managing plans, customers, routers and system operations
Telegram bot	Customer-facing registration, account access, plan/payment interactions and notifications according to edition
Customer website	Customer self-service where the installed edition includes website entitlement
Captive portal / MikroTik Hotspot	Network access entry point managed through RouterOS
Background workers	Time-dependent tasks, synchronization, lifecycle operations and related maintenance
Local control and installation tools	Install, service control and supported update workflows

The customer mobile application is not covered in this documentation release.

Typical interaction

Customer (Telegram or entitled website)
                 |
                 v
      BryanNet backend + database
          |              |
     payment gateway     background worker
          |              |
          +-------> router provisioning
                            |
                            v
                    MikroTik Hotspot
                            |
                            v
                    Customer network access

The exact lifecycle depends on payment method, plan type, and installation configuration. A successful customer payment is not the same thing as a successful router provisioning event: troubleshoot those steps separately.

Management traffic versus internet traffic

BryanNet must be able to communicate with each managed router over the network. Customer internet traffic generally follows the local network and its internet source; it does not need to pass through the BryanNet dashboard. The server may reside on the same LAN or remotely with a secure routed connection.

Edition-sensitive interfaces

The Site edition uses Telegram/captive-portal customer access; do not assume a customer website is available on that edition. Other editions are governed by their verified feature entitlements. Telegram must not be portrayed as universally optional.

Continue: Editions, licensing and feature availability (editions), Network architecture and router connectivity choices (network architecture).