The database is where a municipality's register actually lives. We run managed databases behind the systems we deliver, keep them backed up, and make sure the history of a record can be reconstructed when somebody asks.
Automated backups on a retention window, point in time recovery, and restores we have tested rather than assumed.
Who changed an indigent status, when, and what it was before. A municipal audit asks this, and the answer has to come out of the system.
One municipality cannot read another municipality’s register. Tenant separation is enforced in the data layer, not just in the interface.
Reports and exports run without slowing the people capturing applications at a counter.
Your register is yours. Exports come out in formats your finance system and your auditors can open.
Databases holding citizen information run in the AWS Cape Town region, as POPIA and municipal policy require.
Database services sit underneath the products rather than being sold on their own.
You do not buy or size a database. It is part of what we run for you.
Documented APIs so the finance or billing system you already run can read what it needs.
If you leave, you leave with your data in a usable form.