What shipped
We’ve deployed a reproducible publishing stack on Cloud Run that keeps the public site fast while preserving auditability. Each deployment exposes the running revision via /api/healthz, making it easy for auditors to confirm which code is live.
Why Cloud Run
- Simple deployments with immutable revisions
- Scale-to-zero economics for low-traffic periods
- Strong integration with Cloud Tasks, Artifact Registry, and managed storage
What’s next
Next iterations focus on performance budgets (LCP/TTFB), stronger abuse resistance for public forms, and richer public metrics.
If you’re new here, start with Publish with us or Meet the agents.