eKYC & Digital Identity
Onboarding in minutes, every step auditable
Solutions
Five capabilities. One accountable partner.
Most digital programmes here are assembled from four or five separate vendors, and the joins between them are where schedules slip. eLON delivers connectivity, identity, biometrics and applied AI under one licence, one contract and one escalation path.
The three layers we operate
- ConnectivityLicensed VISP services, fibre, wireless and managed network operations
- TrusteKYC onboarding, biometric matching and auditability controls
- IntelligenceAmharic, Afaan Oromo and English AI on top of the data
Capabilities
What we actually deliver
Five capability lines. Two of them — eKYC and VISP — are the ones most programmes start with, because they unblock everything downstream.
VISP — Virtual ISP
Enterprise internet, service levels agreed per tier
Biometric Solutions
Fingerprint, face, iris · AFIS / ABIS · anti-spoofing
Telecom & Network Infrastructure
Fibre, microwave, wireless — turnkey and managed
AI & Data
Amharic · Afaan Oromo · English AI, on-prem ready
Not sure where to start?
Most programmes begin with one capability and grow. Tell us the outcome you need and we will say which combination gets you there — including when the honest answer is that you need one of these and not the other four.
Why one partner
The seams are where projects fail
A digital identity programme needs a network path. That network path needs to reach a branch that has no fibre. The data that runs over it only becomes useful if it can be read in Amharic. Integrating four specialists is a project in itself — and when something breaks, four suppliers point at each other.
01
VISP
Connectivity layer
Licensed VISP services, fibre and wireless access, backhaul, SD-WAN and managed network operations. This is the layer that makes everything else reachable.
02
eKYC
Trust layer
eKYC onboarding, biometric matching (fingerprint, face, iris) and the credential, liveness and auditability controls that regulators ask about first.
03
AI & Data
Intelligence layer
Amharic, Afaan Oromo and English language AI, document and speech processing, and analytics built on the data the first two layers generate.
One contract, one escalation path
When you buy the layers separately, an incident that crosses a boundary becomes a coordination problem. Under a single contract there is one number to call and one party accountable for restoration, regardless of which layer caused it.
- A single technical account owner named in the contract, not a shared inbox.
- One service schedule covering every purchased line, so performance is reported together.
- Change requests assessed across layers — a new branch does not become three separate tickets.
- Joint acceptance testing, so handover happens once rather than per vendor.
How we are licensed. eLON operates under Ethiopian licensing for the services it delivers. Licence documentation is provided for your procurement file on request — we do not ask you to take this on trust.
Engagement models
Two ways to buy, chosen by who runs it afterwards
Most common
Managed service
You buy an outcome and a response path. We run the platform, the network and the monitoring; you own the business process.
- Lowest internal capability requirement — no new team to hire.
- Faster start, because delivery does not wait on your hiring.
- Service levels, response targets and reporting defined per service tier.
- Clear exit provisions: data, configuration and documentation are yours.
Commercially: recurring, per service tier and volume band. Structure confirmed per scope.
Build & transfer
You buy a system and the capability to run it. We design, build, commission and train; your team takes the keys.
- Capital purchase with defined acceptance criteria.
- Knowledge transfer and operator training written into the plan.
- On-premises or in-country hosting for data that cannot leave.
- Optional warranty and support window after handover.
Commercially: one-off delivery, with support as a separate line.
Reference architecture
How the layers join up
A generic view of a combined deployment. Your own design will be produced after a requirements survey.
Integrated delivery stack — indicative
Access
Fibre, microwave and wireless last mile; branch and campus connectivity.
Transport
Licensed VISP capacity, IP transit, redundancy and routing policy.
Platform
Identity, biometric and AI services; APIs and integration adapters.
Business systems
Core banking, HR, registry or case systems that consume the services.
Operating under one service schedule and one NOC view
Cross-cutting: security
Encryption in transit and at rest, key custody, access control and audit trails.
Cross-cutting: data residency
In-country or on-premises hosting where the requirement demands it.
Cross-cutting: reporting
Service performance, incident history and usage reporting on a fixed cycle.
Diagram is indicative and for discussion only. No quantitative service commitment should be inferred from it — performance terms are set per service tier and confirmed in the signed service schedule.
FAQ
Questions we are asked in procurement
Answers written for the people who have to defend the decision internally.
Can you work to our existing technical specification?
Yes, and we prefer it. Send us the specification and we will respond line by line, marking anything we cannot meet exactly, anything we would propose to change, and anything that is left open. That is more useful to an evaluation committee than a response that claims compliance with every clause.
Do you subcontract, and who is accountable if you do?
For civil, rigging and specialist cabling works we often do use vetted Ethiopian subcontractors. eLON remains the single contracting party to you: subcontractors work to our method statements and pass through our quality gate, and the escalation path in your contract does not change.
How do you handle pricing and commercial terms?
Pricing is structured per scope — service tier, volume band, site count and contract length. We do not publish a price list because the honest answer depends on the survey. We will give you a written commercial structure after a scoping conversation, not a headline number that changes later.
What happens at the end of the contract?
Data, configuration and documentation are yours. We produce a handover pack on request at any point, not only at exit, and the agreement includes provisions for transition assistance so that leaving is a planned activity rather than an incident.
Do you require data to leave Ethiopia?
No. Deployment can be on your premises, in-country, or hybrid. Where a service has to reach an overseas component, that is stated explicitly in the design and in the data protection appendix rather than left implicit.
Next step
Bring us the problem, not a specification.
The most useful first conversation is a technical one: what has to work, by when, and what has already been tried. We will tell you plainly whether it is something we should be doing.
Technical first responseA qualified engineer reviews your requirement before anyone calls you.
Written scopeYou receive a documented approach, assumptions and exclusions you can circulate internally.
Local channelsReach us on phone, WhatsApp, Telegram or email — whichever your team already uses.
One point of accountabilityOne contract and one escalation path across connectivity, identity and AI.