Provider adapter framework
TypeScript · API design · SDKs
Define a stable contract for authentication, provisioning, billing data, health and lifecycle actions while allowing each provider API to stay different underneath.
Help build the layer between Canadian companies andCanadian infrastructure.
The directory makes Canadian providers easier to find. The next step is a unified interface that connects to those providers through modular API adapters—so a company can change the provider behind a service without rebuilding how its team works.
We are defining the contributor pathway now. Repository, licence and governance decisions remain open.
Interface concept
- Overview
- Domains
- Hosting
- Storage
- AI & compute
- Security
Search services and providers
CAYour Canadian stack
Services from independent providers, managed together.
6
Domains
4
Sites
12
Mailboxes
2 TB
Storage
Quick actions
Register domain
Deploy site
Create mailbox
Add provider
One interface. Replaceable providers underneath.
KanataCloud would not become the infrastructure provider. It would become the consistent operating layer: one place to see services, take common actions and understand cost and health while independent Canadian companies continue to run the underlying systems.
Canadian company
One workspace and one operating model.
KanataCloud core
Shared concepts, policy and orchestration.
Provider modules
Independent adapters for each provider API.
The architecture is a proposal. Contributor review will shape the security model, adapter contract and first production integrations.
Modularity turns a directory into practical leverage.
A common interface lowers the cost of trying a Canadian provider. Teams gain choice without accepting a new dashboard and workflow for every service, while providers gain a shared route into organizations that need more than one part of their stack.
Domains & DNS
Registration, records, nameservers, renewals and transfers.
Hosting & compute
Deployments, virtual machines, health, scaling and usage.
Storage & backup
S3-compatible storage, snapshots, retention and recovery.
Email & collaboration
Mailboxes, transactional delivery and team services.
Security & delivery
Certificates, firewalls, CDN controls and incident state.
AI & data
Canadian inference, model access and privacy-conscious data services.
Software engineers can shape the foundation.
This is early enough for contributors to influence the contracts and boundaries that will be expensive to change later. We need people who care about dependable systems, clear product behaviour and Canadian digital capacity.
Identity and secrets
Security · IAM · applied cryptography
Design tenant isolation, OAuth and API-key flows, encrypted credential storage, audit trails and least-privilege access from the beginning.
Unified control plane
React · product engineering · accessibility
Turn inconsistent provider concepts into a coherent workspace without hiding differences that matter to cost, reliability or data residency.
Reliability and operations
Distributed systems · queues · observability
Build normalized events, job handling, retries, health reporting, observability and recovery for actions that cross independent provider systems.
The stack we have—and the decisions still open.
The public product already provides a typed, containerized base. The production orchestration layer should be chosen through threat modelling, provider discovery and contributor review rather than a speculative architecture diagram.
- Interface
- Next.js 16, React 19, TypeScript and Tailwind CSS.
- Delivery
- Docker deployment with a CDN and edge-security layer.
- Integration boundary
- Proposed typed adapters over provider REST APIs and SDKs.
- Open choices
- Identity, secrets, persistence, queues, observability, licence and governance.
Useful first. Sustainable without compromising the map.
Infrastructure software needs a durable operating model. Several paths are worth testing, but any commercial relationship must be disclosed and must never buy directory placement or ranking.
Provider reseller programmes
Use wholesale or reseller APIs where they improve provisioning and support, with the commercial relationship made visible.
Paid operational modules
Charge for optional team controls, policy, audit history, consolidated reporting or managed migration while keeping discovery public.
Provider-funded integrations
Let providers fund adapter development without buying prominence, exclusivity or a favourable comparison.
Support and implementation
Offer paid onboarding and integration help to organizations that need a guided move across several services.
Help turn Canadian infrastructure into a system companies can use together.
Tell us what you build, which workstream you care about and what a credible contributor programme should look like. Until the public repository opens, this page is the project brief.