The full features page reads like an engineering changelog — for buyers who don’t need that depth, here’s the short version. The headline reasons, each one paragraph, the buyer’s angle first.
Runs on the Windows Server you already have. ASP.NET signaling, a tiny Windows Service for the SIP bridge, your usual IIS site bindings. No AWS, no Azure, no GCP.
No SaaS subscription. No cloud invoice that scales with headcount. Audit the source yourself.
Every participant joins from a regular HTTPS URL. Camera, mic, screen share, file transfer, recording — all happen in the user agent. Works on Chrome, Edge, Firefox, Safari, Android.
Zero rollout. New hires productive on day one. No IT ticket for the device you don’t recognise.
Media flows directly browser-to-browser over DTLS-SRTP. The server signals; it never sees the audio or video. End-to-end by the browser’s own crypto stack, not ours.
If we don’t have the bytes, we can’t hand them over, lose them, or be subpoenaed for them.
The bridge registers as a SIP extension on your PBX (FRITZ!Box, Asterisk, FreePBX, Yeastar, any RFC-compliant trunk). Inbound calls ring browser tabs. Outbound calls dial through your usual carrier.
No Zoom Phone, no Teams Phone, no second carrier contract. The trunk you already pay for is the one we use.
Point a number at CodeB, pick a real-time voice mode, paste a system prompt — the next inbound call is answered by a voice AI that speaks any language, follows the script, takes messages, transfers to staff on intent, and emails you the transcript. The model backend is pluggable per deployment, runs on your trunk, no per-minute SaaS surcharge. Sample industry: hospitality — one front desk, three personas (reception, restaurant, spa), 24 hours a day. On the outbound side the same engine dials customers on a schedule, retries on no-answer, transfers them to a human on request, and emails a per-attempt transcript — feedback calls, reminders, courtesy callbacks. More on outbound campaigns →
A front desk that never sleeps and never forgets to email the booking. Small teams stop losing after-hours calls without hiring a call centre.
The whole platform is programmable. POST a phone number + a system prompt to /api.ashx/v1/calls and CodeB dials, attaches a real-time voice AI, emails the transcript. Subscribe to call.ended, transcript.saved, outbound-ai.finished webhooks and your system reacts the instant a call completes — HMAC-signed, auto-retried, auto-paused on bad endpoints. Bearer-token auth, JSON in and out, every endpoint with a single-line curl example. The click-to-call embed and the AI receptionist sit on top of this same surface.
The CPaaS feature set integrators expect — programmable voice, lifecycle webhooks, transcripts — with none of the per-minute SaaS markup. Drop a voice-AI campaign into a CRM with two lines of curl. Full reference: api-docs.html · CPaaS positioning.
Recording composites every tile and the mixed audio into a single .webm written straight to the recorder’s machine — nothing transits a server. Every participant gets a consent prompt the moment recording starts; their answer lands in a tamper-evident JSON sidecar that travels alongside the file.
GDPR / two-party-consent jurisdictions get the paper trail. Your meeting transcript can’t be exfiltrated from a cloud account that doesn’t exist.
The product collects nothing. No third-party analytics, no error-reporting SaaS, no usage beacons. Your IIS access log is the only record of who connected, and it stays on your server.
Nothing to disclose in a privacy policy because there’s nothing to disclose.
An installable Progressive Web App that lives in the dock / taskbar. Rings on inbound calls, places outbound calls, surfaces missed-call counts. Looks like a native softphone — no .msi, no provisioning portal.
Every employee has a desk phone in five minutes. No hardware budget, no provisioning workflow.
A full OpenID Connect identity provider runs inside the install — sign in once on the landing page and your conference tile picks up an amber CodeB shield so every other participant sees you as authenticated, not just whatever display name was typed. The same SSO federates Nextcloud, WordPress, and any custom OIDC relying party against one per-tenant user database.
Spoofed display names cannot pass for known employees. Internal participants are visibly distinguishable from external guests, without making the meeting closed.