Your mailbox from the phone, and recordings you can get through
Mailbox options behind 0, a recordings page built for listening, softphones that work from home, a fax tab in the app, and a fresh look.
What we built, and when.
Status updates from the people building Kahevo, from its first days as a small project called Pidgin Talk to this week. The wins, and the faceplants too.
Updates from 2026
-
-
Fax, texts and voicemail in writing are in production
Fax, text messages on your business numbers, and voicemail and recorded calls written out are now in production.
-
Voicemail in writing, and a backup for calls out
Voicemail and recorded calls written out for you, a second provider when the first fails, and easier transfers.
-
Coming next: AI that does the listening
Planned, not built: voicemail and recorded calls written out for you to read and search.
-
Voicemail you get through, and charts of your busy hours
A voicemail inbox that plays your new messages in order, and dashboard charts of when your calls come. In testing.
-
A sound studio for your hold music
Hear your hold music the way callers will, on a phone line or in HD, and build playlists by dragging. In testing.
-
Nodes: restarts, cut cables and nobody left hanging
A call kept going through a network cut and back. Restarts move calls first, and browser and app calls now reconnect too.
-
Nodes: the node fails, the call carries on
High availability is built and in testing: a failed node is taken over in seconds, and the calls on it carry on.
-
Kahevo runs on Linux
For stability, Kahevo runs on Linux: the platform phone systems have trusted for decades to run for years without a reboot.
-
Nodes: queues across nodes
A caller waiting in a queue is now answered by an agent on any node. Signing in and out of queues holds everywhere.
-
Kahevo Legacy is retired
Every Kahevo now runs the Kahevo Rust Engine, on servers and branch boxes alike, with nothing to switch.
-
Nodes: calls cross between nodes
A phone on one node now rings a colleague on another. Transfers, ring groups, paging, park and listening in work across nodes.
-
Nodes: one phone system, whichever node
Two or three servers that behave as one: one view, one set of limits, and security that holds everywhere.
-
Nodes: the foundations are in
High availability for customers who cannot let the phones go quiet. The groundwork is built and in testing.
-
Standby nodes: the plan for failover
What happens when the server goes dark? Our plan for a second node that takes the calls. Planned, not built.
-
Your day, on one screen
The dashboard is now everyone's: missed calls to return, new voicemail and messages waiting, the moment you sign in.
-
Locking the doors a stranger tries
We went over Kahevo the way an attacker would. What we found, what we closed, and what it means for your calls.
-
A dashboard that is yours
Drag, resize and hide panels, and pick from sets made for a call center, a hotel front desk and a shop. In testing.
-
Whose number is it?
On a shared server, trunks are assigned and numbers are handed out, never typed. Plus one list of every account.
-
Many businesses, one server
Multi-tenant is built and in testing: each business walled off by the database, with limits, usage for billing and an archive.
-
Departments, pickup and paging
Decide who sees and reaches whom inside one business, answer a colleague's ringing phone, and page your own department.
-
Texting, the team way
Text messages with customers on numbers a whole team shares, and messages between colleagues. Built and in testing.
-
How big a box does a branch need?
Our estimates for a branch-office box on a small four-core mini PC: calls at once, memory and the line it needs.
-
The whole call, inside the engine
The Kahevo Rust Engine now carries browser and app calls too, joins calls inside itself, and is chosen with one switch.
-
Listen, whisper, barge
A manager who is allowed to can join a colleague's call: to listen, to coach quietly, or to speak to everyone.
-
Roles: not everyone needs every key
Five ready-made roles and your own on top: each part of Kahevo can be looked at, changed, or kept out of reach.
-
The Rust engine is live
Kahevo's own call engine, written in Rust, is now in production: it sets calls up and carries their audio.
-
This website
Kahevo has a home on the web, with a roadmap, a place for MSPs to register, and these updates.
-
A ringing tone that got too loud
A flaw in how steady tones survive a lost packet, found while measuring the engine, and fixed.
-
The engine's first numbers
In our 500-call test the Rust engine used less than half the processor, with nothing lost.
-
Why we are rewriting the engine in Rust
The part of Kahevo that carries every call's audio is being rebuilt as our own engine.
-
Your logo on the phones
Upload one picture and every color desk phone shows it, sized to fit each screen.
-
A phone book on every desk phone
Desk phones now show colleagues and shared contacts in their own directory.
-
It tells you when something is wrong
Email alerts when the call service, a provider, a desk phone, the disk or a backup needs attention.
-
Kahevo sends email
Voicemail, missed calls and faxes can now arrive in your inbox.
-
Queue reports
Who called, who waited, who gave up, and who answered: on a page, as a file, or by email on a schedule.
-
Call queues
Callers wait in line with music, hear their place, and can ask to be called back.
-
How did that call sound?
Kahevo measures loss, jitter and delay on every call and flags the bad ones.
-
Pick your provider from a list
A catalog of SIP providers fills in the connection details, and you can add your own.
-
A built-in session border controller
The part of Kahevo that faces the internet for you, without a separate box to buy.
-
Hākuʻi goes into service
Kahevo Hākuʻi is now in production, with encrypted phones and setup by link at the branch.
Want the next update to be about you?
Tell us what you need a phone system to do. What our customers and partners ask for is what gets built next.