Skip to content
New releaseNOS 1.2 · Aurora is now shipping — conversational NOC in 24 languages.HardwareCluster-aware installer for Core X100 available today.AppsField Engineer & Subscriber apps re-published to iOS and Android stores.AI EnginePer-tenant AI budget controls now live for multi-tenant operators.PerformanceRADIUS backend picks up a 30% throughput lift over 1.1 LTS.
NetXol
NOS General

Multi-tenant setup: separating MVNO and retail on one Core

1
CCarlos Méndezasked · Jul 11, 2026, 09:15 AM
We host a small MVNO on our infrastructure. Today they run on a parallel toolchain. We'd like to fold them into our X20 as a separate NOS tenant so we can retire the second stack. Two questions: (1) is data-plane isolation enough that we could sell the tenant slot to more partners? (2) does the AI Engine budget partition per-tenant or is it shared? Docs mention Aurora added per-tenant AI budgets but I want confirmation before we quote.
#multi-tenant#mvno#isolation#aurora
2 replies·546 views
1
NNabil Zaidireplied · Jul 12, 2026, 10:47 AM
Yes on both. Data-plane isolation is genuinely airtight — I've run pen tests specifically to cross the tenant boundary and never got through. And per-tenant AI budgets in Aurora are hard limits, not soft — one tenant can't burn another's budget. Selling more tenant slots to partners is a legitimate business model on the same X20/X100 hardware.
0
AAndré Silvareplied · Jul 15, 2026, 12:52 PM
We host two wholesale partners as tenants on our X20 and it's transformed the economics. The moment I'd caution about is billing — you'll want to configure separate ledgers for each tenant, otherwise your GL becomes a headache.
Sign in to reply. New here? Create an account or sign in.