Tel-Agent: Is This Open-Source AI Phone Assistant Really Self-Hosted?
By Matt Cullerton, founder of Mavric and Apso
Tel-Agent is an AGPL-3.0 gateway from Vienna's Dpro GmbH that sits between a phone line and an AI agent, routing calls and messages to a model you choose. A TikTok from @github.signals presents it as an AI phone assistant that "runs entirely on your own hardware." The repository is real, but its default setup sends call audio to LiveKit Cloud, Deepgram, OpenAI and ElevenLabs, the phone feature is milestone 11 of 12 on its roadmap, and its own docs say the "Product of the day" badge belongs to a different product.
What is Tel-Agent?
The README says: "Tel-Agent is an open-source gateway that sits between a phone line and an AI agent. A call arrives over SIP. Tel-Agent checks the caller against your routing rules and either passes it through to a human, blocks it, or hands it to an AI agent." Its tagline is "Connect any phone line to any AI model. Self-hosted, bring your own keys."
It also lists what it is not: a PBX replacement, a workflow automation platform, a CRM or anything that works with analog lines.
The repository was created on 2026-08-16. When checked on 2026-09-15 it had 516 stars, 115 forks and 210 commits, with releases v0.1.0 and v0.1.1 both on 2026-09-05. The stack is LiveKit Agents, FastAPI, Next.js, SQLite or Postgres, Redis and Caddy. Of the 210 commits, 148 come from one account that commits as Mohamed Alarade, Dpro's managing director. The README carries a "Built with Antigravity and Codex" badge.
Does Tel-Agent run entirely on your own hardware?
Not in its default configuration. The .env.example sets TELEPHONY_MODE=livekit, described as "A number bought from a SIP provider, pointed at a LiveKit Cloud SIP trunk." An on-premises mode, TELEPHONY_MODE=sip, registers directly to a 3CX, Asterisk or FreePBX extension, but it is not the default.
The speech pipeline is hosted too. The defaults point to api.deepgram.com for speech-to-text, api.openai.com for the model and api.elevenlabs.io for the voice. The README says: "Providers for v1: Deepgram (STT) · one cloud LLM · ElevenLabs (TTS). Local models (Ollama, Whisper, Piper) follow in v1.1."
The project's own blog post on GDPR concedes this: "The design that gets the first call answered uses hosted speech-to-text, a hosted model and a hosted voice." Recordings and transcripts are stored on your machine. The caller's audio still leaves it.
Are the security defaults good?
Yes, and the video skips them. The server binds to 127.0.0.1 by default, a password is required on first run with no default credentials, and API keys are encrypted at rest. Recording announcements are on by default (RECORDING_ANNOUNCEMENT=true).
The README justifies that last default with "Austria requires both parties to be aware that a call is recorded." Austria's StGB § 120 penalises unauthorised recording of non-public statements with up to one year in prison, and practitioner guidance reads it as requiring consent, which is stricter than awareness.
Did Tel-Agent win Product of the Day?
No. The "Product of the day / 1st" seal on the README is a local SVG file. The repository's awards README says it is "The wreath lockup from the Flowxtra registration page" and that "'Product of the day - 1st' is Flowxtra's, earned by a shipped product. Tel-Agent is pre-alpha, has no release, and has not placed anywhere." Flowxtra is a separate Dpro recruitment product. I found no Product Hunt listing for Tel-Agent.
The "DSGVO & GDPR COMPLIANT" and "AI ACT COMPLIANT" badges are also reused Flowxtra artwork. The compliance README says that "GDPR and the AI Act are, for a self-hosted product, properties of a deployment rather than of a repository."
Under EU AI Act Article 50, applicable from 2 August 2026, people must be told when they are talking to an AI system unless it is obvious. That duty falls on whoever deploys the phone agent.
Can Tel-Agent answer phone calls yet?
Not as a finished feature. The roadmap has twelve milestones and the rule "Step N+1 does not start before step N works." The project is at milestone 3, messaging channels.
Phone calls are milestone 11. The transport code exists, with streaming speech, interruption handling, caller-ID routing and stored transcripts. The roadmap says what is missing: "the latency budget, endpointing and barge-in on a live line." None of its six acceptance checks are ticked. The target is under 800 ms from the end of caller speech to first audio, tested on at least 20 real calls in Austrian German. It warns, "Text-channel comfort is not evidence."
How many channels does Tel-Agent support?
The README says the "official channel scope now covers 24 channels including the phone." The wired channels are web chat, WhatsApp, Telegram, Messenger, Instagram, Discord, Slack, email and SMS. Microsoft Teams, Signal and Viber were merged on 2026-09-14. Seven channels, including iMessage and Google Chat, were still open issues on 2026-09-15. The 24 is a plan.
Is Tel-Agent free for commercial use?
It is AGPL-3.0. The README says, "If you run a modified version of Tel-Agent as a network service, you must publish your modifications." Dpro sells a commercial license for closed-source integration.
Every contributor signs a CLA giving Dpro GmbH an "irrevocable" license that "includes the right to relicense Your Contribution, including under proprietary or commercial license terms," so it can offer "a hosted edition and a commercial license." This is a common dual-license model, and one company holds the commercial rights to all contributions.
Bottom line
Tel-Agent is a real, fast-moving AGPL project with good security defaults and working text channels. Its default setup sends call audio to hosted providers, its phone feature has not passed its own tests, and its award and compliance badges are borrowed from another Dpro product, as its own docs admit.
Sources
- Dpro-at/Tel-Agent on GitHub - the repository
- Tel-Agent README - features, providers and security notes
- Tel-Agent .env.example - default telephony and provider settings
- Award seal documentation - origin of the Product of the day badge
- Compliance badge documentation - origin of the GDPR and AI Act badges
- ROADMAP.md - milestones and phone call criteria
- CLA.md - contributor licence terms
- The GDPR case for a self-hosted AI phone assistant - the project's own blog post
- tel-agent.com - project site
- Dpro GmbH - the company and its products
- livekit/agents - the voice agent framework Tel-Agent builds on
- EU AI Act Article 50 - AI disclosure obligation
- Austrian StGB § 120 on RIS - the recording statute
- Open Source AI Phone Assistant on DEV - the maintainer's writeup
Published September 14, 2026. Based on a TikTok by @github.signals. Full video notes (markdown)