Blog · Alternatives

Best Render alternatives in 2026: when a price per service adds up

By the Pethost team · 30 September 2026 · Updated 5 October 2026 · 10 min read

You started on Render with one web service at $7 a month. Then came a Postgres, a worker and two more apps, each a line on the bill: $34.75 a month in October 2026. The best Render alternatives are of three kinds: platforms that price each service too, platforms that bill by use, and a machine at a flat price. Pethost is the third: €9.99 a month for 2 vCPU and 3 GB, which holds all five.

Render pricing in 2026: a web service, Postgres and the free tier

Render's Hobby workspace is $0. What you pay for is each instance: a web service, a private service or a background worker is $7 a month with 512 MB, $25 with 2 GB and $85 with 4 GB. A managed Postgres starts at $6 for 256 MB, a Key Value store at $10. Railway vs Render vs Fly.io pricing has every plan.

How the Render bill grows from one service to six

Not in these sums: traffic past the 5 GB a Hobby workspace includes is $0.15 a gigabyte, so 10 GB make the fifth row $34.75. HTTP request logs come with the Pro workspace: $25 a month more.

Render's free tier: a web service that sleeps, a Postgres that expires

A free web service spins down after “15 minutes without receiving any inbound traffic” and “takes about one minute” to wake. A free Postgres expires “30 days after creation”, and a worker has no free instance. Pethost has no free tier: €9.99 rents a real machine, and nothing on it sleeps. Always-on hosting compared has the other hosts' rules.

What changed in April 2026

On 23 April 2026 flat workspace plans replaced the plans per member. Compute prices stayed, and the included traffic shrank: “The new Hobby and Pro plans include less bandwidth than their legacy counterparts”. A short Hacker News thread read it as a price rise.

What Render does well

Render is built for a team's production app: a managed Postgres with point-in-time recovery, read replicas and high availability, instances up to 12 CPU and 96 GB, and autoscaling and preview environments on its paid workspace plans. A paid instance never sleeps, and its price is fixed.

The best Render alternatives, in three kinds

A PaaS comparison needs one workload. Ours has five parts: three always-on web services of 512 MB, a worker, a Postgres, and 10 GB of outgoing traffic a month.

Railway's sum is memory only, on our assumption of 0.5 GB for each service and 0.25 GB for Postgres: each 0.1 vCPU a service uses adds $2 a month. Fly.io's are Ashburn prices; Frankfurt is 15.4% dearer.

Heroku, DigitalOcean App Platform and Northflank: a price per service again

These three charge as Render does, so the bill grows the same way. Heroku has been in a “sustaining engineering model” since 6 February 2026: fixes, no new features (Heroku alternatives). DigitalOcean App Platform “does not support volumes”. Northflank is built to run in your own AWS, GCP or Azure account too.

Render vs Railway vs Fly.io pricing: billed by use

Railway meters memory and CPU by the second; the Hobby plan's $5 counts toward usage. It is built for an app that may outgrow one machine, and its hard spending limit takes every workload offline when reached. Fly.io bills each Machine while it runs and is built for one app in several regions; its managed Postgres starts at $38 a month, and it has no spending cap.

One flat price for a machine: Pethost and Sliplane

The third kind sells the machine, not the service: the next service adds nothing to the bill while it fits. Sliplane's €9 a month is a server of 1 vCPU and 1 GB; the first that holds 3 GB is €28.80.

Pethost Starter is €9.99 a month without VAT for a virtual machine of your own, in the EU: 2 vCPU, 3 GB and 30 GB, for as many projects, containers and databases as fit, with nothing metered.

What €9.99 a month buys, at Render's prices

Starter's 3 GB of always-on memory, bought at each host's own plan prices:

On Render that is one 2 GB instance and two of 512 MB. Fly.io's figure is three 1 GB Machines in Ashburn, Railway's memory alone, before CPU. On Pethost €9.99 is the whole machine: the best value of the eight, at €3.33 for a gigabyte of always-on memory. Render's 512 MB instance comes to $14 a gigabyte. Grow, €17.99 for 4 vCPU, 6 GB and 60 GB, is €3.00 a gigabyte.

And the work around the services is already done:

Also in the price: HTTPS on your own domains, a deploy on every push to GitHub, SSH into any container, and security updates that install themselves. Hosting with an MCP server compares the agents' tools.

What if I just rent a VPS?

You can, and Coolify or Dokploy put a free panel on it (the self-hosted panels compared). An agent on a bare server works as root over SSH: nothing tells it what runs there, and one wrong command takes down the proxy, a database or the firewall. On Pethost it works through 13 tools, and its shell is inside a project's containers, never on the machine.

And a server is not sure to cost less. Hetzner is the server guides and assistants name first, at prices it no longer has: it raised them on 1 April and 15 June 2026, and its cheap Cost-Optimized range has long been out of stock. Those servers are hardware it bought at good prices, before the RAM shortage, and on 5 October every plan of the range was marked “not available”. The 2 vCPU, 4 GB server it does sell, CPX22, is €19.49 a month, up from €7.99. Add a panel, backup storage and your hours. Starter is €9.99 with all of it done.

How to move off Render: render.yaml to Compose, Postgres by dump and restore

Render reads its own render.yaml and nothing from a Compose file: the request “Support docker-compose” on its board has been open since 17 July 2019. So the services are written once more, as a Compose file, which Pethost runs as written (managed Docker Compose hosting compares who else does). Each type: web, pserv or worker becomes a service, a keyvalue a Redis-compatible image, an entry of databases a postgres image with a named volume, envVars lines of .env. A type: cron becomes a service that keeps its own timer: Compose has no schedule. A web service, a worker and a database, $20 a month on Render, are one file:

services:
  web:
    build: .
    env_file: .env
    depends_on: [db]
  worker:
    build: .
    command: node worker.js
    env_file: .env
    depends_on: [db]
  db:
    image: postgres:17
    env_file: .env
    volumes: ["pgdata:/var/lib/postgresql/data"]
volumes:
  pgdata:
x-pethost:
  routes:
    - {host: shop.sam.pethost.app, service: web, port: 3000}

Render's documentation gives the export, run on your computer against the database's external URL:

pg_dump --dbname=<EXTERNAL_DATABASE_URL> -n public --no-owner > shop.sql

The file goes into the new Postgres container with psql. With the Pethost plugin, your agent does both:

From then on the database is a container in your project, in the nightly backup: not a managed database with replicas or point-in-time recovery, as Render's is.

Who Pethost is for

Prices are what each vendor's own pages said on 5 October 2026, in its currency; ours are without VAT, and the sums are ours. Render's Blueprint and backup pages were read on 6 October.

1. Render: pricing
2. Render: free instances
3. Render: updated workspace plans
4. Render: disks
5. Render: MCP server
6. Render: Blueprint reference
7. Render: Postgres backups
8. Render: “Support docker-compose”
9. Hacker News: “Render.com Raises Prices”
10. Heroku: pricing
11. Heroku: an update
12. DigitalOcean App Platform: pricing
13. DigitalOcean App Platform: limits
14. Northflank: pricing
15. Northflank: billing
16. Railway: plans
17. Railway: cost control
18. Fly.io: pricing
19. Fly.io: cost management
20. Fly.io: Managed Postgres
21. Sliplane: pricing
22. Hetzner Cloud: Cost-Optimized plans
23. Hetzner: price adjustment