Multi-Tenant ISP Software — Scale Your ISP Portfolio on One Platform
Run multiple ISPs on one NowaCRM platform with complete data isolation, per-tenant branding, separate billing, and independent partner hierarchies.
Quick answer
Managing multiple ISP entities — whether as a holding company, a franchise network, or a SaaS provider — requires rock-solid tenant isolation. NowaCRM's multi-tenant architecture ensures every ISP runs independently on the same platform — separate data, separate branding, separate billing, but unified management.
Database-Level Tenant Isolation
Every database query in NowaCRM is automatically scoped by tenant_id through the TenantScopedModel base class. Subscribers, invoices, payments, tickets, inventory — all data is isolated at the query level. Even if a developer forgets to add a filter, the global scope ensures no data leakage between tenants. This is an architectural invariant, not an optional feature.
Per-Tenant Domain & Branding
Each ISP gets its own subdomain (e.g., skpc.nowacrm.in) or custom domain. The system resolves tenant context from the domain automatically. ISP-specific branding (logo, colors, company details) is displayed in the portal and on invoices. Each tenant is a fully independent ISP from the subscriber's perspective.
Independent Billing Configuration
Each ISP configures its own plans, pricing, tax rules, payment gateways, invoice templates, and billing cycles. One ISP might use prepaid-only billing while another uses postpaid with grace periods. Tax rates, GSTIN, and HSN codes are per-tenant. No sharing, no conflicts.
Centralized Platform Administration
The platform owner (or director entity) has a bird's-eye view across all ISP tenants. Aggregate dashboards show total subscribers, revenue, and growth across the portfolio. Platform admins can manage ISP entities, monitor health, and intervene when needed — all without breaking tenant isolation.
Scalable Architecture
NowaCRM's architecture scales horizontally. Add new ISP tenants without infrastructure changes. Each tenant's data grows independently. RADIUS tables (radacct, radpostauth) are partitioned by month for performance. Background jobs are tenant-aware, processing each ISP's billing cycle independently.
Frequently Asked Questions
How does NowaCRM isolate tenant data?
Every database model uses a TenantScopedModel base class that applies a global scope filtering by tenant_id. Data isolation is enforced at the query level — it's an architectural invariant, not optional.
Can each ISP have its own domain?
Yes. Each ISP gets a subdomain or custom domain. Tenant context is resolved automatically from the domain. Branding, logos, and company details are per-tenant.
Can each ISP have different billing rules?
Yes. Plans, pricing, tax configuration, payment gateways, invoice templates, and billing cycles are all configured independently per ISP.
How many ISPs can one NowaCRM instance handle?
NowaCRM is designed to scale horizontally. New ISP tenants are added without infrastructure changes. Each tenant's data and billing runs independently.
Related Solutions
Explore More ISP Solutions
Platform Features
Ready to Transform Your ISP Operations?
Join 200+ ISPs running on NOWA CRM. Schedule a free demo and see it in action.