Sovereign comms for a workforce that isn’t in the office.
When agents, support staff and back-office teams work from anywhere, the comms platform becomes the perimeter. CodeB gives a remote workforce one phone identity, signed call recording for audit, and an on-prem control plane that no third-party SaaS sees.
The perimeter moved. Most phone systems didn’t.
Call media leaves the company
Hosted voice products route every call through their cloud. For a remote agent that means audio, transcripts and recordings traverse a third party before they reach the customer’s storage — a compliance gap that wasn’t a gap when everyone was on the office PBX.
Identity fragments by location
One worker has a desk-phone extension, a softphone, a personal mobile they answer for company calls, and a separate meeting account. None of them carry the same identity. Joiners and leavers are provisioned in four places.
Recording obligation gets harder
MiFID II requires regulated calls to be recorded. DORA expects operational-resilience evidence. HIPAA-adjacent workflows want signed audit trails. When the worker is at home, who is responsible for the recording chain of custody?
Per-desk hardware doesn’t scale
Buying every remote worker a Yealink and shipping it to their home is a procurement problem. Most companies fall back to a SaaS softphone — trading the procurement problem for the data-residency problem above.
One platform, one identity, one storage boundary.
Browser phone, anywhere
The phone is the browser. Installs as a PWA on the worker’s laptop, tablet, or personal mobile. Same SIP registration, same DID, regardless of where they log in. No per-handset purchase, no per-extension licence.
Signed call recording & transcripts
Every call recorded to per-tenant storage with a verifiable signature. Transcripts emailed to the right inbox. Same audit trail whether the agent is in the office, working from home, or travelling.
One OIDC identity, joiners & leavers central
One sign-in per worker via password, passkey (FIDO2 / WebAuthn) or EU Wallet. Unlocks phone, meetings, recordings, admin pages. Provision once, deprovision once — no per-handset onboarding trip.
Video meetings on the same install
Daily standup, customer call, training session. Same Windows + IIS server. No Zoom subscription, no SaaS media path. Same identity in the meeting as on the phone.
A 60-seat customer support team across Europe.
60 agents in 12 countries, plus a regulated back-office that needs MiFID-style recording on a subset of calls. Current setup: Zoom Phone for the team, Microsoft Teams for meetings, an unattested mobile app for the regulated subset, and an out-of-band recording vendor.
- One CodeB tenant. Each agent gets a DID and an OIDC identity. Sign in once per shift — on the home laptop or a hotel-room iPad.
- Regulated subset: dial out via a tagged route — signed recording fires automatically, written to the customer’s storage with a verifiable signature.
- Cross-team daily standup: same browser, same identity, no extra Zoom or Teams licence.
- Joiner Monday morning: HR provisions the OIDC user — phone, meetings, recordings, admin pages all unlock at once. Leaver Friday afternoon: same workflow, reversed.
Four vendors collapse into one. Call audio never leaves the customer’s control plane. The audit trail is the same whether the agent is in Frankfurt, Lisbon or working from a campsite in Wales.
Two products solve different problems.
Sovereignty is the whole point
Cloud voice products route every call through their cloud. CodeB doesn’t — meeting and SIP-call media stay on the customer’s IIS. For a remote workforce that turns "where does our call audio live?" into a one-line answer.
Recording without a separate vendor
Most cloud-voice products add recording as an upsell, often via a third-party integration. CodeB ships signed call recording per-tenant on the same install. Regulated subset and unregulated calls share the same chain of custody.
Identity is OIDC, not a vendor account
The phone, meetings and admin pages all consume the same OIDC identity. A SaaS voice product gives you a vendor account; CodeB gives you a standards-compliant identity you can layer Passkeys or EU Wallet on top of.
No per-seat carrier change
CodeB sits on the SIP trunks the company already pays for. No carrier porting, no rate-sheet change, no notice-period negotiation. The remote workforce gets the new phone on Monday; the carrier doesn’t know it happened.
The regulations didn’t soften when staff went home.
NIS2
Remote workers widen the attack surface. CodeB’s on-prem control plane keeps comms inside the entity’s NIS2 scope — not a third-party SaaS.
DORA
Financial entities need verifiable evidence of operational resilience. Signed recordings + on-prem CDRs give an auditor a single chain of custody.
MiFID II
Regulated investment-firm calls must be recorded. CodeB’s signed-recording works the same way for a home-working trader as for an office trader.
GDPR
Data residency is a clear answer when call media stays on the customer’s storage. No data-processing agreement with a third-party voice cloud is required.
One server, many remote workers.
On a Windows server
Existing back-office Windows + IIS box is enough. No extra infrastructure required; the platform installs on top of IIS.
In a private cloud
If on-prem isn’t a fit, run the same software on a VM in the customer’s preferred EU region. Storage stays in the tenant.
Hosted tenant
For teams that don’t want to operate it themselves, Aloaha runs a private hosted tenant on the customer’s domain.
One sprint
Typical onboarding: identity wired Monday, browser phones to staff Wednesday, signed-recording on regulated routes by Friday.
Want a 30-minute walk-through?
Show us how your remote team is wired today — carrier, recording vendor, identity, meeting tool. We’ll tell you which pieces of CodeB collapse the stack, in what order — and which aren’t worth the change.
Get in touch →Related: For whom is CodeB? Identity (OIDC + passkeys) EU Wallet sign-in AI-call privacy vs. Zoom / Teams CRA / NIS2 / DORA Buy / host