How Heroku and Render compare on dynos and instances, Postgres plans, workers, cron, pricing and platform direction now that Heroku is in sustaining engineering.

Heroku is the platform that made git push deploys normal, and for a single web app with a Postgres add-on it still does that job well. Render picked up the same model with web services, workers, cron jobs and managed Postgres in one dashboard and per-second billing for compute. Heroku stopped selling Enterprise contracts to new customers in February 2026.
This guide compares Heroku and Render for backend work, on compute, Postgres, workers, cron and pricing, and covers when the better move is a backend in your own AWS or GCP account with Encore.
Heroku prices are from heroku.com/pricing and Render prices from render.com/pricing, checked November 16, 2026.
Encore brings infrastructure from code to the same git push workflow, with the difference that the services, database, queues and schedules your code declares are provisioned in your own AWS or GCP account. A typical Heroku app with a web dyno, a worker dyno, the Postgres add-on and Heroku Scheduler maps onto four declarations in one TypeScript file.
Run in your terminal to get started locally.
The hr folder also gets an encore.service.ts that exports new Service("hr"). The service takes signups, hands the welcome email to a subscriber the way a worker dyno would, and deletes unconfirmed signups nightly. The subscriber claims each email with a conditional UPDATE, since Pub/Sub delivers at least once:
// hr/signups.ts
import { api, APIError } from "encore.dev/api";
import { SQLDatabase } from "encore.dev/storage/sqldb";
import { Topic, Subscription } from "encore.dev/pubsub";
import { CronJob } from "encore.dev/cron";
import log from "encore.dev/log";
// Replaces the Heroku Postgres add-on: RDS or Cloud SQL in your account,
// started locally by `encore run`.
const db = new SQLDatabase("signups", { migrations: "./migrations" });
interface SignupEvent {
userId: number;
email: string;
}
// Replaces the worker dyno reading from a Redis queue.
export const signups = new Topic<SignupEvent>("signups", {
deliveryGuarantee: "at-least-once",
});
// Replaces the web dyno's POST /signup route.
export const signup = api(
{ expose: true, method: "POST", path: "/signup" },
async ({ email }: { email: string }): Promise<{ id: number }> => {
if (!email.includes("@")) throw APIError.invalidArgument("valid email required");
const row = await db.queryRow<{ id: number }>`
INSERT INTO users (email) VALUES (${email.toLowerCase()})
ON CONFLICT (email) DO UPDATE SET email = EXCLUDED.email
RETURNING id`;
await signups.publish({ userId: row!.id, email });
return { id: row!.id };
},
);
const _ = new Subscription(signups, "welcome-email", {
handler: async (event) => {
// Claim the email so a redelivered message does not send it twice.
const claimed = await db.queryRow<{ id: number }>`
UPDATE users SET welcomed_at = now()
WHERE id = ${event.userId} AND welcomed_at IS NULL
RETURNING id`;
if (!claimed) return;
log.info("send welcome email", { email: event.email });
},
});
// Replaces Heroku Scheduler: called by the Encore platform at 04:00 UTC.
export const purgeUnconfirmed = api(
{ expose: false },
async (): Promise<{ deleted: number }> => {
const row = await db.queryRow<{ deleted: number }>`
WITH gone AS (
DELETE FROM users
WHERE confirmed_at IS NULL AND created_at < now() - interval '30 days'
RETURNING 1
)
SELECT count(*)::int AS deleted FROM gone`;
return { deleted: row?.deleted ?? 0 };
},
);
const __ = new CronJob("purge-unconfirmed", {
title: "Delete unconfirmed signups after 30 days",
schedule: "0 4 * * *",
endpoint: purgeUnconfirmed,
});
encore run starts Postgres locally, applies the migration and runs the topic and subscriber in process, so the web-plus-worker flow works on a laptop without a Procfile, Redis or Heroku Local. Cron jobs do not run locally or in preview environments, and you test purgeUnconfirmed by calling it from the local development dashboard. The SQL in this sample was checked against Postgres 17, including the claim, which returns a row once and nothing on the second delivery.
When you push, Encore builds the image and provisions the services on Fargate, RDS for PostgreSQL and SNS/SQS in your AWS account, or Cloud Run, Cloud SQL and Pub/Sub on GCP, as the infrastructure docs list. The cron job is managed by the Encore platform, so there is no scheduler add-on or extra cloud resource behind it. The migration guide covers what keeps running if you later stop using Encore, since everything sits in your own account. An AI coding agent working in this repository can add a second subscriber or another schedule in the same file and run it locally before it is pushed, with no dashboard settings to change alongside the code.
Best fit: teams leaving Heroku who want the push-to-deploy workflow with the database, queues and schedules running in their own AWS or GCP account.
Heroku runs apps on dynos from a Procfile, with web and worker process types, and add-ons for data and tools, most often Heroku Postgres, Heroku Key-Value Store and Heroku Scheduler. Eco dynos cost $5 per month and sleep after 30 minutes without traffic, Basic dynos are $7 for an always-on 0.5 GB process, and Standard-1X and Standard-2X at $25 and $50 add horizontal scaling and preboot. Heroku Postgres starts at $5 for Essential-0, a shared plan with 1 GB of storage and 20 connections, and the first dedicated plan, Standard-0, is $50 with 4 GB of RAM and 120 connections. The newer Fir generation runs on Kubernetes and requires a Private Space.
Heroku Scheduler runs one-off dynos at 10-minute, hourly or daily intervals and is documented as best effort, so jobs that must run every time usually move to a clock process. From February 2026 Heroku has been in sustaining engineering, focused on stability, security and support rather than new features, while credit-card customers keep the same pricing and service.
Best fit: existing Heroku apps that work today and have no pressing reason to move, and teams that rely on Heroku Connect with Salesforce.
Render charges a workspace plan, $0 for Hobby, $25 per month for Pro and $499 for Scale, plus compute for each instance. Web services, private services and background workers start at $7 per month for 512 MB and $25 for 1 CPU and 2 GB, with free instances that have usage limits. Render Postgres starts with a free instance and paid plans from $6 per month, includes point-in-time recovery and connection pooling, and storage is billed at $0.30 per GB. Cron jobs are their own service type that runs a command on a schedule, and Pro workspaces get full-stack preview environments and horizontal autoscaling.
Render moves much of what a Heroku app does into first-class service types, so a worker or a cron job is configured per service in the dashboard or in a render.yaml blueprint. It runs on Render's infrastructure, which means reaching services in your own AWS account goes over the network or AWS PrivateLink on Pro and above.
Best fit: teams that want a maintained Heroku-style PaaS with workers, cron and managed Postgres, and are fine running on the provider's infrastructure.
Stay on Heroku if the app is stable, the add-ons it depends on are working and a move would cost more than it saves for now. Pick Render if you want a Heroku-style platform with active development, first-class workers and cron jobs and cheaper small Postgres. Pick Encore when the reason to move is to own the infrastructure: the backend's services, database, queues and schedules declared in code, running locally with encore run and provisioned in your own AWS or GCP account, so a future change in a provider's plans, like Heroku's in February, does not decide where your app runs.
Both deploy web services, workers and databases from a Git push. Heroku runs apps on dynos with add-ons such as Heroku Postgres and Heroku Scheduler, and since February 2026 it is in sustaining engineering with no new features planned. Render runs web services, private services, background workers, cron jobs and static sites with its own Postgres and Key Value, and charges a workspace plan plus compute per instance.
For small always-on services the entry prices are close: Heroku's Basic dyno is $7 per month and Render's smallest paid instance is $7 per month for 512 MB. The gap shows up in Postgres, where Heroku's first dedicated plan, Standard-0, is $50 per month, and Render's paid Postgres starts at $6 per month for small instances. Prices checked November 16, 2026.
Heroku says nothing changes for current customers, but it no longer sells Enterprise contracts to new customers and is not developing new features. That is a reason to review whether Heroku still fits, and to consider another PaaS such as Render or a backend in your own AWS or GCP account.
With Encore, a web dyno route becomes an api endpoint, the worker becomes a Pub/Sub Subscription, Heroku Postgres becomes an SQLDatabase and Heroku Scheduler becomes a CronJob, all declared in TypeScript or Go. Encore provisions Fargate, RDS and SNS/SQS in your AWS account on git push, and cron jobs are managed by the Encore platform.
Deploy to your cloud on AWS and Google Cloud
without managing infrastructure
Encore lets developers and agents define application infrastructure directly in code, then automatically provisions it from local development to production in your AWS or GCP account.