← All posts

Kilter Goes Global: EU and USA Regions Are Now Open

Paddy O'Cybear3 min read
announcementplatformkiltersovereignty

Short version: Paddington.io is now in three regions. Our EU and USA regions are open as of today, joining the Canadian region where the platform was born.

  • Canada — ca-central. The original Miniscaler instance — bare metal, with cloud provisioning as needed.
  • USA — us-east. Hetzner Cloud — US data residency for US customers.
  • EU — eu-west. Hetzner Cloud — EU data residency, GDPR-friendly by design.

You pick a region when your trial is provisioned; existing customers can request a second region from the portal.

What a "region" means here

Not an availability-zone marketing diagram — an independent Miniscaler instance. Each region runs its own cluster and its own data plane on the same canonical kilter stack: same catalog, same charts, same GitOps reconcilers, same Ory identity pattern. Your app is pinned to the region you choose, and its data — Postgres, objects, queues, audit — lives in that region, full stop. There is no cross-region replication of your data unless you ask for it.

That independence is deliberate. Regions that share nothing can't leak into each other, fail into each other, or quietly move your data somewhere a regulator would frown at. The three-region topology is documented on the Miniscalers page.

Regions are the smallest part of the answer

"Where can my apps live?" has never had a one-vendor answer on this platform, and going global doesn't change that. The full menu:

  1. A Paddington region — Canada, USA, or EU. Managed, metered at cost + 35%, running the open stack.
  2. Any Miniscaler — independent providers running the same kilter platform. Same manifests, same portability. Moving is a migration, not a rewrite.
  3. On-prem kilter — install the platform on your own hardware. The same kilter up-to-production experience, inside your own walls. This is the sovereign endgame for regulated and air-gapped environments.
  4. Your existing Kubernetes, natively — you don't even need kilter running in production. kilter package transmutes a provisioned environment into an operator-free bundle: plain manifests, materialized credentials, images pinned by digest, opened as a pull request against your own GitOps repo with an ArgoCD Application — reconciled by your ArgoCD, behind your RBAC, with nothing of ours in the change-control boundary. That mechanism is walked in detail in GitOps Is the Control Plane and Building an Inner-Enterprise Loop.

Notice what that list does to the usual cloud-region announcement. When a hyperscaler opens a region, it's a bigger net. When a sovereign platform opens a region, it's a bigger menu — because every option on it, including the ones that pay us nothing, keeps working. Our regions have to win your workloads on merit, every month.

Why this ordering

We opened Canada first because that's where we live. We opened the EU and the USA next because data residency is the first question every serious prospect asks — and "your data stays in your region, on an independent instance, on an open stack you could take with you" is a better answer than any compliance PDF.

The pricing is identical in every region. The stack is identical in every region. The exit is identical in every region. That's the point.

Where to go next

  1. See the three-region topology on the Miniscalers page.
  2. Read GitOps Is the Control Plane — how kilter package lands your app in your own ArgoCD.
  3. Start your free trial — and pick your region.