The house
A voice infrastructure company with one organising idea: build in layers, and put a boundary around each.
- Every layer has an edge — Stated at design, not discovered during an incident.
- Protection at the boundary — The right control in the right place, rather than everything everywhere.
- Evidence as a by-product — Every control produces an artefact, not only a behaviour.
- Limits published — Every layer stated with what it does not cover.
What we build
Four layers: connectivity into a phone system you already own or into ours, control when the existing system has reached its end, numbering, and the operation of all of it.
We run the platform rather than reselling access to somebody else's. That matters on the day a fault needs investigating rather than escalating to a company with whom you have no relationship.
How we work
Measure, specify, prove, fit, hold. Nothing is provisioned before the specification is agreed, nothing is fitted without a rollback position established first, and nothing is assumed to work because it worked last time.
Every layer carries a stated failure boundary. When something goes wrong, the question of what is affected has an answer that was written down before the incident rather than reconstructed during it.
What we publish
No business figures at all: no uptime target, no customer count, no names. A number about ourselves asks to be believed. A layer boundary can be argued with, which is why the site is built out of those instead.
We name no customers, publish no testimonials, and assert no certification, accreditation, regulatory approval or carrier authorisation. Where a specific status bears on procurement, ask and the answer will be precise and in writing, including where it is no.
We do publish the limits of the design itself. A single-circuit site is bounded by that circuit regardless of how carefully everything above it is separated, and the design says so rather than letting the architecture imply otherwise.
Who we suit
Organisations that want to know what happens when something breaks, rather than to be told that it will not. That requirement usually accompanies either scale or a low tolerance for a failed call.
We suit poorly anyone whose only criterion is the lowest per-minute rate. There will always be someone cheaper, and buying on that basis is legitimate and not what this is built for.
What that produces
Connectivity
The outermost layer. Whether a call can happen at all.
Open Layer twoControl
Where a call goes, and what happens when nobody answers.
Open Layer threeNumbering
What a caller dials, and whether it can ever be unreachable.
Open Layer fourOperation
Change, treated as a layer because it causes more incidents than failure does.
Open