Quick answer: A white-label CPaaS model lets you sell communications — voice, messaging, AI agents — under your own brand while the underlying platform carries the carrier relationships and infrastructure. You become the provider your customers see; the platform stays invisible. On the Devotel Orbit platform this is the shipped CSPaaS capability: you create an isolated sub-account per customer, brand it on your own domain, set your own margin and spend cap, and fund it with prepaid credit drawn from your parent wallet. MSPs, agencies, and multi-brand groups run this model because it turns a communications line item into a product line, at a margin they set themselves.
What a white-label CPaaS model is
White-label (or resale) CPaaS means the company your customer pays for communications is you, not the platform behind you. The platform supplies the numbers, the routing, the channels, and the APIs; you supply the brand, the price, and the customer relationship. Every touchpoint your customer sees — the dashboard, the domain it loads on, the name on the invoice — carries your identity, and the underlying provider never appears.
Four buyer profiles operate this model:
- Multi-brand companies. One group runs several consumer brands, and each brand needs its own sender identity, its own dashboard, and its own usage view — without buying four separate platform subscriptions.
- Agencies and MSPs. You manage communications for a client portfolio. Each client gets an isolated account with your agency's branding, and you bundle the resale margin into your service or platform fee.
- Resellers and distributors. Communications is the product itself: you buy capacity at platform rates, sell at your rates, and the spread is the business.
- Product companies embedding a communications tier. Your SaaS ships voice or SMS as a feature, and each of your customers sits in their own account under your brand, with scoped API access that never crosses customers.
The common thread: more than one brand or customer, and isolation between them, with one billing relationship at the top.
The resale mechanics, mapped to shipped capability
A resale program stands on five mechanics. On Orbit each one maps to a capability on the CSPaaS pillar, reachable end-to-end from the white-label and reseller surface:
- Multi-tenant sub-accounts. Create one isolated sub-account per customer or brand from a single parent account. Each sub-account holds its own contacts, numbers, and configuration, and you can provision, suspend, or close it without a support ticket. Isolation is the foundation of resale: one customer's data never touches another's.
- Per-tenant branding and custom domains. Set each sub-account's logo and colors, and serve the dashboard on that customer's own domain. The customer logs into your brand at your address — the white in white-label.
- Reseller pricing and margins. Set a markup margin per sub-account, with an optional monthly spend cap. Your customer is billed at your rates; you settle the underlying usage with the platform; the difference is your margin. The spend cap is the partner-side control that keeps a runaway customer inside the wholesale cover you extended them.
- Prepaid credit allocation. Seed a new sub-account with an opening credit balance transferred from the parent account, so a fresh customer starts sending immediately and never outspends what you allocated. Prepaid allocation converts resale from an invoicing problem into a wallet problem — like a gift-card balance you top up per customer.
- Scoped API keys and usage rollups. Issue API keys scoped to a single sub-account, and read per-account usage rollups and statements to reconcile exactly what you resold. Scope enforces isolation at the API layer; rollups make the margin arithmetic auditable.
None of these mechanics is exotic — they are the standard shape of a resale program. What matters operationally is whether the platform ships them as first-class objects or leaves you scripting around a single-account API.
Worked example: one agency, three brands
Consider an agency that manages communications for three client brands under one Orbit parent account.
From the parent account, the agency creates three sub-accounts — one per brand. Each gets its own logo and color scheme, and each dashboard is served on that brand's domain, so the client's team logs into what reads as their own platform. The agency generates an API key for each sub-account scoped to that sub-account alone, so an integration built for brand A can never reach brand B's data.
On the money side, the agency seeds each sub-account with an opening credit balance transferred from the parent wallet, sets a markup margin and a monthly spend cap per brand, and reconciles with per-account usage rollups at month end. All three brands' costs are funded by the same parent wallet, while the margin on each is billed at the agency's own rates. One billing relationship at the top; three isolated customers underneath.
Operator bounds: where the platform ends and you begin
A resale model makes you the provider of record to your customers, and the bounds that come with that are yours to set. On Orbit the controls are tenant-owned: sub-account provisioning, branding, margins, spend caps, and key scopes are settings you configure per account — the platform provides the levers, not the mandate.
The same holds for communications rules. Consent handling, sending windows, sender registration, and program-level policy are set per tenant by the operator — in a resale model, that operator is you. The platform gives you per-tenant workspace isolation; policy is the partner's call per sub-account. Keep that division explicit in your partner onboarding documents and the model stays clean.
Frequently asked questions
Does Orbit support resellers?
Yes. The CSPaaS capability is the white-label and reseller model: sub-accounts per customer, per-tenant branding on custom domains, reseller margins with spend caps, prepaid credit allocation from a parent wallet, and scoped API keys — all first-class on the platform.
Is margin handling native on Orbit?
Yes. You set a markup margin and an optional monthly spend cap per sub-account. Your customers are billed at your rates, you settle the underlying usage with the platform, and per-account usage rollups let you reconcile the spread.
Can I bring my own domains?
Yes. Each sub-account's dashboard can be served on your customer's own domain, with per-account logo and colors, so customers interact with your brand rather than the platform's.