diff --git a/docs/deployment-architecture.md b/docs/deployment-architecture.md
index b2130c7b0..ce89858d4 100644
--- a/docs/deployment-architecture.md
+++ b/docs/deployment-architecture.md
@@ -35,12 +35,9 @@ Run the Next.js app as a **single long-lived container** (Node 24, image built
 from `Dockerfile`) on a managed container host **in Sydney, co-located with
 the Supabase project's ap-southeast-2 region**.
 
-Recommended host: **Fly.io (`syd` region)**, because it runs plain OCI images
-with per-app secrets, health checks, and rollback to previous releases, and it
-has a Sydney region. Google Cloud Run (`australia-southeast2`) is an equivalent
-alternative if a GCP account is preferred; the image is host-agnostic either
-way. Railway is _not_ suitable today (no Sydney region — cross-region RPC
-latency would multiply across the per-answer fan-out).
+Recommended host: any OCI-image host. Production runs on **Railway**; Google
+Cloud Run (`australia-southeast2`) is a Sydney-region alternative if lower
+answer latency matters. The image is host-agnostic.
 
 ### Why a long-lived container and not serverless (Vercel et al.)
 
diff --git a/docs/staging-setup.md b/docs/staging-setup.md
index f1ad55caa..717801463 100644
--- a/docs/staging-setup.md
+++ b/docs/staging-setup.md
@@ -51,9 +51,9 @@ those vars are unset.
 
 ## B. Staging app host (compute tier)
 
-Recommended host: **Fly.io `syd`** (Sydney region; no MCP available here, so
-this is an operator step). Google Cloud Run `australia-southeast2` is the
-equivalent. Railway is unsuitable — no Sydney region.
+Recommended host: any OCI-image host. Production runs on **Railway**; Google
+Cloud Run `australia-southeast2` is a Sydney-region alternative if lower
+answer latency matters. No MCP is available here, so this is an operator step.
 
 1. **Build the image** from the committed `Dockerfile`, passing the _staging_
    publishable key (it inlines into the client bundle):
@@ -110,6 +110,6 @@ equivalent. Railway is unsuitable — no Sydney region.
 ## What is operator-only (cannot be scripted here)
 
 - Creating the Supabase project (billable) and its DB password.
-- Opening the Fly.io/host account and setting the runtime secrets.
+- Opening the host account (e.g. Railway) and setting the runtime secrets.
 - Any change to the **production** project's settings (e.g. auth
   percentage-based connection allocation — see `docs/capacity-review.md` §3).