Sovereign hosting
On your soil, named in the contract.
A connection nobody recorded still draws power every night
More than half of grid-connected households are not registered consumers. Power delivered to a home with no account can never be billed, and never shows as a loss because it never shows at all.
34.4% of the water Uganda's national utility supplies never earns revenue, rising to 39.1% in Kampala.
National Water and Sewerage Corporation, FY2024/25
Nigeria's distributors never earn revenue on 37.4% of the power they receive.
Nigerian Electricity Regulatory Commission, Q1 2026
More than 27% of the power entering Ethiopia's grid is lost before it is paid for. The national target is under 19% by 2030.
National Energy Compact, Ethiopia, 2025
Addis Abeba's non-revenue water has not moved from its 2020 baseline of 39%, against a program target of 34%.
World Bank, Second Ethiopia Urban Water Supply Project, 2026
South African municipalities owed Eskom R110.5 billion as at 31 December 2025.
National Treasury, Budget Review 2026
Ethiopia's target is commercial losses down from 10% to 4.5%, and a collection rate above 90%, by 2030.
National Energy Compact, Ethiopia, 2025
Where the module earns its keep
From the meter read to money in the account.
-
Reading capture and validation
Captured on a phone, checked against the meter's own history before a bill is generated.
-
Billing on consumption
What the meter says, checked, and delivered to the customer's phone.
-
Collection on every channel
The same receipting and same-day matching as the revenue module, on the rails people already use.
-
Disconnection on the record
Every disconnection carries a named approver and a written reason. Reconnection is logged the same way, so a household can be told why the water stopped and when it returns.
Verider · Utilities
Validated
Reading · Feeder 12 · Cycle 6
A field reading validated against the meter's history before billing.
- Reading within expected band
- Bill generated
- Digital delivery queued
Cycle 6 · Billing
14,203 reads
The units that leave the plant and never reach a bill.
-
Connections with no account
Live connections with no billing account behind them, listed with a location.
-
Silent meters
Meters that have reported nothing for several cycles while the service stayed on.
-
Zeros nobody ordered
Consumption falling to zero with no disconnection order on file.
-
Estimates that never end
Estimated bills running past the policy threshold, and consumption gaps between neighboring premises of the same size.
-
Two collection rates, side by side
One measured against bills issued, one against energy delivered.
Verider · Utilities
Flagged
Detection · District 4 · Water
A meter silent for three cycles at a connection still drawing service.
- Connection confirmed active
- No disconnection order on file
- Field inspection assigned
Watchlist · 37 open
3 cycles
Two registers, one building, nothing missed.
-
One premises record
Utilities and revenue read the same record, and both keep it current.
-
Cross-findings, then a decision
A building that pays for water but not rates comes up as a referral, and a named officer decides what follows.
-
Each finding makes the next one easier
A parcel confirmed by the water account is a parcel the valuation roll no longer has to guess at.
Verider · Utilities
Matched
Cross-check · Premises 5521
An active water account found with no property rate on file.
- Water billing confirmed
- Rates register searched
- Assessment referral opened
Cross-findings · This month
112 premises
Field-level encryption
Personal data is encrypted, field by field.
Complete audit trail
On every read and write, views included.
Under your national law
Your law governs the deployment, not a vendor's policy.
Paid out of what it recovers
No upfront budget line, just a baseline your finance ministry sets.
FAQs
Where does the platform run?
On a server in your country, or in your region where you choose that. The region, the facility and the exit terms go into the deployment contract, so they are not a policy a vendor can revise. It runs offline where connectivity thins and takes mobile money where payments happen.
Whose law governs our data?
Yours. Personal data is encrypted field by field. Access is scoped to the field, so a market-fee clerk cannot query the pension roll. Every read and every write lands in the audit trail, views included. The schema holds what your mandate needs and nothing more; what that includes is settled with your ministry and your data protection authority before go-live, then written into the contract.
How does a pilot start?
With one slice of the mandate, named by your team. It runs against your own records, in your own building. What it recovers is a figure your own finance people can check, and that figure is what your team carries into the tender for the rest.
Which languages does it run in?
It is built for names as your people write them, not for one alphabet. This site runs in seven: English, French, Spanish, Swahili, Arabic, Hausa, Amharic. Your deployment's languages are named by your team.
What happens after go-live?
Support and maintenance terms sit in the deployment contract, from response times to upgrade duties to who is on the phone and when. Written before go-live rather than assumed after it, and your team is trained to run the system without us. Verider does not sell incident response or security monitoring; where your ministry needs those, they are procured separately.
How do we buy this?
Through your own process, from expression of interest to formal tender. Where your rules allow it, we will propose terms that take payment out of what the system recovers, so the cost sits against new collections rather than a budget line that is already committed. If the tender still has to be written, a meeting is the fastest way to scope what it should say.
What does it cost?
The build is paid for out of what it recovers, so there is no new budget line to win before the work starts. Terms are set against measured results from your own pilot.