ISPbills
Online demo

MikroTik control planeUpdated October 2026

MikroTik ISP Operations: RouterOS, PPPoE & RADIUS

Connect RouterOS subscriber access, PPPoE, Hotspot, queues, address pools and live device context to the same billing and support record. ISPbills supports both RouterOS API workflows and centralized RADIUS architectures.

Explore the live demoDiscuss your environment →
  • RouterOS 6 and 7 workflows
  • API and FreeRADIUS operating models
  • No per-router device fee
ISPbills / mikrotik isp operationsRouterOS context live
ISPbills MikroTik monitoring interface with RouterOS device details
Connected workflowRouter health beside subscriber state
v6 + v7RouterOS workflows
API + AAAdirect and centralized models
PPP + Hotspotsubscriber access paths
$0per-router device fee
The operating model

Choose API, RADIUS or a controlled hybrid based on the job.

RouterOS API operations are useful for configuration and direct device actions. RADIUS provides centralized authentication, authorization and accounting. ISPbills makes the distinction visible so teams can design a deliberate access architecture instead of treating every MikroTik integration as equivalent.

01

Connect the router

Register the RouterOS endpoint, verify credentials and use a private management path where the router is behind NAT.

02

Select the access model

Use direct PPPoE or Hotspot workflows, FreeRADIUS, or a tested combination appropriate to the service.

03

Map packages and policy

Relate speeds, profiles, pools, queues and expiry behavior to the subscriber package.

04

Monitor before changing

Review resources, interfaces, sessions and live bandwidth with subscriber and billing context nearby.

Platform capabilities

Everything this workflow needs—without losing the boundaries.

Capabilities shown here are implemented product areas. Device, provider and protocol behavior still depends on the selected integration and environment.

01

PPPoE billing

Coordinate PPP secrets or RADIUS-backed credentials, packages, recurring billing, expiry and reconnection.

02

Hotspot billing

Manage captive access, users, vouchers, plans, walled-garden context and supported payment journeys.

03

RADIUS accounting

Track authentication and session accounting centrally across supported NAS devices.

04

Bandwidth policy

Connect package speeds to profiles, queues and controlled RouterOS configuration workflows.

05

Router monitoring

Inspect health, interfaces, resources, wireless clients and traffic before support teams take action.

06

API automation

Use saved connections and auditable actions for supported RouterOS configuration rather than unmanaged scripts.

Designed for production reality

Use each MikroTik integration for the job it actually owns.

RouterOS API is a management path. RADIUS is an AAA control plane. ISPbills supports both, so operators can choose a direct, centralized or deliberately tested hybrid model.

Read implementation documentation →

RouterOS API

Read device resources, interfaces, VLANs, wireless stations and active PPP or Hotspot context; perform supported device actions.

FreeRADIUS AAA

Centralize credentials, reply attributes, session accounting and compatible disconnect or CoA workflows.

Controlled hybrid

Keep configuration in the API path and subscriber authentication in RADIUS, with explicit ownership and rollback.

Product evidence

Inspect the router before a customer-impacting change.

The live monitor reads CPU, memory, storage, uptime, top interfaces, errors, drops, VLANs, wireless stations and active access counts when the RouterOS API exposes them.

Real ISPbills interfaceProduct data and access vary by configuration
ISPbills MikroTik router inventory and management interface
Interface capture from the current product. Treat your own device, provider and billing configuration as the acceptance environment.
Go deeper

Focused guides for the decisions behind the product.

Implementation guideHow MikroTik ISP Billing WorksPlan the technical lifecycle connecting invoices and verified payments to MikroTik PPPoE or Hotspot policy, suspension, active sessions and restoration.Read guide →Implementation guideMikroTik PPPoE Billing and Subscriber AutomationDesign MikroTik PPPoE billing around subscriber identity, packages, RADIUS or RouterOS, session state, expiry, suspension and reconnection.Read guide →Implementation guideMikroTik Hotspot Billing, Vouchers and Captive AccessConnect MikroTik Hotspot users, captive portal access, vouchers, plans, payments, expiry and customer self-service with ISPbills.Read guide →Implementation guideConnect MikroTik RouterOS to FreeRADIUSPlan MikroTik and FreeRADIUS integration for PPPoE or Hotspot authentication, authorization, accounting and subscriber session control.Read guide →Implementation guideMikroTik Router Monitoring for ISP OperationsMonitor MikroTik availability, resources, interfaces, wireless clients and traffic with subscriber and incident context in ISPbills.Read guide →Implementation guideAutomatically Suspend and Restore Expired PPPoE UsersDesign safe MikroTik PPPoE expiry, suspension and reconnection workflows around billing status, grace periods, sessions and operator overrides.Read guide →
Deployment discipline

Validate the network path before automating customer-impacting actions.

Public product information describes the current operating model. A controlled pilot proves the exact fit for your data, devices, providers and failure cases.

  1. 01
    ConnectivityConfirm routing, VPN, firewall, API port and credential scope from the ISPbills deployment to every managed router.
  2. 02
    Version compatibilityRecord RouterOS versions and test required read and write operations against representative devices.
  3. 03
    RollbackDefine who can approve service-affecting changes and how a failed package, queue or access update is reversed.
Common questions

Straight answers before you deploy.

Need a model-, provider- or migration-specific answer? Bring the exact environment to the team.

Does ISPbills replace MikroTik User Manager?

ISPbills can provide the broader subscriber, billing, payment, support and network operating layer around MikroTik access. Test required User Manager attributes and migration data before replacing an existing deployment.

Does ISPbills use the RouterOS API or RADIUS?

It supports both operating models. API workflows manage supported device configuration and actions; FreeRADIUS centralizes authentication, authorization and accounting.

Can expired PPPoE users be suspended automatically?

Yes, when billing policy and the relevant RouterOS or RADIUS integration are configured. Test timing, grace rules and reconnection behavior before enabling production automation.

Can ISPbills monitor MikroTik routers?

Yes. Supported monitoring includes device resources, interfaces, connectivity, wireless context and live traffic views.

Validate it with your operation

See how ISPbills fits the network you already run.

Explore the current product, then scope compatibility and migration with your actual devices, billing rules and integrations.

Explore the live demoSee pricing