Cloudflare
Current platform infrastructureEdge and cloud infrastructure supporting our current development environments.
Portable architecture is a deliberate engineering direction. Provider support must be demonstrated through native validation, not assumed from a diagram.
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.
Edge and cloud infrastructure supporting our current development environments.
Containerized application hosting, PostgreSQL, object storage and enterprise infrastructure.
Planned containerized workloads, PostgreSQL and object storage through AWS provider adapters.
Long-term deployment models shaped by organizational requirements and operational responsibility.
Cloudflare supports Municipal Centre's current development environments and product work.
Containerized application hosting, PostgreSQL and private object storage are being validated. This is not a production certification.
Future provider support and operating models require engineering, validation and defined responsibilities.
Provider-neutral service boundaries keep core product behavior separate from infrastructure-specific implementations.
Containerized hosting is being validated for Azure. AWS container services are part of the planned deployment direction.
Native PostgreSQL behavior, including concurrent operations, forms part of portability validation rather than being inferred from emulated tests.
Storage adapters are designed to support private documents across providers. Native object storage authorization and access behavior require validation.
Adapters translate deployment and service operations into provider-specific APIs while preserving a consistent product boundary.
External services are connected through controlled integration points. Permissions and service availability remain deployment-specific.
The release direction packages code and associated requirements into artifacts that can be validated and promoted consistently.
Each environment retains appropriate configuration and credentials, separate from the release artifact and from other organizations.
The Console is being developed to coordinate provisioning, validation and deployment with clear progress and failure records.
Application and infrastructure health, logs and operational history support troubleshooting. Coverage evolves with each provider integration.
Web interfaces are designed for desktop, tablet and mobile use, with clear navigation and accessible controls.
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.
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.
Whether you're a municipality, professional association or technology partner, we'd like to hear from you.