Scoped against real traffic
Design decisions come from your actual profile — destinations, volumes, growth — not from a feature checklist.
Turnkey voice platform
Not our first platform. Ours.
The strongest specification we can show you is running right now, terminating our own traffic. A voice platform build from HiClass is that system's design — border control, switching, billing, monitoring, fraud defence — engineered for your operation and handed over to your team.
What it is · who it's for
Your own switch, without the false starts.
For operators, aggregators and IPRN businesses that have outgrown renting someone else's panel and want infrastructure of their own.
The build
We scope the platform around your traffic: which destinations, what concurrency, which protocols and partners. Then we build it — border controllers, switching and routing, a billing pipeline computing from per-second call detail, monitoring across every component, and the fraud controls that premium traffic makes mandatory.
What you receive is not a license and a manual. It is a deployed, documented, working system your engineers are trained into — with the option of keeping ours on call through a support plan.
Handover that sticks
Documentation, runbooks, and working sessions with your team until they operate it with confidence.
What's in the platform
The parts that matter, and why.
Each component below exists in our own production platform — the Technology page describes the operated versions in detail.
Border control & routing
Redundant SIP border controllers with a routing layer your team controls — failover policy included, not extra.
Billing from the switch
Per-second call detail written at completion feeds invoicing directly. Statements that reconcile because they were never separate.
Monitoring built in
Metrics and log pipeline across every node, with live call visibility — the view our own NOC relies on daily.
Fraud defence at the core
IRSF and false-answer detection, per-provider rate and concurrency limits, pattern analysis — in the platform, not bolted on.
How delivery works
Scope to handover, stated plainly.
1
Scoping
Engineers map your traffic profile, partners and constraints into a concrete design and plan.
2
Build & deploy
The platform is stood up on your infrastructure or hosting we provide, component by component.
3
Prove it
Test traffic, failover drills and billing verification before anything production touches it.
4
Handover
Documentation, training, and a defined support arrangement — your system, your team, our backup if you want it.
Ask us how ours is built.
The scoping conversation starts with your traffic and ends with a concrete design. Bring hard questions — the reference implementation is in production and we can describe every layer of it.