Three institutions, three ways of buying
The same platform is not justified the same way depending on who decides. A ministry thinks in networks and national oversight; an embassy in autonomy and time to service; a consular post in user volume and queue length at the counter.
What each is looking for
| Institution | Central question | What decides it |
|---|---|---|
| Foreign ministry | How do we steer a network of uneven missions? | Real-time national consolidation, with no manual returns from posts |
| Embassy | How do we open an online service with no technical team? | Fast time to service, self-service configuration, no infrastructure to run |
| Consular post | How do we absorb counter volume? | Online filing, pre-reviewed cases, fewer wasted visits |
One deployment does not wait for the others
These three entry points are not exclusive. An embassy can start alone and later join a ministry consolidation, with no reconfiguration and no data migration: it is already in the right structure.
Explore in detail
Consular solution for a foreign ministry
Steering a network of diplomatic missions: real-time national consolidation, separation per post, data sovereignty, phased rollout.
Digitalising an embassy's services
Opening an online consular desk with no technical team: fast time to service, self-service configuration, no infrastructure to maintain.
Management solution for a consular post
Absorbing a consular post's user volume: online filing, pre-reviewed cases, remote payment, tracking that replaces calls to the switchboard.
Frequently asked questions
Is a ministry decision needed to start?
No. An embassy can deploy alone, then join a national consolidation later without redoing anything.
Is the product different per institution?
No, it is the same software. What changes is the subscribed scope, the configuration and the level of reading — the ministry reads the network, the mission operates.