Raye Technology Plc
We build trust infrastructure for Ethiopian software. Emnet is our first product.
Why we built Emnet
Ethiopia now has a national digital identity. That is a genuine step change — for the first time, a piece of software can ask “is this a real, uniquely identified person?” and get an authoritative answer.
The obstacle was never the technology. It was that every company wanting to use it had to become an identity integrator: a partner agreement, a relying-party registration, cryptographic key custody, OpenID Connect and JOSE correctness, and a permanent obligation to protect the most sensitive identifier a citizen has. For a ten-person fintech, that is a quarter of engineering work before a single user is verified.
Worse, the naive version of that architecture spreads national identity numbers across dozens of private databases. Every one of those is a breach waiting to be correlated with the others.
So we took the opposite approach. Raye Technology Plc holds one relationship with the national identity infrastructure, and exposes it as an API that hands back verified claims and a pseudonym — never the identifier itself. One integration point to secure properly, instead of fifty secured unevenly.
The name is the Amharic word for trust. It is what our customers extend to us and what they are trying to establish with their own users. It seemed like the right thing to be held to.
What we believe
- Data you never receive cannot leak from you. The strongest protection for a national identifier is for it to never arrive in the first place.
- Verification is not a decision. We report what was verified. What it means for an account belongs in our customers’ own systems, where their regulators can see it.
- Defaults decide outcomes. Claim release is default-deny, environments are resolved server-side, and a test key cannot reach production. Safety that depends on every integrator being careful is not safety.
- Boring, documented, versioned. Identity infrastructure should be the least surprising dependency a team has.
Security
Emnet is a security product before it is a convenience one. Personal data is encrypted at rest, API keys are stored hashed, and keys, personal data and released claims are never written to logs on any surface. Claim release is default-deny and cross-tenant access is indistinguishable from “not found”.
If you believe you have found a vulnerability, please write to security@emnetid.com before disclosing it publicly. We will acknowledge your report, keep you updated while we fix it, and credit you if you would like us to. We will not pursue action against good-faith research that respects user privacy and avoids service disruption.
More on the platform’s security posture →
Contact
- Sales and partnerships
- sales@emnetid.com
- Technical support
- support@emnetid.com
- Security disclosure
- security@emnetid.com
- Office
- Raye Technology Plc
Addis Ababa, Ethiopia
If you are evaluating Emnet for a regulated product, tell us what you need to prove and to whom. We would rather talk through your compliance requirements early than have you discover a gap in month three.