Six ways operators earn on NetOS. Which one is yours?

An estate or compound hotspot lives or dies on how little you have to touch it. Residents want to connect and pay without finding you first.

A resident opens your branded portal, picks an hour, a day or a week, pays by mobile money, and is online before they have put their phone away.

Your MikroTik runs the hotspot; NetOS generates its configuration and keeps RADIUS checking every connection against a paid plan.

When a plan runs out the customer is disconnected, and when they pay again they are reconnected. You are not the one flipping a switch at 11pm.

You see active sessions, revenue and who is online from your phone, without walking round the compound.

A shopping centre hotspot sees hundreds of different phones a day, most of them once. The portal has to do all the selling, because you cannot.

Your pricing and branding are the first thing a shopper sees when they connect: pick a pass, pay, get online.

Price a quick browse or a full afternoon, with a data cap that matches what you are willing to give at that price.

A go-live check tells you at setup whether your router is actually letting customers authenticate, so you hear it from NetOS rather than from an empty revenue day.

SMS and WhatsApp confirm payments, so you are not answering “did my payment go through?” all day.

Students want WiFi priced by the day or the week, not a monthly contract they cannot commit to, and they want it to work the moment they pay.

Set a price, a duration and a data cap that matches what a student will actually pay.

Add a whole block of tenants at once instead of one account at a time, which matters at the start of a new intake.

At move-out, expired accounts stop pulling bandwidth without you remembering to disable anyone.

Students already pay for everything by phone. WiFi works the same way, through the portal, with no separate app.

A café or kiosk hotspot is a small, simple business, and the WiFi should be too. A customer asks for the code, pays and connects.

Vouchers can be short and cheap, an hour or two, priced for someone who is only there for a coffee.

The portal carries your branding, so it looks like your shop offered it, not a third-party tool.

RADIUS checks every session, so a customer cannot stay online past their voucher just by staying in their seat.

One dashboard shows what the WiFi earned that day, next to everything else you track.

Once you run more than one location, a second estate or a second kiosk, checking each one separately stops working.

Every site gets its own customers, pricing and captive portal branding under one account.

Staff get access scoped to what they need. Someone who sells vouchers does not need your payment settings.

Revenue and active customers roll up across every site, so you know which location earns without visiting each one.

A new site means registering a new router. The platform does not need rebuilding for you to grow.

Some hotspot customers stop being occasional. The shop next door wants WiFi every day, not a voucher every day.

PPPoE runs alongside the hotspot on the same router and the same account, so a dedicated connection does not mean a second platform.

Fibre works the same way: provision the ONU from NetOS and bill the line like any other subscription.

The customer moves from daily passes to a monthly subscription; your billing, RADIUS and dashboard do not change.

Subscriptions renew and lapse on their own, the same way vouchers do. No due dates kept in a notebook.