Reliability is not a feature. It is public service infrastructure.
CMS is positioned for municipalities that need secure access, tenant-isolated data, resilient cloud operations, and auditable workflows. Claims on this page require final security and compliance review before publication.
Discuss Security RequirementsTenant isolation
Municipal data boundaries are a core architecture requirement
Modern identity
Draft positioning includes Entra ID authentication and role-based access
Backup strategy
Point-in-time recovery and retention claims require verification before launch
Auditability
Critical user and system actions should be recorded for review
Security and reliability pillars
These pillars reflect the supplied product positioning and should be reviewed against actual architecture, policies, contracts, and controls before publication.
99.95% uptime SLA
Draft claim: enterprise Azure infrastructure with geo-redundant failover to keep municipal workflows available during peak demand.
Learn more →Row-level security
Draft claim: tenant-isolated data access so one municipality's records are separated from another municipality's records.
Learn more →SOC 2 Type II aligned architecture
Draft claim: encrypted data, audit logging, modern identity, and control design that needs formal review before public compliance language.
Learn more →Automated backups
Draft claim: point-in-time recovery with 30-day retention, designed to support resilience and recovery planning.
Learn more →Zero-downtime deployments
Draft claim: updates roll out without interrupting the everyday work of staff, inspectors, contractors, and residents.
Learn more →Operational continuity
Draft positioning: municipalities should be able to keep issuing permits while other providers recover from outages.
Learn more →Security review topics
Use the demo process to align CMS documentation with municipal IT, procurement, and legal review.
Bring your IT and procurement questions.
A serious municipal software conversation should include uptime, recovery, identity, audit logging, data ownership, retention, integrations, support, and procurement timing.
Request a Technical Demo