Long-form writing on Canadian cloud infrastructure, the CLOUD Act, deploying without Git, and what it actually takes to build a software company in Canada — written by the founder.
Canner started as a deployment app for personal projects. Customers kept asking for more, and a year later it's a Canadian-owned AWS alternative — here's where it actually beats AWS, where it doesn't yet, and what's shipping next.
Canner's dedicated Postgres instance adds point-in-time recovery, pgvector and PostGIS, logical replication, live migration from another server and an encrypted off-site recovery archive, all hosted in Montreal.
How Canner runs logical replication for customers: physical replication closed, a one-database replication login, a WAL cap per slot, non-superuser apply, and an SSRF guard on the remote address.
We moved Canner's entire platform from virtualized VPS infrastructure to dedicated hardware overnight — and builds got dramatically faster.
What it actually takes to add passkey sign-in to an app: the two WebAuthn flows, and the four things that surprised us once the demo worked.
A layer-by-layer map of a fully Canadian-owned application stack — compute, database, storage, analytics, DNS, email, payments, CDN — with real vendor names for each, and an honest note on where the ecosystem is still thin.
One Google Safe Browsing flag took down our website, our ads, and our email at once — fixed in fifteen minutes, but restored only when Google decided.
Canner is now a native Astro 7 cache provider — the same Astro.cache.set() API you'd use on Netlify or Vercel, pointed at Canadian infrastructure — with draft mode and stale-while-revalidate built in.
Run SQL on a cron schedule against your own Postgres databases in Canada — read and write them by name, join across projects, and write results straight to your backend, with no external ETL tool.
Manage your Canadian-hosted projects from code — a documented REST API under /v1, an OpenAPI 3.1 spec, a --json CLI, and an MCP server with over thirty tools for AI agents.
Built a Python AI demo with Gradio or Streamlit? Deploy it to sovereign Canadian infrastructure in about 30 seconds — plus Go, Ruby, PHP, Rust, Java, and BoxLang. No Docker, no config.
In August 2025, Shared Services Canada asked the market for a fully sovereign public cloud — Canadian-owned, Canadian-controlled, beyond foreign-government access laws. Here's what that means and where Canner fits.
Quebec's Law 25 gets the headlines, but Ontario and most of Canada run on PIPEDA, with BC and Alberta on their own PIPA. The sovereignty case is the same coast to coast — and it's about ownership, not geography.
Built something with Cursor, Bolt, Grok, Claude, Lovable, or Replit? Get it hosted in Canada, on infrastructure that isn't subject to a foreign government's reach.
Agencies don't need to size a hosting plan around their worst-case client. Canner pools resources per account and lets you buy exactly what one client needs, dedicated Postgres included, no server to manage.
A Canadian AWS region doesn't make your hosting Canadian — if the provider is US-incorporated, the CLOUD Act applies wherever your data sits.
Futurpreneur, IRAP, SR&ED and Investissement Québec, with the terms stated plainly: what each one pays, what it requires first, and when it's worth your time.
A map of the Canadian-owned cloud infrastructure that exists in 2026: compute, PaaS, CDN, database, DNS, email — what's there and what's missing.
Selling software to the Government of Canada means meeting cloud security rules. A plain-language guide to the GC Cloud Guardrails and Protected B.