Government · 2024
Govexa
A public-scale digital system modernised without ever taking the service offline, accessible by default and built to outlast the team that shipped it.
Timeline
Phased over several months
Team
9 engineers, 1 product manager, 2 devops
Services
The situation
Govexa was carrying a brittle legacy system that real people depended on every day. It could not simply be switched off and rebuilt over a weekend. Any modernisation had to happen while the service kept running underneath it.
On top of that, a public system has to work for everyone, on any device, and stand up to genuine scrutiny on security and accessibility. The bar is higher than most products ever face.
A few choices that mattered.
The decisions that shaped the build, and why we made them.
One slice at a time
We modernised in slices, routing one piece of traffic at a time to the new system and proving each slice live before moving the next.
Accessible and secure by default
We built to public standards from the start, so accessibility and security were foundations rather than a final audit scramble.
Built to be handed over
We documented decisions and kept the system clear, so the in-house team could operate and extend it long after we finished.
What Zeto owned.
The parts of this engagement that were ours end to end, not handed off between vendors.
- The phased migration, one slice of traffic at a time
- Accessibility and security built to public standards from the start
- The cloud infrastructure underneath the service
- Documentation and runbooks so the in-house team could carry it on
What went into production.
- A modernised public-scale system migrated with zero downtime
- Accessible, multi-device interfaces built for every citizen
- Secure, compliant cloud infrastructure
- Documentation and runbooks for the in-house team
What it added up to.
Phased over several months, with zero downtime across the entire migration.
downtime in migration
accessible by default
scalable and documented
scale
In plain words
The old system was retired one slice at a time with no interruption to the service people relied on. What replaced it is accessible by default, secure under scrutiny, and documented well enough that the in-house team carries it forward without us.
Let's build something that compounds.
Bring your objective and your constraints. We will come back with a focused execution path, and we stay accountable to the outcome.