Omevision
US AI and technology company · Core technology for African institutionsLagos · Nairobi · Accra · Johannesburg · Mbabane

We build the technology Africa runs on

Identity, verification, payments, messaging and AI. Eleven products of our own already run on them. So can yours.

Discuss your requirementsExplore our products
01 — About us

We build core technology: the identity, verification, payment, messaging and AI layer beneath African software. Then we build the systems institutions run on top of it. Nothing reaches a customer that has not already carried our own products in production.

Omevision is a US-incorporated AI and technology company. Our mission is to lead the development of practical AI infrastructure for African markets. YeboAI supplies shared intelligence across our products, while Yebo connects them through one assistant.

Fig. 00 / Systems architecture

Everything we ship sits on five services. So does everything we build for you.

No client edition, no cut-down tier, no separate roadmap. A system built for you attaches at the same layer our own products do.

L1Foundation

What it runs on

  • Managed containers
  • Managed Postgres
  • Edge and storage
  • Model providers
  • CI and delivery
  • Observability
L2Platform

The five services

  • YeboIDIdentity and single sign-on
  • YeboVerifyKYC, KYB and AML
  • YeboPayPayments and settlement
  • YeboLinkSMS, WhatsApp and email
  • YeboAIShared inference layer
L3Surface

What people actually use

Our own products · 12
  • Eneza
  • YeboLearn
  • YeboLand
  • YeboShops
  • YeboCars
  • YeboLift
  • YeboMart
  • YeboDash
  • Yebona
  • YeboJobs
  • YeboTickets
  • YeboForge
Built for customers
  • Financial
  • National venue
  • Government
  • City council
  • Transport
  • Yours
L4Conversation

Yebo, the conversational layer

One assistant, signed in once, driving every product beneath it over MCP.

L5Frontier

Autonomy

Not built

Earth observation and the data layer beneath it. What is on the ground, where, and what changed since the last pass.

L4 is where the leverage is

One conversation operates every product beneath it, so a new capability arrives everywhere at once rather than product by product.

Same layer, no lesser tier

A system built for you attaches where our own products attach. There is no client edition running behind a version.

The portfolio is the test rig

Nothing reaches a customer that has not already carried our own traffic, at our own expense, for months.

L5 is dashed on purpose

It is not built. It stays drawn that way until it flies, on this page and everywhere else we draw it.

Read from the ground up. Every other figure on this page is a detail of one of these five layers.L1 — L5
02 — Selected deployments11 engagements · 7 public sector

Delivered systems. Verifiable results.

Our delivery record spans regulated finance, government, national venues, transport and enterprise operations. Explore the systems delivered in each sector, with named case studies and client references available through our partnerships team.

  • Regulated financial institutionRegulated
  • National sporting venuePublic sector
  • Central government agencyPublic sector
  • National police servicePublic sector
  • City councilPublic sector
  • National transport sectorPublic sector
  • Regional intergovernmental summitPublic sector
  • Municipal parking operatorPublic sector
  • National holding groupPrivate
  • Events and retail operatorPrivate
  • Construction group, United StatesPrivate
Decisions from the record

Administration is what each of these systems does. The record it leaves is what changes how a ministry decides.

Read the full register
03 — Standards held to

Standards demonstrated in delivered systems.

Regulatory review, venue standardization and security architecture demonstrated through institutional deployments. Supporting reviews and reference contacts are available on request.

Regulator-cleared onboarding

The regulator reviewed the verification flow, the record-keeping and the retention terms before onboarding went live. Nothing there is self-certified, and the review is repeatable on request.

National financial regulator

FIFA venue standardization

The entry and crowd-flow requirements a standardized venue is held to were audited against the system as deployed, at full capacity rather than in a test.

Venue standardization

Government-grade architecture

Identity on every request, row-level scoping and a complete audit trail — applied across the whole estate rather than assembled for one deployment under review.

Applied estate-wide
04 — The portfolio

Twelve products. One shared platform.

Our portfolio spans advertising, commerce, education, logistics, employment and industry. Our established products use our shared platform services; YeboForge is in development for factory pilots.

Who they serve
For shopkeepers
restocking and settling with a supplier from one thread.
For skilled workers
finding work without a CV or a data bundle to spare.
For schools
keeping records digitally and managing daily operations.
For factory owners
planning material accountability and production visibility with YeboForge.

Our products give us direct experience of the workflows our clients need: trading, hiring, payments and record-keeping. Explore all products.

05 — The platform

The platform you build on.

Five services, each one carrying our own products in production before it carries yours. You integrate them, or we build on top of them for you. There is no third arrangement.

  • YeboID

    Identity and single sign-on

  • YeboVerify

    KYC, KYB and AML

  • YeboPay

    Payments and settlement

  • YeboLink

    SMS, WhatsApp and email

  • YeboAI

    Shared inference layer
What each of the five does
06 — Custom builds

The system we build for you.

Some systems cannot be bought. A national venue’s gate control. A regulator-cleared onboarding flow. A ministry’s citizen request desk. We build those on the platform above, not on a separate stack kept for clients.

What you get

A system specified against your process, built in your environment, and operated by your team. Identity, verification, payments and messaging are already solved before the first line is written for you.

What it runs on

The same five services that carry every one of our own products in production. You are not the first traffic they will see.

What it is not

Not a licence to a product that almost fits. Not a tier. Not a pilot that quietly becomes the production system.

07 — How we engage

Direct engineering. Clear accountability.

A named engineering team, a written scope and clear responsibilities from the first conversation through deployment and handover.

Who does the work

The engineers who built the platform, working directly with your team. Named contacts, regular technical reviews and one clear line of accountability.

How it runs

Two-week increments against a written scope. Something running in your environment inside the first month, rather than a design document that describes one.

Who is on call

A named engineer, an escalation path, and a response window written into the contract rather than into a brochure.

What handover looks like

Your team commits to the same repository from the first week. Runbooks, architecture notes and an operations walkthrough land before the engagement closes, not after it.

08 — Security and data

Six questions procurement asks, answered in writing.

Rather than extracted over six weeks of email. Each one is answered in full, alongside the authorization model and the document pack.

  1. 01Where the data lives
  2. 02Who can reach it
  3. 03What is written down
  4. 04Who else touches it
  5. 05Who owns it
  6. 06When something fails
Read the answers
09 — Continuity

Ownership and continuity, defined from the start.

Source code, data access, operational handover and exit terms are covered in writing before the engagement begins.

Who owns the code

You do. The system built for you is yours, in a repository you control, from the first commit rather than the final invoice.

Who owns the data

You do. A full export in an open format is a term of the contract, not a favour at the end of one.

If we part ways

Exit terms are written at the start: source, data, runbooks, and a handover period long enough for your team or another supplier to take it over without a gap in service.

Where we operate

Omevision is a US-incorporated AI and technology company. Yebo Hub in Manzini provides coworking space, meeting rooms, a studio and a café.

10 — FrontierNot built

Nobody has flown this ground. So nobody has the data.

Aerial survey, models that read what comes back, and a data layer that compounds every pass. Most decisions about ground in this region are still made against a survey somebody did years ago.

Fig. 07 / Autonomy · the frontier layer

Fly it. Land it. Read it. Act on it. Then fly it again.

Four stages and a season that returns to the start. The loop is the point — one pass is a survey, six are a record nobody else holds.

Swipe to see the whole drawing

01 · SURVEYWe fly itFarmland, parcels, catchments,on a repeatable schedule02 · DATAIt lands somewhereJoined to the parcels already inYeboLand. Sovereign, not exported.03 · MODELSSomething reads itCrop health, yield estimate, waterstress, encroachment, disease04 · DECISIONSomeone actsA ministry plans. An agency targets.A farmer gets a message.EVERY SEASON, THE RECORD GETS LONGER
Drawn dashed on purpose. None of this is built, and the audience for this page checks.Not built
Why it compounds

The asset is not the aircraft. It is the time series.

Anyone can buy a drone. What cannot be bought is six seasons of the same ground, joined to a registry, across markets where nobody else has flown. That moat widens on its own, which is the argument for starting now rather than when the models get better.

Who it servesOne set of passes, a different question in each.
Logistics
Corridors, ports and road conditions, so a route is planned against what is on the ground now rather than what was there last year.
Border and national security
What is at a border, a coastline or a site of interest, and what moved since the last pass. Observation on a schedule, with the record kept in-country.
Agriculture
Food-security forecasting, subsidy targeting and drought response against real numbers instead of last year’s survey.
Land and tenure
Parcels, boundaries and encroachment, joined to the registry already in YeboLand rather than held in a system of its own.

Not built yet. Drawn dashed everywhere it appears, and it stays that way until it flies.

11 — Engage

Tell us what you are working on.

Send your requirements to our team, or start a meeting with our assistant to explore the products and discuss a system you need built.

Start here

No procurement process required to begin.

Or email contact@omevision.com

A briefing

Forty-five minutes on what you are trying to do and whether we are the right supplier for it. We will say if we are not.

Request a briefing →

A technical review

Your engineers and ours, on the architecture, the data boundary and the integration surface. Bring the objections.

Book a technical review →

References and documents

Capability statement, sub-processor list, processing terms, and contacts at deployments already running.

Request the pack →
Who answers

Laslie Georges Jr

Founder and Chief Executive

contact@omevision.com
Company locations
  • Delaware, United StatesPlace of incorporation
  • Mbabane, EswatiniEswatini branch
  • CameroonCameroon branch

Explore YeboTickets features

See all features

Explore YeboAI features

See all features