Saltar al contenido
NUEVONOS 1.2 · Aurora ya disponible — NOC conversacional en 24 idiomasNUEVOCore X100 flagship — instalador en clúster para más de 500.000 abonadosNUEVOApp Field Engineer — órdenes de trabajo, GIS y pruebas in situNUEVONetxol One Suite — NMM · CRM · ERP bajo una sola identidadNUEVOHistoria de despliegue · 82.000 abonados en un solo Core X20
Netxol
NOS General

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

1
CCarlos Méndezpreguntó · 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 respuestas·547 vistas
1
NNabil Zaidirespondió · 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é Silvarespondió · 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.
Inicia sesión para responder. ¿Nuevo por aquí? Crear una cuenta o iniciar sesión.