Connect · available now · source on GitHub
Connect is not one app — it's a technology-agnostic core with nine provider integrations, voice AI agents, and Customer Memory. Pick your transport, mix backends in one database, and keep every conversation on the record.
The core
The architecture lesson from years of telephony products: keep the data model in Odoo, make transport a plug-in.
Calls, messages, recordings, users, numbers, and call flows live in a technology-agnostic core. Providers plug in underneath; your data and workflows stay put.
Each integration extends the core through Odoo inheritance. The core never imports provider code — swapping or mixing backends is configuration, not surgery.
Whisper transcription and LLM summaries work on any recording, no matter which backend produced it.
The messaging UI lives in the core with an abstract send method; each provider implements delivery. Same workflow, any carrier.
Integrations · 9 backends
Every integration is a module you install alongside the core. Each block shows what it ships today — named capabilities, a capability readout across the seven platform features, and the honest scope of the current version. The full catalog — business bridges, voice AI, and Customer Memory included — is on the modules page.
connect_twilio Full cloud telephony, browser calling, and messaging controlled from Odoo.
Module scope The reference telephony transport for ElevenLabs voice AI agents.
connect_telnyx Calls, WebRTC, and omnichannel messaging on TeXML, including native AI assistants.
Module scope Attended transfer and advanced RCS cards are not in the current version.
connect_freeswitch An Odoo-managed telephony platform with its own dialplan, queues, call parking, and firewall.
Module scope Built for self-hosted infrastructure and full control over telephony.
connect_asterisk Connects FreePBX, Issabel, or standard Asterisk to the shared Odoo ledger through an AMI sidecar.
Module scope Numbering and dialplan stay in the customer's PBX. SMS is not supported.
connect_3cx Connects 3CX V20 to Odoo contacts and the call ledger through a server-side CRM template.
Module scope The advanced agent tier requires live validation on a real 3CX instance.
connect_infobip Event-driven Calls API, WebRTC phone, SMS, and WhatsApp in one Odoo ledger.
Module scope IVR, RCS, Viber, and transfer are not in the current version.
connect_bird SMS and WhatsApp through Bird.com, plus a call ledger and callback click-to-call.
Module scope There is no public WebRTC SDK; parts of the voice API require live validation.
connect_vonage NCCO telephony, browser calling, IVR, recordings, and SMS through the Messages API.
Module scope The Browser Client SDK is marked in the spec as requiring live validation.
connect_livekit A realtime stack for video rooms, SIP telephony, browser calling, and voice AI agents.
Module scope No SIP registrar for desk phones or internal user-to-user calls.
Voice AI agents
External frameworks and provider-native assistants both land their outcome in the same shared journal.
External agent
via Twilio · Telnyx
Conversational voice agents in 27 languages: appointments, tickets, and orders against your catalog.
External agent
via FreeSWITCH
Open agent framework bridged into the self-hosted FreeSWITCH backend.
Built in the open
Connect is developed the way Oduist works: AI agents build, humans decide, and every architectural choice is a numbered decision record in the repository — from why caller IDs normalize to E.164 before partner matching, to why endpoint passwords generate as readable passphrases.
The code is public so your own AI agents can read, extend, and customize it; the gated test suite that verifies customizations ships alongside. Open code, with a safety net as the product.
Clone the source, add it to your addons path, and install the modules you need. Every feature works for 30 days; buy inside the module when you are convinced. The license binds to your instance.
git clone https://github.com/oduist/connect_addons_ng.git
Connect is the next generation of both: one modular platform that carries the Twilio experience of the original Connect and the self-hosted PBX experience of Asterisk Plus, plus a FreeSWITCH backend and Customer Memory. The earlier standalone modules are folded into it.
Yes — providers are modules over one core, so cloud telephony, a self-hosted PBX, and a messaging-only channel can share the same data model, users, and workflows in a single database.
Start from what you already run and what you need: the capability readout on each block shows exactly what ships in that module today, including the honest gaps.
The source is public at github.com/oduist/connect_addons_ng, every architectural decision is recorded in the specs/decisions folder, and releases land in the changelog first.