The application servers behind the systems we deliver. We size them to the workload, keep them patched, and scale them when a deadline puts a whole municipality on the system at once.
A municipality of two thousand households does not need what a metro needs. We start from your register size and transaction volume rather than a tier chart.
Indigent registration and billing runs are spiky by nature. Capacity goes up for the period that needs it and comes back down afterwards.
Operating system and runtime updates are ours to apply, on a schedule agreed with you rather than in the middle of a working day.
Releases are versioned and a rollback is one step, so a bad deploy is an inconvenience rather than an outage you sit through.
Each municipality or business gets its own data separation, so one client cannot see another. Auditors ask about this first.
We watch error rates and response times on the systems we run and act on them, rather than waiting for you to report that something is slow.
Compute is part of how we run a system for you. We do not sell raw instances by the hour.
Hosting is included in the monthly price of the product rather than metered separately.
Anything holding citizen data runs in AWS Cape Town. See cloud services for why.
Your data is exportable. We would rather keep you because the system works than because moving is painful.