---
title: "Can a VoIP platform support multiple customer configurations?"
topic: "White-Label / Wholesale"
updated: 2026-05-06
canonical: https://acrobits.net/resources/knowledge-base/multi-tenant-voip-platform/
summary: "Cloud Softphone supports multi-tenant architectures through per-domain provisioning. Each SIP domain maps to isolated branding, feature flags, codec settings, and usage tracking."
---

# Can a VoIP platform support multiple customer configurations?

> Cloud Softphone supports multi-tenant architectures through per-domain provisioning. Each SIP domain maps to isolated branding, feature flags, codec settings, and usage tracking.

Cloud Softphone supports multi-tenant deployments through per-domain provisioning: each SIP domain gets isolated branding, feature flags, codec settings, and usage tracking, all from a single platform deployment, with no custom development required.

## What Multi-Tenant Means for a Softphone Platform

**Multi-tenant [provisioning](/voip-glossary/provisioning/)** means a single Cloud Softphone deployment serves multiple operator customers or business segments, each with isolated configuration, branding, and usage tracking.

This is different from simply having multiple SIP accounts in one app. True multi-tenancy means:

  - **Each tenant has its own configuration profile**: codec preferences, feature toggles, UI settings, and call behavior rules

  - **Branding is per-tenant**: logos, color schemes, splash screens, and app store metadata can differ

  - **Provisioning is isolated**: one tenant's subscribers cannot see or affect another tenant's configuration

  - **Usage data is segmented**: call volumes, active users, and feature adoption are trackable per tenant

## Per-Domain Configuration in Cloud Softphone

Cloud Softphone supports multi-tenant architectures through **per-domain provisioning**. Each SIP domain maps to a distinct configuration set:

**Separate branding per domain.** An MVNO reselling your VoIP service gets their own branded experience. Your direct enterprise customers get yours. Both run on the same Cloud Softphone deployment.

**Feature control per domain.** Enable call recording for one tenant, disable it for another. Offer video as a premium tier for enterprise tenants while keeping it off for residential. Feature flags are granular and domain-scoped.

**Codec and quality settings per domain.** Tenants on high-bandwidth enterprise networks get wideband audio by default. Tenants serving mobile-heavy markets get bandwidth-optimized codec stacks. No compromise either way.

## Usage Tracking and Analytics Per Tenant

Operators managing multiple tenants need per-tenant visibility. Cloud Softphone's admin portal provides:

  - **Active user counts** per domain: know exactly which tenants are growing and which are stagnant

  - **Call volume metrics**: track minutes, call completions, and failure rates per tenant

  - **Feature adoption**: see which tenants use push, video, messaging, and other capabilities

  - **Push delivery rates**: per-tenant push reliability metrics via [SIPIS](/voip-glossary/sipis/), Acrobits' push infrastructure (operational since 2009), help you troubleshoot domain-specific issues

This data feeds into your billing and business intelligence systems. If you charge tenants per active user or per minute, the tracking is already built in.

## Scaling to Hundreds of Tenants

Cloud Softphone's provisioning architecture handles hundreds of distinct tenant configurations without performance degradation. The provisioning endpoint resolves the correct configuration based on the subscriber's SIP domain at activation time. Adding a new tenant is a configuration task, not an infrastructure deployment.

For operators running wholesale or reseller models, this means onboarding a new business customer takes hours, not weeks. See the [provisioning guide](/resources/knowledge-base/provision-softphone-hundreds-users/) for details on scaling to hundreds of users.

## Getting Started With Multi-Tenant Provisioning

Multi-tenant provisioning is available on Cloud Softphone's standard platform. No custom development required. The Acrobits team handles implementation end to end: typical launch is **2–4 weeks**.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Can a VoIP platform support multiple customer configurations?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Cloud Softphone supports multi-tenant architectures through per-domain provisioning. Each SIP domain maps to isolated branding, feature flags, codec settings, and usage tracking."
      }
    }
  ]
}