Asked in every briefing.
Answered in writing.
The questions evaluators, architects and procurement teams actually ask — kept honest because we answer them the same way in contracts.
Ownership & commercial
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. Itemised on the licensing page.
Are there per-seat or per-transaction fees?
No. The platform is licensed per deployment — not per seat, not per transaction, not per citizen. Growth is your success, not our billing event.
What happens if we stop working with Emeron?
You keep the platform, the solutions, the metadata and your certified team. Support and updates end; nothing that runs stops running. We would rather earn the next contract than hold the last one hostage.
How do engagements start?
With a deliberately small decision: ninety days, real services, your environment, your team in the room — priced and terminable on its own, with everything produced belonging to you either way. See how it works.
Technology & security
Which technologies is the platform 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.
How is security actually enforced?
At the runtime kernel: one write path, a compiler boundary in front of your data, row- and field-level security injected into every operation, and a tamper-evident audit trail — fail-closed. Details on the security & trust page.
Where does AI sit in the engine?
AI drafts services, rules and interfaces into versioned metadata — people review, the compiler admits, the kernel governs. It never bypasses the pipeline. See the AI engine.
Can it run air-gapped?
Yes — the platform is identical across public cloud, sovereign cloud, on-premises, hybrid and fully disconnected postures. Moving between them is a deployment decision, not a re-build.
What happens to our existing systems?
They are integrated first and retired gradually — the platform absorbs services one 14-day cycle at a time, and legacy retires when its last service has moved.
Delivery & people
How fast is a first go-live, honestly?
Twelve to sixteen weeks is the typical pattern for first production services — because discovery, integration and hardening happen once, up front. After that, each new service is a 14-day configuration cycle, typically.
What does our team need to look like?
Smaller than you expect: analysts who own services, administrators who own governance, engineers who own integrations. The academy certifies them on the tooling we use ourselves — and our share of each cycle falls by design.
Can we talk to institutions already running it?
Yes. We arrange reference calls directly between your evaluators and client platform teams — under their terms, about the parts that were hard. Start from engagements.
Who delivers — Emeron or partners?
Both, to one standard: certified delivery partners train through the same academy and are backed by Emeron engineering. See the partner programme.
The four answers
behind every question.
A question we haven’t answered?
Ask it — the right person replies within one business day, and the good ones end up on this page.