How to Deploy Your First App on Render in 15 Minutes

October 30, 2026

Render is a hosting platform that builds and deploys your app directly from a Git repository. You connect GitHub, point at a branch, and get a public HTTPS URL on every push — no Dockerfile required for Node, Python, Ruby, Go or Elixir.

The whole path from empty account to live URL takes about 15 minutes if your repo runs locally already.

What does Render do that Heroku did?

Render is the closest thing to the old Heroku workflow: push to Git, get a running web service. The differences are a free tier for static sites and web services, native Docker support, and persistent disks you pay for separately.

Render is a company (Render Services, Inc.), the platform runs on AWS and GCP regions, and services are defined either in the dashboard or in a render.yaml blueprint file.

How do you deploy in practice?

  1. Sign up at render.com with your GitHub account.
  2. Click New → Web Service, pick the repository, then the branch.
  3. Render detects the language. Confirm the build command (npm install) and start command (npm start).
  4. Choose an instance type. Free works for testing; Starter at $7/month avoids sleeping.
  5. Add environment variables under the Environment tab — do this before the first deploy, not after.
  6. Click Create Web Service and watch the log stream.

The build log is where you will spend most of your time. Failures are usually a missing package.json lockfile, a start script that binds to the wrong port, or a build that needs a newer Node version.

What port should your app bind to?

Whatever process.env.PORT says. Render assigns a port at runtime and routes to it. Hardcoding 3000 works locally and fails in production, which is the single most common first-deploy error.

In Express: app.listen(process.env.PORT || 3000). In FastAPI: uvicorn main:app --host 0.0.0.0 --port $PORT. Binding to 127.0.0.1 instead of 0.0.0.0 also breaks health checks.

Does the free tier really sleep?

The answer is yes, after 15 minutes without traffic. The next request triggers a cold start that takes 30-60 seconds on a Node service, longer on a JVM app.

That is not a bug, it is the deal. Free instances also get 512 MB RAM and 0.1 CPU, which is fine for a demo and painful for anything doing image work.

Related free-tier limits worth knowing: 750 instance hours per month per workspace, 100 GB bandwidth, and free Postgres databases that expire 30 days after creation unless you upgrade. That last one catches people who assume their demo database is permanent.

How do you add a database?

Under New → Postgres, pick a plan, then copy the internal connection string into your service’s environment variables. Use the internal URL, not the external one — internal traffic stays inside the region and costs nothing.

Render’s Postgres supports point-in-time recovery on paid plans. Free databases do not, and they are deleted 30 days out. Do not run a real product on a free database you forgot about.

What about custom domains and TLS?

Add the domain under Settings → Custom Domains, then create a CNAME (or A records for the apex) at your DNS provider. Render issues a Let’s Encrypt certificate automatically and renews it.

Propagation usually finishes in under 10 minutes with Cloudflare DNS, and up to an hour elsewhere. If you use Cloudflare, set the record to DNS-only during verification or the ACME challenge will loop.

Honest limits

Render is not the cheapest option for a single small box. A $5 VPS from Hetzner or DigitalOcean beats it on raw specs. What you are paying for is deploys on push, managed TLS, and zero server maintenance — which is worth it the moment you have more than one service.

Skip Render if you need GPU inference, have long-running background jobs over 12 hours, or need sub-100ms cold starts on a free budget.

Key Takeaways

  • Connect a Git repo, confirm build and start commands, deploy — about 15 minutes total.
  • Bind to 0.0.0.0 and process.env.PORT, never a hardcoded port.
  • Free web services sleep after 15 minutes idle; cold start is 30-60 seconds.
  • Free Postgres databases expire after 30 days; paid plans add point-in-time recovery.
  • Paid plans start at $7/month for a Starter instance with no sleeping.
Tags: