Technical Specifications
Technical Overview
Infrastructure, architecture, and operational specifications for IT Directors and technical evaluation teams. Civic Elections is designed for the performance, reliability, and security standards expected by Canadian public sector election systems. Delivered as a full source code licence — your municipality has complete access to the codebase.
99.9%
Uptime SLA
5,000+
Concurrent Users
<200ms
API Response
6
Platform Modules
Architecture Overview
Civic Elections is built on a microservices architecture with a Next.js web client, API gateway, and PostgreSQL database engine. Each functional domain — voters list management, candidate nominations, voting logistics, tabulation & results, campaign finance, analytics, and public portals — operates as an independently deployable microservice. This enables municipalities to scale individual components based on demand (especially results publication on election night), apply updates without system-wide downtime, and achieve fault isolation so that an issue in one service does not affect others. Each municipal tenant operates in a logically isolated environment with dedicated database schemas. The platform is deployed on containerized infrastructure (Kubernetes) across redundant Canadian data centres with automated failover. Full source code licence means your IT team can inspect, modify, and extend any component.
Platform Modules
Microservices Architecture
Civic Elections decomposes election administration into independently deployable microservices. Each service owns its domain logic, data store, and API contract — enabling independent scaling, fault isolation, and zero-downtime deployments. Services communicate via asynchronous event bus and synchronous REST/gRPC calls through a centralized API gateway.
Total Modules
6
Protocol
REST / gRPC
Bus
Async Events
Container
Kubernetes
Database
PostgreSQL 16
Specifications
Technical Details
Browse specifications by category. All values reflect current production configuration.
Elector lookup response time
< 200 ms across 500 K+ elector records
Results publication latency
< 5 seconds from poll report to public dashboard
Election night dashboard capacity
50 K+ concurrent viewers with CDN
MPAC import throughput
100 K elector records in < 10 minutes
Voter card generation
100 K cards rendered in < 30 minutes
Uptime
99.99% (election period) / 99.9% (non-election) Availability SLA
Election systems demand extraordinary availability during critical periods — especially election night. The platform employs a tiered availability model: always-on for administration, high-availability for voting operations, and election-night-grade for results publication with automatic scaling, CDN distribution, and warm standby failover.
99.953%
30-Day Avg
1
Incidents
3× DC
Redundancy
< 15min
Recovery
30-Day Uptime History
All Systems Operational
Deployment
Deployment Models
Flexible deployment options for Canadian municipalities — from fully on-premises for maximum control to managed hosting with Canadian data sovereignty guarantees. Every model includes full source code access and election-cycle deployment support.
On-Premises — full election platform deployed within municipal data centres. Complete infrastructure control, no external dependencies during voting, deployment automation via Ansible and Docker Compose
Managed Hosting (Canadian Cloud) — Civic-managed deployment in Canadian cloud infrastructure (Azure Canada, AWS Canada). Auto-scaling for election night, 24/7 operations support, SLA: 99.99% during election period
Hybrid — core admin (voters list, nominations, tabulators) on-premises with results publication and public portals in managed Canadian cloud. Encrypted VPN between environments, municipality decides service placement