Hosted on your soil
In-country, written into the contract. A policy can be rewritten without anyone telling you; a contract cannot.
Enrollment had a playbook, followed at enormous scale. None exists for what comes next. Reconciliation crosses ministries that never shared a key, and turns on judgment no algorithm should make alone.
Amharic to Latin, patronymic naming, records with no reliable date of birth.
Every candidate carries a score. The system never returns a yes on its own.
An officer reads the documents and decides every consequential match. This is not a setting that can be switched off.
A contested match opens a case, and the payment keeps arriving while it is open.
One name, spelled two ways, matched across scripts and scored for an officer.
And when she dies, her family reaches survivor benefits the same month.
Every salary on the run matches a serving employee, and what the run returns goes back to the schools.
Title, license and utility connection resolved to one owner, across ministries that have never shared a number.
Vital events recorded once, so the health budget is sized to the district it serves.
Every salary on the run checked against the civil registry and the national ID.
In-country, written into the contract. A policy can be rewritten without anyone telling you; a contract cannot.
The schema has no field for ethnicity, religion or political affiliation. Switching one on would take a code change, and that is not a change we make.
Not only every write. Who looked at a person's file, and when.
In Ethiopia that means the Personal Data Protection Proclamation 1321/2024, named by number in the contract.
Recovered wages and halted duplicate payments fund the deployment.
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.
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. Verider runs no face search, keeps no watchlist and takes no camera feed. This is a system for recognizing people, not for watching them.
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.
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.
Support and maintenance terms sit in the deployment contract, covering response times, upgrade duties, 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.
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.
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.