Billing models
We do not publish a price list: a network of three consulates and a ministry of forty missions are not buying the same thing. We do publish how the price is built, because a budget is prepared before a quote exists.
Four billing bases
One is chosen per contract. The choice mostly comes down to predictability: a ministry building a multi-year budget does not want an invoice indexed on activity it does not control.
| Basis | Principle | Suits when |
|---|---|---|
| Per mission | A subscription per deployed post | The network is stable and the budget must be predictable |
| Per enrolled national | Indexed on register size | The diaspora's size is unknown at the outset |
| Per credential produced | Indexed on cards and passports | Issuance activity is the dominant item |
| Licence | Right of use, typically for on-premise | The state operates the platform itself |
What is included
- The subscribed modules, with no usage cap on the functions they cover
- Platform upgrades for the term of the contract
- Initial configuration: document catalogue, prices, card artwork, mission branding
- Support for officers during rollout
What is optional or passed through
- Modules not subscribed to, which can be enabled mission by mission mid-contract
- Third-party costs: online payment, messaging, dedicated hosting
- Card production consumables, where production is distributed to the posts
- Mission-specific development, quoted separately
The cost worth comparing
The real competition in this market is not another product: it is bespoke development handed to a local integrator or to diaspora engineers. Against an annual licence, bespoke often looks cheaper.
The honest comparison is total cost over five years: initial development, then corrective maintenance, regulatory changes, security updates, and dependence on the team that wrote it. That is the ground on which we ask to be assessed, not entry price.
Frequently asked questions
Why is there no published price list?
Because the scopes are not comparable: an isolated consulate and a ministry network of forty missions are not buying the same product. Publishing one price would mean publishing a false one for one of them.
Can we start small?
Yes. Rollout goes mission by mission and module by module, starting from a pilot post. The scope then extends without redoing the configuration already in place.
Are online payment fees included?
No, those belong to the payment provider. They are shown separately to the user at payment time, and the mission's share is distinguished in the ledger.
What does an extra mission cost?
It depends on the basis chosen. On per-mission billing, adding one is one more subscription; there is no new instance to install and no extra software version to maintain.