Municipal Centre
TECHNOLOGY

Modern Architecture. Practical Technology.

Portable architecture is a deliberate engineering direction. Provider support must be demonstrated through native validation, not assumed from a diagram.

A Product Architecture With Room to Evolve.

Our application services are being separated from provider-specific runtime, database and storage implementations. This supports a more flexible deployment path as the products mature.

Municipal HubAssociation CentreMunicipal Centre Console
Provider-Neutral Application ServicesApplication logic · Service boundaries · Provider adapters
CloudflareCurrent platform infrastructure
Microsoft AzurePortability validation underway
Amazon Web ServicesPlanned deployment target
Runtime · Database · Object Storage · Identity · Monitoring
Implemented

Current Development Infrastructure

Cloudflare supports Municipal Centre's current development environments and product work.

Under Validation

Native Azure Portability

Containerized application hosting, PostgreSQL and private object storage are being validated. This is not a production certification.

Planned

AWS & Customer-managed Models

Future provider support and operating models require engineering, validation and defined responsibilities.

ENGINEERING DIRECTION

Connected Services. Explicit Boundaries.

Portable Application Architecture

Provider-neutral service boundaries keep core product behavior separate from infrastructure-specific implementations.

Containerized Runtime

Containerized hosting is being validated for Azure. AWS container services are part of the planned deployment direction.

PostgreSQL Compatibility

Native PostgreSQL behavior, including concurrent operations, forms part of portability validation rather than being inferred from emulated tests.

Object Storage Abstraction

Storage adapters are designed to support private documents across providers. Native object storage authorization and access behavior require validation.

Cloud-provider Adapters

Adapters translate deployment and service operations into provider-specific APIs while preserving a consistent product boundary.

API Integrations

External services are connected through controlled integration points. Permissions and service availability remain deployment-specific.

Immutable Release Artifacts

The release direction packages code and associated requirements into artifacts that can be validated and promoted consistently.

Environment Configuration

Each environment retains appropriate configuration and credentials, separate from the release artifact and from other organizations.

Deployment Automation

The Console is being developed to coordinate provisioning, validation and deployment with clear progress and failure records.

Observability

Application and infrastructure health, logs and operational history support troubleshooting. Coverage evolves with each provider integration.

Responsive Web Architecture

Web interfaces are designed for desktop, tablet and mobile use, with clear navigation and accessible controls.

The AWS Deployment Target.

AWS support is planned. The proposed service map includes containerized workloads with ECR and ECS/Fargate, Amazon RDS for PostgreSQL, Amazon S3, IAM and CloudWatch.

Final service choices, regions, validation and operational controls will be determined during implementation. No AWS production support or partnership is claimed.

Canadian Deployment Considerations.

Region selection, storage location, provider permissions and backup arrangements need to be evaluated against each organization's requirements.

Portability does not automatically establish residency, compliance or equivalent behavior across providers. These must be verified for the selected environment.

READY TO WORK TOGETHER?

Let's Build Better Digital Infrastructure for Public Service.

Whether you're a municipality, professional association or technology partner, we'd like to hear from you.