One front door.
Every service behind it.
Citizens do not want forty portals; they want their permit. Emeron powers one governed front door — every service, one identity, one application tracker, one place to pay — on web and mobile, Arabic and English first-class.
What the engine
generates.
Six governed parts, one description. Your analyst describes the service in Studio; the engine generates all of it — application, workflow, portal, audit.
One identity
National identity integration signs citizens in once — with guardianship, delegation and business roles modelled properly.
Service catalogue
Every service published from the same engine that runs it — descriptions, requirements, fees and SLAs always in sync with reality.
Unified tracker
Applications across ministries in one timeline — status, actions required, and the SLA clock the institution is held to.
Payments & wallet
Fees paid through national rails; receipts, certificates and permits land in a documents wallet — verifiable, reusable.
Notifications that matter
Status changes, expiries and appointments over channels citizens actually read — with quiet governed APIs behind each.
Feedback loop
Ratings and complaints per service feed dashboards leadership actually watches — the portal measures the state it fronts.
The portal is the
easy part — if the
engine is real.
Portal projects fail when they are wallpaper over disconnected systems. On Emeron the portal and the services are the same platform — publish a service and its forms, fees, SLAs and tracker appear, because they are one thing.
CitizenOS is that layer: the citizen experience of the governed engine underneath.
- WCAG-conscious, Arabic-first, mobile-first experiences
- Guardianship, delegation and business profiles modelled
- Every service’s SLA public — and enforced by the kernel
- No integration wallpaper: portal and engine are one platform
Measured, not
promised.
Before the
briefing.
Can the portal front services that still run on legacy systems?
Yes — legacy services can appear in the catalogue and tracker through governed APIs while your team progressively re-platforms them. Citizens get one front door on day one; the estate modernises behind it.
How is accessibility handled?
As a default, not a retrofit: semantic structure, keyboard and screen-reader paths, contrast discipline and reduced-motion support are part of the generated experience.
Is there a mobile app?
The portal is mobile-first web, and a native shell is available where an app-store presence is required — same governed services underneath.
Who owns the citizen data?
The state, without asterisks. Data lives on your infrastructure under your law; Emeron is the engine, not the custodian.
Give citizens the one door they wanted.
Portal live with its first services in ninety days — Arabic-first, owned by the state.