BryanNetProduct architecture and service map
Prerequisites and authority
Use this reference with your installed release. Internal implementation routes and settings are not public integration contracts.
Customer-installed architecture
The deployment contains application interfaces, a FastAPI backend, MySQL, background workers and managed MikroTik routers. Telegram integrates through the bot/backend; the entitled website and administrator interface use the API.
flowchart TD
A["Administrator"] --> API["BryanNet API"]
C["Entitled customer website"] --> API
T["Telegram bot"] --> API
API --> DB["MySQL"]
W["Background workers"] --> DB
API --> R["Managed MikroTik routers"]
W --> R
The diagram is conceptual. It does not imply every worker talks directly to every router or that database access is public.
| Layer | Responsibility |
|---|---|
| Application account | Registration, identity, app sessions and recovery |
| Subscription | Plan entitlement, queue, validity and quota |
| Payment | Economic transaction and verification history |
| Provisioning | Translate entitlement into router access |
| Router session | Runtime internet connection |
| Accounting | Attribute traffic to entitlement/device/router periods |
Customer internet traffic normally follows the site's router/upstream network. Management can be local or routed through a VPN. Provider callbacks enter through stable HTTPS ingress and need separate event verification.
The commercial/public BryanNet Control/CMS platform is outside this customer-product manual. Use Docker services, Compose files and persistent volumes for actual services and Network architecture and router connectivity choices/13 for network relationships.
Related guides
Related guides: Configuration reference (env vars, ports, URLs), Docker services, Compose files and persistent volumes, Database diagnostics and safe query reference, Subscription and provisioning state model.