Technical Specifications
Technical Architecture
Civic Court / POA is built on a modern microservices architecture designed for Ontario municipalities — containerized, API-driven, and fully source-code-licensed so your IT team owns the entire stack.
99.9%
Uptime SLA
5,000+
Concurrent Users
<200ms
API Response
11
Platform Modules
Architecture Overview
Civic Court / POA uses a containerized microservices architecture with React/Next.js front-end, Node.js/TypeScript API layer, PostgreSQL database, and Redis caching. Each court function — charge intake, scheduling, proceedings, fine management, and reporting — is an independent service that scales horizontally. The architecture is designed for municipal IT teams to understand, maintain, and extend using mainstream technologies with large developer communities. Full source code ownership means you control the deployment, the infrastructure, and every line of code.
Platform Modules
Court / POA Microservices
Each court function is an independent, deployable service with its own API surface. Services communicate via internal REST APIs and an event bus for asynchronous coordination. This separation ensures that changes to fine management don't affect court scheduling, and ICON integration can be updated independently of the defendant portal.
Total Modules
11
Protocol
REST / gRPC
Bus
Async Events
Container
Kubernetes
Database
PostgreSQL 16
Specifications
Technical Details
Browse specifications by category. All values reflect current production configuration.
Framework
React 18 + Next.js 14
Language
TypeScript 5.x (strict mode)
State
Zustand + React Query
Styling
Tailwind CSS + Radix UI
Accessibility
WCAG 2.1 AA · AODA compliant
Internationalization
i18next — English + French
Uptime
99.9% uptime SLA — maintenance windows scheduled outside court hours Availability SLA
Civic Court / POA is engineered for high availability — critical for court operations where downtime disrupts court sessions, delays proceedings, and impacts defendant access to services.
99.953%
30-Day Avg
1
Incidents
3× DC
Redundancy
< 15min
Recovery
30-Day Uptime History
All Systems Operational
Deployment
Deployment Options
Choose the deployment model that fits your municipality's IT strategy — from managed cloud to fully self-hosted with complete source code control.
Managed Cloud (Recommended) — hosted on Canadian infrastructure (Toronto + Montréal) with 99.9% SLA, automated backups, patching, and monitoring. Full source code licence retained. Most municipalities choose this option.
Self-Hosted (Municipal Infrastructure) — deploy on your own servers or private cloud. Full source code delivered with Docker/Kubernetes templates, sizing guides, and architecture docs. Complete control over deployment and data.
Hybrid (Self-Hosted + Managed DR) — production on municipal infrastructure with disaster recovery on managed Canadian cloud (Montréal). Automated replication, annual failover testing, and flexible migration path.