EMERON.IO / GLOBAL GOV-TECH / HQ SHARJAH SRTIP / EST. 2013
§ 01 / HOW EMERON PRICES

Pricing follows deployment shape.

Government and public-sector procurement does not fit one commercial model. A defence ministry deploying on-premises has a different commercial shape from a city council subscribing to a permit workflow. A multi-year national rollout has a different shape from a single-agency pilot.

Emeron supports five commercial models, intentionally. Most procurements pick one. Some combine two. Below is the public posture; precise pricing is provided after a discovery conversation, because the variables that drive cost — number of agencies, number of users, integration scope, language pairs, deployment topology — are the same variables that drive the entire shape of the deployment.

The orientation is consistent across models: license fees are deliberately weighted away from us and toward your internal capability. The economics work because the customer stays for years longer than they would under a high-services model — not because they cannot leave.

§ 02 / COMMERCIAL MODELS

Five supported models. You choose.

Every Emeron contract is shaped around one of the five models below. Where two models overlap — for example a subscription with an embedded capability-transfer program — the contract names both explicitly. Hybrids are common.

MODEL 01

Perpetual license

One-time platform license fee with annual support and maintenance. Customer owns the licensed software in perpetuity.

TYPICAL USE: DEFENCE · ON-PREM
SUPPORT: ANNUAL 18–22%
UPGRADES: INCLUDED 36 MONTHS
MODEL 02

Subscription

Annual platform license per agency, jurisdiction, or named user-tier. Includes all upgrades, security patches, and standard support.

TYPICAL USE: CITIES · STATE
TERM: 3 / 5 / 7 YEAR
UPLIFT CAP: CPI OR 5%
MODEL 03

Build-Operate-Transfer

Emeron builds and operates the deployment for a defined period, then transfers ownership to the customer at a contractual milestone.

TYPICAL USE: NATIONAL ROLLOUT
BUILD: 12–24 MONTHS
TRANSFER: MONTH 24–36
MODEL 04

Capability transfer

Lower license fees deliberately weighted toward academy investment and internal capability. The customer becomes self-sufficient on the platform within 18 months.

TYPICAL USE: FEDERAL · CENTRAL
ACADEMY: 30–200 SEATS
GATE: CERTIFICATION MILESTONES
MODEL 05

Hybrid

Combinations of the above per agency or per module. Common for multi-agency programs where the federal centre operates differently from line agencies.

TYPICAL USE: PROGRAMME-LEVEL
STRUCTURE: PER-AGENCY
GOVERNANCE: PROGRAMME BOARD
§ 03 / COST DRIVERS

What actually moves the number.

Pricing variables are unusually similar across our deployments because the platform is unusually similar across deployments — that is what configuration-not-customization buys you. The seven variables below explain the overwhelming majority of cost variation.

DRIVER 01

Number of agencies

Single agency vs. multi-agency vs. federal-scale deployment. Largest single driver of cost.

DRIVER 02

Deployment topology

Cloud subscription is the lowest baseline. On-premises and air-gapped are higher. Hybrid sits in between.

DRIVER 03

Module scope

Single-module pilots are priced separately. Full GovStack deployments are priced as a platform.

DRIVER 04

Integration surface

National identity, national payment switch, legacy registries, central reporting — each is a known unit of work.

DRIVER 05

Language pairs

Bilingual is standard. Trilingual+ deployments include additional content engineering and accessibility validation.

DRIVER 06

Compliance posture

Standard sovereign deployment vs. classified vs. multi-jurisdiction with conflicting regulatory regimes.

DRIVER 07

Capability transfer depth

Standard academy program vs. deep program with sovereign codebase governance, fellow exchange, and quarterly reviews.

A NOTE ON PUBLISHED PRICE LISTS

We don't publish a price list. Here's why.

Most enterprise platform vendors publish list prices that nobody pays, attached to "discount" structures that reward the largest deals. The published number is theatre. The actual number is set in the room.

Government procurement deserves better than theatre. A 30-minute scoping call tells us your deployment shape, and a written proposal — with line items, assumptions, and pricing model options — follows within five business days. The proposal is the price. There is no list-price-and-then-discount dance.

If you are required by your procurement framework to quote a public price range before a scoping call, contact us and we will provide a written budgetary range, in writing, signed by an authorized officer, with the assumptions clearly listed.

Request a written proposal

Get a written proposal.

A 30-minute scoping call. Five business days. Line-item proposal with assumptions and pricing-model options. No follow-up SDR cadence.

Request scoping call Download procurement kit