Request a briefing →
The licensing model

Owned, not rented.
In the contract, not the slogan.

The model is simple enough to state in three lines: a perpetual licence for what you deploy, no per-seat fees, and everything defined on the platform — solutions, workflows, metadata — is your asset.

Discuss your structure →
How it’s structured

Three components.
No meters on your growth.

Component 01

Platform licence

Perpetual, per deployment — not per seat, not per transaction, not per citizen. Growth is your success, not our billing event.

Component 02

Delivery & certification

The 90-day path, integrations, and academy certification for your team — a defined scope with a defined end, priced as work, not as dependency.

Component 03

Support & evolution

Optional annual support with platform updates and engineering access — renewable because it earns renewal, terminable without losing what runs.

What you keep

The year-seven answer,
itemised.

If our relationship ended tomorrow, this is what would still be yours, running, in your environment — in writing, in the agreement.

The platformPerpetual right to run everything you deployed — indefinitely.
The solutionsEvery service, workflow and portal configured on it.
The metadataThe versioned definitions your systems generate from — readable, exportable.
The dataIn PostgreSQL / SQL Server / MySQL — open formats, standard tooling.
The capabilityYour certified staff — and the right to keep configuring without us.
Against the alternatives

Where the money goes,
compared.

Tier-1 pattern — services & integration share of total cost60–80%
SaaS pattern — cumulative rent, year on year, foreverRising
Emeron — spend that becomes an asset you keepThe platform, yours

Pattern-level figures — no vendor named; your own contracts will tell you where you sit.

Put the model against your numbers.

Bring your current licence and services spend. We’ll map both onto this structure — and you keep the comparison either way.

Discuss your structure →