Not a concept.
A shipped platform.
A metadata engine, code generation and a Service OS — orchestrated so a defined system becomes a running one without ever losing its context. AI-assisted. Governance you cannot switch off.
One governed stack.
Every layer runs on the same kernel.
Every layer above the kernel is defined as versioned metadata — which means every layer can be regenerated, audited and owned. Nothing is hand-wired; nothing is a one-off. Hover a layer to see it in the stack.
Six components.
One centralised power.
Metadata engine · code generation · Service OS — one centralised tool that carries the real power.
Admin Studio
Design-time orchestration — entities, services, data and interfaces defined as versioned metadata.
Runtime Engine
Executes every solution from governed metadata. One write path. Fail-closed.
Governance Kernel
RLS & FLS enforced at the core — row and field security injected into every operation, by construction.
AST · QL · EL Engine
A compiler boundary — only governed queries and expressions ever reach your data.
Service Layer
Composable services for building portals — citizen, customer and officer experiences on one foundation.
Report Designer
In-built enterprise reporting — governed by the same kernel as everything else.
You cannot ship
an ungoverned app.
It isn’t a rule a developer follows. It’s a property of the platform they cannot switch off. Every request — UI, API or query — travels one governed path.
Any request
UI · API · query — however it arrives.
Compiler boundary
Only governed metadata runs — raw SQL never reaches the database.
Row-level security
Only the rows you may see — fail-closed.
Field-level security
Only the fields you may see — everywhere.
Governed result
Nothing ungoverned escapes — with a tamper-evident audit trail.
This is the difference between our engine and ungoverned AI generation: beautiful on the surface is not enough. No row-level security, secrets in the source and actions that leave no evidence behind are a risk for a business — and a liability for a government.
A team of few.
The output of a hundred.
Because solutions are generated from governed metadata rather than hand-built, a small certified team delivers what a hundred-person programme used to — and every deliverable stays maintainable, auditable and yours.
Five ways to deploy.
One identical platform.
Your data lives where your law says it must — and moving between postures is a deployment decision, not a re-build.
Public cloud
Managed and elastic — fastest path to production.
Sovereign cloud
In-jurisdiction government or regulated cloud.
On-premises
Your data centre, your keys, your perimeter.
Hybrid
Split by data classification — sensitive stays home.
Air-gapped
Fully disconnected — for the estates that demand it.
Asked in every briefing.
What do we actually own at the end?
The running platform, every solution defined on it, and the metadata that defines them. Your licence is perpetual for what you deploy — the year-seven answer is that you keep running the platform, because you already own it.
How is this different from low-code platforms?
Low-code rents you speed and keeps the governance question open. Emeron generates production-grade systems from versioned metadata behind a kernel that enforces row- and field-level security on every operation — and the result is an asset you keep, not a subscription you outgrow.
What happens to our existing systems?
They are integrated first and retired gradually. The platform runs alongside your estate, absorbs services one at a time, and each migration is a 14-day configuration cycle rather than a big-bang rewrite.
Where does AI sit in the engine?
AI assists at design time — drafting metadata, services and interfaces. It never bypasses the kernel: whatever is generated compiles through the same governed boundary as anything a human defines. Modern speed, engineered governance.
What does our team need to look like?
Smaller than you expect. Trained analysts and administrators configure services; your engineers extend capabilities. Certification transfers the capability to your staff — the dependency on Emeron decreases over time, by design.
Which technologies is it engineered on?
.NET, PostgreSQL and React — an open, portable, enterprise stack with first-class support for MySQL and SQL Server estates. No exotic runtime, no proprietary database, no hostage formats.
Walk the architecture with the people who built it.
A technical session for your architects and security team — kernel, compiler boundary, deployment postures, and the exit question answered in writing.