Company
We build for the places where the connection is not a given.
Business telephony has made enormous progress in ten years, and it paid for that progress with one regression: it stopped working without the internet. We think that regression is avoidable, and that fixing it means giving nothing up.
Why this product exists.
A telephone system sitting in a comms cupboard has an obvious flaw: it ages, nobody updates it, and it offers nothing to the people who use it. It also has a quality its generation had come to find unremarkable: it keeps the handsets ringing when the outside world stops.
Cloud platforms brought the app, easy administration and continuous updates. They took that quality away. For a head office with two fibre links, the trade is reasonable. For a clinic, a factory, a town hall, a site in Abidjan or a rural branch, it is not.
Konvoice refuses that trade. Administration and intelligence live in the cloud, because they are better there. Calls live as close to the handsets as possible, because they are safer there.
What we refuse to do
- Promise continuity that physics forbids. A locked mobile will not ring without the internet, and we write that on our product pages.
- Lock our customers in. Free outbound porting, exports in open formats, the right to leave written into the contract.
- Put AI in the call path. No transcription, no model and no third-party supplier can delay a ringtone.
- Display certifications we do not hold. What we have is published; what is under way is described as under way.
- Hide a price behind a form. Our prices are on the site, including the cost of the Edge appliance.
For a head office with two fibre links, the trade was reasonable. For everybody else, it was not.
That is the sentence that brought this product into being
Engineering principles
Four rules that decide our trade-offs.
They are written into our internal documentation and are used to settle arguments when a deadline is pushing the other way.
The cloud is never critical
No call function may depend on a remote service. If a new feature requires it, the feature is designed differently or it does not exist.
Security is not bypassed to go faster
No shortcuts on encryption, on isolation between companies or on authentication, whatever the schedule says.
The limits are published
What the product cannot do is written on the same pages as what it can. A nasty surprise costs more than a lost contract.
Nothing is irreversible
Every update, every migration and every switchover has a way back, tested before it is offered.
Where the product is used
The places that taught us what breaks.
Not one of these sites has two fibre links and an air-conditioned room. They wrote the specification — not a product committee.
What we measure
The numbers we use to tell whether we are doing our job.
These are not sales arguments: they are the indicators we watch internally, and the ones we publish.
We recruit rarely, and we say so when we do.
Real-time engineering, telephony, embedded systems, security. If you have ever debugged an RTP stream at three in the morning and enjoyed it, write to us even with no vacancy open.
See Konvoice on your own numbers.
Thirty minutes, your call plan, your network constraints. We cut the link live and show you what keeps running.
No commitment. No card number asked for.