Log in Get started free

Billing and paymentsInvoices, vouchers and mobile money that reconcile themselves RADIUS and subscribersPlans, sessions, suspension and instant reconnects

Hotspots and vouchersBranded splash pages and voucher batches Network monitoringUptime for every tower and POP

Customer portal Field and agent app Integrations Security Changelog

New Agents collect payments in the field with the agent appLearn more →

WISPsWireless ISPs and tower networks FTTH providersFibre-to-the-home networks

Hotspot operatorsPlazas, malls and cafés Estates and MDUsShared connectivity for compounds and blocks

Ghana Togo Migrate from spreadsheets Compare options

Switching? Moving from another system or spreadsheetsRead the migration guide →

DocsGuides, tutorials and reference API referenceEndpoints, webhooks and errors

Guides Changelog Status Glossary Free tools Sitemap

Need a hand? Chat with us while you set upWhatsApp →

Draft documentation. Check each step against the product before publishing.

Docs / Concepts

How tenant data stays separate

3 min read

How OneRezo keeps each ISP’s data apart on shared infrastructure.

Tenants

Each ISP is a tenant. Its subscribers, invoices and sessions belong to that tenant only.

Row-level security

Access is enforced at the data layer with row-level security, so a query made on behalf of one ISP cannot return another ISP’s rows, whatever the request asks for.

Read more on the security page.

Was this page helpful?

PreviousSoft suspension and the payment page NextPlans, services and sessions