Your first hour

This page takes you from nothing to a subscriber who can authenticate. It assumes you have a router you can configure and about an hour.

Create your tenant

Start a trial from the instance's home page. Sign-up asks for an email address and a mobile number and verifies both, then places you in your own tenant with an owner account.

Your tenant has its own address, of the form your-slug.the-instance-domain. That address matters more than it looks: a session lives on one host, and the API, the subscriber portal and the panel all expect to be reached there. Use the host you see in the browser after signing in.

Create a plan

A plan is what a subscriber is sold: speed, quota, validity, price, and the behaviour when the quota runs out. Create one under Plans.

The smallest useful plan sets a download and upload rate and leaves everything else unlimited. You can add a data quota, a time quota, a session limit and a fair-use chain to another plan later — each of those is a separate switch, and one that is off costs nothing at authentication time.

Create a subscriber

Under Subscribers, create one with a username, a password and the plan you just made. A subscriber is identified by the pair of your tenant and that username, so a name another operator on the same instance already uses is still available to you.

Add your first network device

Under Network, add the router that will send the RADIUS requests. You need its address and a shared secret; the same secret goes into the router.

If it is a MikroTik, do not type any of this by hand — generate the onboarding script instead and paste it into the router's terminal. That path is described in Onboarding a MikroTik router.

Watch the live log

Open Logs. The RADIUS log is a live stream, not a page you refresh, and it shows every authentication decision as it is made, with the reason attached.

Now make the router authenticate: connect the subscriber. An Access-Accept with your plan's reply attributes is the end of this page.

If it did not work

Read the live log first — the rejection carries its own reason. The four common ones:

• Nothing appears in the log at all. The request is not reaching the instance. Check the router's RADIUS server address and that UDP 1812 and 1813 are open outbound.
• The tenant could not be resolved. The device's address or identifier does not match what you registered under Network. The device is how the instance knows which tenant a request belongs to.
• The shared secret does not match. The router and the Network entry must carry the same one, character for character.
• The subscriber is rejected. Check the account is active, the plan is attached, and the expiry date has not passed.