Can a prompt replace Render?

Build the same single-server PaaS described in this catalogue's Railway entry — Render's actual shape (accept a repo or image, build with Docker, route with automatic HTTPS, health-check before swapping traffic) is close enough to Railway's that reimplementing it as a second, differently-designed system would be dishonest busywork. Use Docker Compose with Caddy as the reverse proxy for automatic Let's Encrypt TLS. Build a small control-plane service that watches for new commits or manual redeploy triggers, builds the image, health-checks the new container before routing traffic to it with a blue-green swap, and keeps the last few images for instant rollback. Store environment variables encrypted at rest, injected at container start. Stream bounded build and runtime logs per app through a minimal dashboard, with restart, rollback, and redeploy actions. Add a basic host-level disk and memory alert. Do not build multi-region infrastructure, autoscaling, or managed database provisioning — this runs on one server, and that limitation belongs in the README, not hidden. Requires a server (a modest VPS is enough for a few small apps) and a domain pointed at it.