Module · Packages & Policies
Change a policy. The network follows.
A package is the commercial object — price, validity, who may sell it. A policy is the network object — rate limit, pool, attributes. Bind them once and every activation, renewal and login enforces both.
What it does
Built in, not bolted on.
Packages
Speed, validity, retail price — the thing your dealers actually sell, defined once and assigned down the chain.
Retail & wholesale pricing
Every assignment carries its own wholesale price per tier. The same package earns differently through different chains — by design, not by spreadsheet.
RADIUS policies
Rate limits, IP pools, session attributes. Edit the policy and the next authorization — or a CoA to live sessions — applies it.
Dictionary import
Upload vendor dictionaries and use any attribute your BRAS understands — Mikrotik-Rate-Limit today, something else tomorrow.
Activations & renewals
Activating a package writes the wallet ledger, the expiry date and the RADIUS profile in one transaction.
Bulk import
Migrating from another panel? Import packages and customers in bulk and keep their expiry dates intact.
Package → policy → session
The price list and the network config are the same object.
25M-Fibervalidity ........... 30 daysretail ............. 10.00policy ............. fiber-25m policy fiber-25m → radreplyMikrotik-Rate-Limit = "25M/25M"Framed-Pool = "dreamnet-active" ; dealer activates ahmed.kwallet debit ......... 9.00expiry set ........... 2026-08-02next login ........... 25M/25M from pool- 01
Commercial and technical, bound
Sales thinks in packages; the network thinks in policies. Binding them means nobody ever sells a speed the BRAS was never told about.
- 02
Edit once, applied everywhere
Upgrade the 25M profile to 30M and every subscriber on it gets the new rate at next authorization — or immediately, via CoA.
- 03
Assignment is permission
A reseller can only sell packages you assigned to them, at the wholesale price you set. The catalog is the control.
Screenshot coming — the package editor with its bound policy and per-tier pricing, captured from the live product.
What it replaces
Retire the workaround.
The BRAS profile saying 20M while the price list says 25M, and the customer's speed test settling the argument publicly.
One object defines both. The sold speed and the enforced speed cannot diverge.
Creating a new plan meaning edits in the billing panel, the RADIUS config and every dealer's WhatsApp.
Create the package, bind the policy, assign it down the chain — dealers see it in their panel with their price.
Speed changes that require touching every subscriber by hand.
Change the policy once. Sessions pick it up at reauthorization or by CoA — zero per-customer edits.
Keep exploring