Registry

One record per person, across every register you keep.

Schedule a meeting

The ID is enrolled. The registers still disagree.

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.

What connected registers deliver

The engine proposes. A person decides.

  1. A name matched across scripts

    Amharic to Latin, patronymic naming, records with no reliable date of birth.

  2. A score, not a verdict

    Every candidate carries a score. The system never returns a yes on its own.

  3. A person decides

    An officer reads the documents and decides every consequential match. This is not a setting that can be switched off.

  4. An appeal path at the counter

    A contested match opens a case, and the payment keeps arriving while it is open.

Hosted on your soil

In-country, written into the contract. A policy can be rewritten without anyone telling you; a contract cannot.

Encrypted field by field

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.

Every read is on the record

Not only every write. Who looked at a person's file, and when.

Under your national law

In Ethiopia that means the Personal Data Protection Proclamation 1321/2024, named by number in the contract.

Paid out of what it recovers

Recovered wages and halted duplicate payments fund the deployment.

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. Verider runs no face search, keeps no watchlist and takes no camera feed. This is a system for recognizing people, not for watching them.

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, 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.

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.