Frequently asked questions

BryanNet brings customer accounts, internet plans, subscriptions, devices and supported MikroTik router management into one software installation. Customer access options depend on the licensed edition.

You provide the infrastructure, internet connection and working network. See Platform for the product overview.

The software licence does not include internet service, routers, other hardware, domains, hosting or third-party charges. You arrange these for your deployment.

Software setup and connection of an agreed initial router set are separate from network design, cabling and general network installation or maintenance.

Start with the customer interfaces and operating features you need, then review customer, router, administrator and location allowances. Site is for one location; Business adds the customer website, reporting, analytics and multi-location management.

Professional includes advanced reporting, analytics, administration and integrations. Enterprise has negotiated scope, including customer mobile apps. Compare the current terms on Pricing.

Site provides Telegram and captive portal customer access, alongside customer, plan, subscription, device and session management. It does not include the separate customer website or customer mobile apps.

Choose Business or above for the customer website, and discuss Enterprise if customer mobile apps are required.

Professional includes advanced reporting, analytics, administration and integrations, as well as higher included capacity. Its advanced features are part of the edition; they are not unlocked by purchasing capacity add-ons.

Customer mobile apps remain Enterprise-only under the current edition policy. Confirm any specific integration requirement in your quotation.

Customer Android and iOS apps are Enterprise-only under the current edition policy. Site, Business and Professional do not gain mobile access through capacity add-ons.

Discuss mobile deployment and branding requirements as part of your negotiated Enterprise scope.

All BryanNet software licences are annual. The purchased edition covers 12 months of software use within the licensed capacity; Enterprise commercial scope and pricing are negotiated.

Deployment is a separate charge. Software updates and ongoing support follow the terms agreed in your quotation.

The annual licence covers use of the purchased software edition within its licensed capacity. Deployment covers the separately agreed setup work on infrastructure you provide.

Review the deployment scope and exclusions before accepting a quotation. Hardware, hosting, internet service and third-party charges are separate.

NGN is the binding pricing currency. Any USD display is an approximate conversion for reference, rather than a separate contractual price.

Use the NGN amounts and terms in your reviewed quotation when planning the purchase.

Annual capacity add-ons increase approved customer, router, administrator or eligible location allowances within your edition. They do not change the edition or enable unavailable features.

Site remains limited to one location. Business and Professional can include approved additional locations; Enterprise capacity is negotiated.

Capacity counting includes stored inactive records, not just connected customers, active routers or enabled administrator accounts. Check the effective signed limits shown in the licence screen when planning growth.

Per-customer device rules are separate from the customer, router, administrator and location capacity allowances.

The calculator provides an annual estimate, and a quote request records your requirements for commercial review. Neither action accepts a binding quotation, takes payment or grants a licence.

The team reviews the scope and pricing before an offer is accepted. Mid-term changes and any proration require separate commercial review.

Renewal retains existing quantities unless revised terms are explicitly agreed. Arrange changes through commercial review and the supported licence workflow.

A smaller licence does not delete your records, but existing over-limit records can prevent further additions. Downloading an expired licence again does not extend its validity.

BryanNet can be planned for a local server or a hosted server on infrastructure you provide. The application needs a working management path to each supported router.

A hosted installation does not mean your customer internet traffic must pass through the BryanNet server. Agree the host and connectivity design before deployment.

Windows and Linux are the intended installer platforms, using the supplied Docker containers. Confirm the operating system version, CPU architecture and Docker requirements against the chosen release before installation.

The existence of an installer does not establish compatibility with every operating system version or distribution.

Size the host around the workload: customers, simultaneous connections, routers, locations, payment activity, accounting and reporting. Allow storage for the database, logs and retained backups.

A universal minimum or subscriber-per-server guarantee is not established in the current sizing draft. Have the proposed host reviewed and validate it with representative workload tests before committing to production.

BryanNet manages supported MikroTik routers through RouterOS API connectivity. Confirm your router models, RouterOS release, authorised API access and network reachability for the proposed deployment.

Do not assume every router model, firmware version or existing configuration is compatible. Agree and test the initial router set within the deployment scope.

Plan a routed management connection, such as a VPN to a router or site gateway, with the required forward and return routes. Test connectivity from the application runtime as well as the server host.

A public web tunnel provides web ingress; it does not replace the router management connection or distribute internet between physically separate sites.

The internet source may be fibre, wireless, cellular, satellite or another upstream service. The management requirement is a working IP path to each supported router.

Your provider, distribution network and router configuration determine customer connectivity. Review and test the proposed topology; this is not a compatibility guarantee for every provider or network arrangement.

Prepare suitable hardware or hosting, internet connectivity, a working network and authorised access to the agreed routers. Supply required domains, third-party accounts and credentials, branding assets, plan requirements and supported import data.

Nominate administrators for training and agree the go-live schedule. See Pricing for deployment responsibilities and exclusions.

BryanNet supports time-based and usage-based plan workflows. A time plan is bounded by validity; a usage plan is bounded by its quota or validity end. Plans also have configured speed and concurrency rules.

A configured speed limit is not a guarantee of upstream internet performance. Review the actual plan details before offering them to customers.

Confirm the provider supported by your installed release, edition and organisation configuration before promising a checkout option. Payment setup uses your approved provider account and the required API keys and callback configuration.

You arrange provider registration, verification and approval. Test the selected integration in its sandbox before enabling live payments; third-party charges are separate.

A browser return alone must not establish payment success. The supported integration verifies provider events and payment status through the backend.

If payment appears pending or access has not activated, use the operator's supported investigation workflow. Do not treat an unverified browser message as proof of payment.

Supported standard data or CSV imports can be included where applicable in the agreed deployment scope. Prepare records in the required format and confirm what will be imported before setup.

Data cleanup and custom migration are excluded from standard deployment and require a separate agreement.

BryanNet includes device and active-session management, with plan-based concurrent-device rules. These rules help an operator manage how an account is used.

A customer's device allowance is separate from the installation's licensed customer and router capacities. Confirm the intended access policy during setup.

Use individual staff accounts and roles with the permissions needed for each person's work. Effective permissions, organisation modules and licence availability determine access; a role name or visible menu alone does not establish authority.

Review permissions when responsibilities change and confirm the selected release's behaviour for protected actions and existing sessions.

Create or import student and resident accounts, assign the appropriate access entitlement, and manage validity, subscriptions and permitted concurrent devices. Access can expire or be revoked when eligibility ends.

Institutional identity integration and automatic student-status synchronisation require a separately agreed integration scope. Available features depend on the edition.

Create individual guest accounts and assign time-bound access entitlements. An authorised administrator can review sessions and devices, let access expire or revoke it when a guest leaves.

Automatic hotel PMS check-in, checkout and room synchronisation are separate integrations, rather than part of the standard guest-access workflow.

Estates can use time-based entitlements for included access or paid plans where subscriptions are sold. Individual accounts, validity and device rules help keep access aligned with eligible residents.

Automatic links to property-management or tenancy databases require an agreed integration. Edition and deployment configuration determine available features.

BryanNet brings plans, prices, payments, subscription activation, renewals and supported MikroTik access management into the operator's workflow. Customer self-service and reporting depend on the licensed edition.

Confirm supported routers, payment configuration and capacity for your deployment. See Solutions for the ISP and WISP use case.