Many customers.
One control plane.
Provision and isolate as many customer tenants as you like over one API. A single agent template gives each tenant its own number and isolated call data, so you run a real multi-tenant voice product without building the control plane yourself. Flat $0.08 a minute.
HOW IT WORKS
Provision, isolate, repeat.
One template, defined once
You build a single agent template with the persona, prompt and tools. It is the shared behaviour every tenant runs, so you configure it once rather than rebuilding it per customer.
Provision a tenant
For each customer you provision a number over the API and attach it to the template. That number is the tenant boundary, and onboarding a new customer is one call, not a new deployment.
Isolated from there on
Each tenant keeps its own number, call history, settings and integrations, separated at the data layer. One tenant can never read the calls or configuration of another.
WHAT THE CONTROL PLANE GIVES YOU
The multi-tenant plumbing, already built.
Provision over the API
Add a customer with one request. No new deployment, no per-tenant infrastructure to stand up.
Isolated per tenant
Own number, own call data, own settings. One tenant never sees the data of another.
Isolation at the data layer
Tenant boundaries are enforced in the database, not left to application-layer filtering.
One template, many numbers
A single template sits behind hundreds of numbers, so shared behaviour scales without copies.
One key runs it all
Provision, configure and read call data for every tenant from one API key over plain REST.
Scales to hundreds
The same model that runs three tenants runs three hundred, without a rebuild at each step.
ISOLATION THAT SURVIVES A SECURITY REVIEW
Separation at the data layer, not just the app.
The weak version of multi-tenancy is one shared account with prefixes standing in for isolation. It fails the first questionnaire an enterprise customer sends. Nixflex separates tenants at the data layer, so each tenant boundary holds even under queries an agent generates on the fly. When a customer asks where their data lives and who else can reach it, the answer is already clean.
QUESTIONS
Multi-tenancy, answered.
What does multi-tenant mean for a voice product?+
It means one system serves many customers, each kept separate. In Nixflex each customer is a tenant with its own number, its own call data and its own settings, all running on one shared agent template. You get the efficiency of one platform with the separation each customer expects.
How is one tenant isolated from another?+
Each tenant is bounded by its own number, and its data is separated at the database layer rather than only in application code. That distinction matters: an agent generating queries cannot accidentally reach across tenants when the boundary is enforced in the data layer, which is what a serious security review looks for.
Do I build a control plane myself?+
No, and that is the point. Provisioning, isolation and per-tenant configuration are handled for you over the API. You add a customer with one request instead of building the multi-tenant plumbing that would otherwise take months before you shipped anything.
How do I onboard a new tenant?+
You provision a number for the customer over the API and attach it to your template. That is the whole onboarding step. Because the template already defines behaviour, the new tenant is live immediately with its own isolated boundary.
Can each tenant have different settings?+
Yes. The template holds shared behaviour, and per-number settings let each tenant have its own script, voice, integrations and webhook. Shared where it helps, separate where it matters.
How many tenants can one template serve?+
Hundreds. The same one-template model that runs a handful of tenants runs hundreds without a rebuild at each step, which is how a single agent can sit behind hundreds of live numbers at once.
Is there an SDK for managing tenants?+
No separate SDK is needed. Every tenant is provisioned and managed over the same plain REST API, which you call from any language. Typed client libraries are on the roadmap; the REST surface is what you use today.
Run many tenants on one plane today.
One template, a number per customer, isolated data. Provision your first tenant in minutes.