diff --git a/docs/changelog.d/+fly-deploy-immediate-strategy.infra.md b/docs/changelog.d/+fly-deploy-immediate-strategy.infra.md
new file mode 100644
index 0000000..205bd6a
--- /dev/null
+++ b/docs/changelog.d/+fly-deploy-immediate-strategy.infra.md
@@ -0,0 +1 @@
+Switch the Fly proxy deploy strategy from `bluegreen` to `immediate` in `fly/fly.toml`. With a single proxy machine, bluegreen offers little benefit — the green machine routinely failed to reach "started" inside Fly's default 5-minute deploy timeout (the cold-start sequence of `tailscaled` → `tailscale up` → wait-for-MagicDNS → nginx startup eats most of the budget), and the failed deploys would roll back. `immediate` replaces the machine in place with a brief downtime (~5–10s) but actually completes.
diff --git a/fly/fly.toml b/fly/fly.toml
index 11aac9c..6ccf29d 100644
--- a/fly/fly.toml
+++ b/fly/fly.toml
@@ -7,7 +7,7 @@ primary_region = "sjc"
 memory = "512mb"
 
 [deploy]
-strategy = "bluegreen"
+strategy = "immediate"
 
 [http_service]
 internal_port = 8080