Business Context

LotusFlare sells DNO Cloud - a SaaS BSS for telcos. The Portal is the console where an operator's staff, and LotusFlare's own people, actually run it.

The product

DNO Cloud is the commerce and monetization stack: product catalog, subscribers, orders, billing, charging, campaigns, and ~115 services in total. The Portal is the single point of entry into all of it - one web console, deployed per operator, module-gated per tenant. Every operator buys the whole stack and gets it isolated in their own DC.

The two audiences

External: operator staff

Care agents, catalog and marketing managers, and ops engineers at the operator. They run their business in the Portal daily. Subscribers - the operator's own customers - never touch it.

Internal: LotusFlare staff

Solution Architects (SAs) configure and support operator deployments through the Portal itself: tenant setup, OAuth/SSO integration, operator configuration, Power User Mode. Default read access to all operators except T-Mobile.
Delivery PM - read-write, only for the operators they support. PMO - read-only, same scoping.
Support (HDS) - triage access for production incidents.

The operator fleet

DC/operator mapping below comes from the internal knowledge base (2026-09-16). Verify before acting on it - sources can lag reality.

Region	Operators	DCs
APAC	Globe, GOMO, Tapp, Ooredoo	dc16, dc20, dc23, dc95, dc96
EU	Deutsche Telekom, A1 Slovenia	dc33, dc71, dc72
US / AMER	T-Mobile + MVNEs (Roccstar, Smartless), Pilot Fiber, Digicel Panama, Avantel	dc11, dc21, dc84, dc90
Staging	lotusflaretelecom, dtmace, Intrepid, Tillman, Charter, Mojo...	dc02, dc22, dc25, dc26, dc30 + labs

MVNE/MVNO customers (virtual operators) share the same product at different scale - dc84 hosts several on one cluster.

Teams around the Portal

platform-portal - owns the shared Portal platform: the BFF, permission machinery, build and deploy plumbing, and the portal-team alerts.
DATAP (Data Platform - my team) - owns the Dataflows, DataHub, and Reports feature areas inside the Portal. Work arrives from the users of those pages and from the team lead; our upstream services (dataflow-manager, report daemons) live in lfscala with the platform backend team.
Upstream owners - billing, charging, party management and other teams own the services the BFF proxies to; the service name on a proxy route points at its owner.

Adjacent but out of scope for this documentation: DT's T-Portal (MACE team) and TMO DevEdge - portal-flavored products owned by other teams.

How a module reaches an operator

Commercially and technically the same lever: a View is enabled for the operator's tenant, which makes the module's permissions assignable to their roles. Feature rollout inside a module can additionally be flagged per operator via the operator row's featureFlags configuration - a database edit in the Tenant Editor, not a deploy.

Open full screen ↗

Next: Technologies - the concrete stack and its conventions.