Owner-operator
Controls signalling, media, billing and monitoring. Can change, explain and prove what happens on the platform.
The distinction that matters
Two business models sell the same words.
Every provider's website says quality, coverage and support. The words cannot tell you which kind of company you are dealing with — but the model behind them decides everything about your experience when something needs to change or goes wrong.
The two models
What a reseller can't do, however good.
This is a description of structures, not of any company. Good resellers exist; the model still sets their ceiling.
Structure decides service
A reseller stands between you and the platform. Whatever they promise, delivery depends on a system they neither built nor control: allocation waits on an upstream inventory, routing changes wait in someone else's queue, and when traffic misbehaves, their support asks the same helpdesk you would — one step further from the switch.
An owner-operator answers from the platform itself. Allocation comes from inventory it holds; a routing change is applied, not requested; a dispute is settled by reading the signalling, because the signalling is theirs to read. Neither model is dishonest — but only one can show you the machine.
Reseller
Controls a panel and a relationship. Speed and truth both arrive second-hand, at the pace of the platform behind them.
Questions that settle it
Ask any provider — including us.
These questions cost nothing and cannot be answered convincingly from a panel. Our answers are on the Technology page.
"Who operates your border controllers?"
If the answer names a partner, you are buying through a middle layer. Ours are our own, run redundantly — described component by component on this site.
"Can you show me a live call and its trace?"
An operator can pull a SIP capture of your actual traffic. A reseller can forward your question. Ask before you commit traffic, not after.
"Where do my settlement numbers come from?"
The honest answer is a data path. Ours: per-second records written by the switch at call completion, feeding billing directly — one system, no reconciliation gap.
"What happens when a route degrades at night?"
Listen for who acts: their team on their switches, or an email to a vendor. Our monitoring and routing policy act on our own platform, around the clock.
What it means for you
Pick the model, then the company.
The practical difference
Model choice shows up on ordinary days as speed — allocation from the portal, changes that apply immediately, reports that exist the moment traffic completes. It shows up on bad days as truth: an explanation from the system itself, and a fix applied by the people you are already talking to.
HiClass is an owner-operator by construction: registered in Ramallah in 2019, running its own platform, and building the same class of systems for others. Judge the claim the right way — read the Technology page, then ask us the four questions above.
- Registered in Ramallah in 2019 — Reg. No. 562585406, checkable
- Platform described component by component, publicly
- The four questions above — we invite them
- The same engineers build platforms for customers
Come ask the hard questions.
Bring the four questions on this page and any traffic scenario you care about. You will be answered by people who operate the platform — which is, in the end, the whole point.