Can I run CodeB for multiple clients on one install?

Yes. CodeB is multi-tenant by request domain — App_Data/ / holds each tenant's user records, SIP credentials, prompts and config. One Windows host can run dozens of tenants if the bridge box is sized for it.

Is white-labelling supported?

The product is openly CodeB — we don't ship under reseller brands. Several elements (favicon, accent colour, brand text, footer wording, navigation labels) are easy to tune per tenant, and we're open to deeper customisation conversations.

How does pricing work for resellers?

Per-install licensing, not per-seat. That makes the unit economics predictable for resellers: you know your cost up front, and the upside on customer numbers and seats goes to you, not back to the vendor.

What does support look like?

You are the first line of support for your customer. We provide second-line support to you, plus SBOM material, signed installers and architecture documentation. Channel-partner agreements are bespoke — talk to us.

For IT providers & resellers

A platform you can stand up for clients — where the margin stays with you.

For MSPs, IT consultancies and channel partners selling phone systems, meetings or identity to SMB clients. Multi-tenant by domain, runs on Windows + IIS infrastructure you already deploy, no per-seat vendor markup eating into your unit economics.

Talk channel partner All public APIs →

01 / The MSP reality

SaaS comms doesn’t fit the channel model.

Per-seat pricing erodes margin

The SaaS phone-vendor pricing model assumes you’re Microsoft. A reseller who sources at the standard tier and resells at the next tier up has 10-20% to play with, and that gets eaten by client churn and price-down pressure.

You don’t own the relationship

When the vendor’s console is the client’s daily interface, you’re the deployment company, not the platform. Renewal-time the vendor competes with you directly.

White-label is theatrical

Most SaaS “white-label” offerings keep the vendor URL in the email footer, the legal entity in the DPA and the cookie banner. The client knows. Procurement asks.

Vendor lock-in via call data

Two years of recordings and transcripts in a SaaS vendor’s storage make switching painful for the client — and for you when you want to move them.

02 / What CodeB gives you

A platform with channel-friendly economics.

Per-install licensing, not per-seat

You know your cost per client up front. Adding seats inside a client doesn’t change what you pay us — the upside on growth goes to you.

Predictable costUpside yours

Multi-tenant by domain

One bridge host can run multiple client tenants — each isolated under App_Data/<client-domain>/, with separate user records, SIP credentials, prompts, config and OIDC keys. Same software, no shared media path.

App_Data isolationPer-tenant keys

You own the relationship

You install it. You configure it. You operate it. The client renews with you because you are the platform, not because they like vendor X this quarter.

Channel-firstSticky

Open API surface

REST API + webhooks + signed transcripts. Integrate with the client’s CRM, PMS or ticketing system. No reseller-tier paywall on integration features.

REST + webhooksCRM hooks

03 / Worked example

A regional MSP with 40 SMB clients.

A managed-services provider in the 5-50 employee SMB space. They currently resell a hyperscaler-backed phone product, take 15% margin, lose three clients a year to price competition.

Stand up one CodeB bridge per client, on either a small Windows VM in the MSP’s own infrastructure or on the client’s server.
SIP trunk is whatever the client wants — the MSP picks the wholesale provider; the client doesn’t see it.
Roll out browser softphones, an AI receptionist for the front-of-house number, and OIDC SSO into the client’s Nextcloud / WordPress / GitLab. One configuration; replicate per client.
MSP charges the client a monthly managed-comms fee that covers softphone licences, hosting, support and the AI minutes. Margin is per-client-managed, not per-vendor-seat.

04 / Why not Zoom reseller / Teams CSP

Channel programs that aren’t actually channel programs.

Hyperscaler CSP margin shrinks every year

The pattern is well-documented: vendor builds a CSP/reseller programme, takes share for a couple of cycles, then squeezes margin as direct-sales gains traction. CodeB is per-install — no escalator.

Direct-vendor competition for renewal

SaaS vendors land your clients via your channel, then compete with you at renewal. CodeB doesn’t have a direct-sales motion into the SMB space — we’re a platform vendor, not your competitor.

Procurement transparency

Compliance-minded SMB buyers want to see the architecture. Self-hosting on a server they own — rather than a billing relationship with a US hyperscaler — is an easier conversation in many regions.

Add-on revenue you actually keep

AI receptionist, outbound campaigns, OIDC identity, video meetings, signed recording — all part of the same install. No add-on licence rev-share back to the vendor.

05 / Deployment patterns

Three shapes that work for the channel.

One host per client

Mini-PC on-premises at the client, or a Windows VM in your data centre. Clean security boundary, easy to back up.

Multi-tenant on your infrastructure

One bridge host, multiple client tenants. Lower per-client cost; you operate the host, not the client.

Co-managed

You install and operate; the client’s internal IT has admin access via OIDC for day-to-day tweaks. Reduces ticket volume.

Pilot, then expand

Start with two clients. Capture lessons. Roll out a repeatable per-client deployment runbook. Migrate the rest.

Want to talk channel-partner terms?

We’re building the reseller programme deliberately and bespoke per partner — we’d rather a few good partners than many transactional ones. Tell us about your SMB book and we’ll work out a sensible arrangement.

Get in touch →