Platform Guides: Render & Leapcell

Deploying Go: Render & Leapcell

In 2026, Heroku is a distant memory. Modern PaaS (Platform as a Service) providers handle Go natively.

Render (render.com)

Render detects Go apps automatically.

  1. Push code to GitHub.
  2. Connect Repo to Render.
  3. Build Command: go build -o server ./cmd/server
  4. Start Command: ./server

Pros: Excellent free tier, managed Postgres/Redis, Private Networks.

Leapcell (leapcell.io)

Leapcell is designed for Serverless Go. Instead of running a container 24/7, Leapcell scales your Go binary to zero when not used, and spins it up in milliseconds (using Firecracker microVMs).

Difference from AWS Lambda: * AWS Lambda forces you to write specific handlers. * Leapcell runs standard net/http servers. You just deploy your binary.

Config: Usually configured via a leapcell.yaml.

runtime: go
entrypoint: ./server

VPS Deployment (Systemd)

If you run on a bare Linux VPS (DigitalOcean/Hetzner) for $5/mo:

  1. SCP the binary to the server.
  2. Create a systemd unit: /etc/systemd/system/myapp.service
[Unit]
Description=My Go App
After=network.target

[Service]
User=appuser
ExecStart=/usr/local/bin/myapp
Restart=always
EnvironmentFile=/etc/myapp.env

[Install]
WantedBy=multi-user.target
  1. systemctl enable --now myapp

This is the “Old Reliable” way. Cheap, robust, but manual.