Render is the modern, tidier take on Heroku — clean panel, sensible pricing tiers, a real free tier for static sites. This piece isn't here to diminish it. But most people searching "render alternative" just learned two things: the free Postgres is deleted after 90 days and free services sleep. Let's unpack both, and the rest.
Where Render Is Genuinely Good
- Static sites: a real free tier + global CDN — still one of the best free options for portfolios, docs and landing pages.
- Clean DX: less magic than Heroku, a more readable pipeline, Infrastructure-as-Code via render.yaml.
- Preview environments: per-PR environments that actually work.
- Cron jobs + background workers: built in, no separate product to buy.
The 90-Day Postgres Trap
Render's free Postgres looks generous — until the small print: after 90 days the instance expires and is deleted with its data. The "free database" is really a "90-day trial database". People have learned this on day 91 with customer data inside — Render does send warning emails, but anyone who misses the inbox loses the data.
Paid Postgres starts reasonably (~$6/mo) but the ladder steepens fast with disk/RAM: $20-40+/mo arrives quickly.
Sleeping Services and the Instance Ladder
| Render tier | Price (mo) | What you get |
|---|---|---|
| Free web service | $0 | Sleeps after 15 idle minutes — cold starts up to 50s; monthly hour quota |
| Starter instance | ~$7/instance | 512MB RAM — no sleep but small |
| Standard instance | ~$25/instance | 2GB — real production |
| Postgres (paid) | ~$6-40+/mo | Ladder by disk+RAM |
| Worker/cron | Separate instance | Each billed individually |
An always-on web + worker + Postgres combination starts at ~$20/mo minimum — and every instance bills in USD. For teams in Turkey, FX risk is constant.
The Hidden Cost of Sleep Mode
A free service sleeps after 15 idle minutes; cold starts can hit 50 seconds. It's not only the first visitor who waits — search engine crawlers wait too. Uptime-monitor pings are the common workaround, but they eat the quota and Render treats it as a gray area. The starter tier doesn't sleep — so "staying awake" is already paid.
Two Extra Factors for Teams Serving Turkey
- Regions: Render runs in Oregon, Frankfurt, Ohio, Singapore — no Turkey. Frankfurt → Istanbul is ~40-60ms RTT; Turkey-hosted is ~5-10ms.
- KVKK: once personal data leaves the country, the transfer machinery (standard contracts + notification) starts — covered in our article. Data in Turkey means the machinery never runs.
Render vs Skyversal — The Honest Table
| Render | Skyversal | |
|---|---|---|
| Static sites | Free + CDN — their win | Included in paid plans |
| Web service sleep | 15 min on free | None |
| Free Postgres | Deleted after 90 days | Managed, permanent, backups + PITR |
| Worker/cron | Separate instance billing | Included in the same project |
| render.yaml / IaC | Strong — infra lives in code | Panel + API + CLI |
| Regions | US / EU / Singapore | Turkey |
| Billing currency | USD | TRY — fixed |
| Deploy experience | git push + blueprint | git push, container build |
Where Render wins: free static sites + CDN and infrastructure-as-code via render.yaml. For portfolios and JAMstack sites Render can still be the right pick. Where we win: Postgres that doesn't expire, services that never sleep, worker/cron inside one project, Turkey region, TRY pricing.
Who Should Stay on Render, Who Should Move
Stay on Render:
- You host static sites/portfolios — the free tier is real
- Your customers are in US/EU and USD billing is fine
- You built your flow around render.yaml IaC
Move:
- You keep real data on the free Postgres — don't see day 91
- Sleeping-service cold starts hurt users
- Web + worker + DB totals inflate in USD
- You serve users in Turkey — latency and KVKK are wins
Migration Steps from Render
- Connect the repo: link your repository — take the build/start commands from render.yaml into the pipeline.
- Env vars: paste the Render env group output into the panel.
- Map services: web service → project, worker → project process, cron → scheduled task, Postgres → managed database.
- Move data — before day 90: if you're on free Postgres, pg_dump first.
- DNS: attach the domain; SSL is automatic.
FAQ
Does Render's free Postgres really get deleted?
Yes — free Postgres instances expire after 90 days and are removed with their data. Warning emails go out, but anyone who misses them loses it. Production data needs paid Postgres or a managed DB.
Why does my free service load slowly?
After 15 idle minutes it sleeps; cold starts can reach 50 seconds. Starter instances don't sleep.
What happens to my render.yaml?
The commands inside (build, start, env) move directly into project settings. Instead of blueprint logic, services + workers + cron are defined together in one project.
Is there a better free tier than Render for static sites?
Honest answer: for static + CDN, Render's free tier is still strong. The comparison changes on dynamic apps and databases — that's where we win.