Try a Go HTTP service on a free instance with a public URL and managed TLS. Use the standard library or your preferred web framework.
Each instance has a fixed monthly price, prorated by the second.
Capability | Render | |||
|---|---|---|---|---|
How Go runs | Native Go web service or Docker | Long-running container | Web dyno | Fly Machine built from a Dockerfile |
Free tier | 750 free hours/month. Spins down after 15 min idle | $5 trial for 30 days, then $1/month credit | None. Eco: $5/month for 1,000 hours | No free tier. Personal bills under $5 waived |
Always-on, 2 GB | $25/month (1 CPU) | Up to $40/month at full use (1 vCPU) | $250/month (Performance-M, 2.5 GB dedicated) | $13.39/month shared CPU, $33 dedicated |
Managed Postgres and Redis | Postgres from $6 with PITR, plus Key Value | Maintained databases. HA and Postgres PITR opt-in | Postgres and Key-Value. No rollback on Essential | Managed Postgres from $38, HA included. Upstash Redis |
Background workers | Workers and cron jobs | Workers and cron jobs | Worker dynos and Scheduler | Process groups. Cron via Supercronic |
WebSockets | Yes, no maximum duration | Yes, no maximum duration | Yes, closes after 55s idle | Yes, through Fly Proxy |
Autoscaling | Scales on CPU or memory, Pro plan and up | Manual replicas. Vertical up to plan limits | Performance, Private and Shield dynos only | Proxy autostart, or a self-run autoscaler |
Competitor details as of November 2026. Instance prices are compute only. Fly.io prices are for US East.
Build Go on the native runtime or in Docker. Define your services and databases in one render.yaml Blueprint.
Set the build command your Go project needs. Render runs the binary from your start command after a successful build.
Connect through your PostgreSQL driver using the database’s internal connection details. Keep the app and database in the same workspace and region.
Run an internal Go API as a private service when it should have no public URL. Private-service compute is billed separately.
Configure an HTTP health check for application readiness. Handle graceful shutdown and in-flight connections in your Go server.
Run continuous queue consumers as background workers and periodic jobs as cron jobs. Give each task its own service configuration and compute.
Add instances to spread web traffic across your Go service. Autoscaling is available on Pro and up, and each instance is billed separately.
Pick a GitHub, GitLab, or Bitbucket repo and branch.


Choose Go, set your build and start commands, and add environment variables. Have the server listen on 0.0.0.0 and the port in PORT.
Render builds your app and publishes its URL. Every later commit to your branch deploys automatically, or only after CI checks pass.

