Railway vs Render for Indie Hackers (2026 Pricing)

Verdict: Pick Railway if your app is small, idle a lot of the time, and you want to pay for what it actually uses: Hobby is $5/mo and includes $5 of usage. Pick Render if you want fixed, predictable instance prices, a free tier for demos, and managed Postgres with point-in-time recovery. For the small SaaS we costed below, Railway came to about $19/mo and Render to about $23.25/mo.

Every price and limit below comes from Railway's and Render's own pricing pages and docs, checked on 10 Nov 2026. The opinions in between are ours and marked as such.

TL;DR#

• Railway is usage-based. Hobby is $5/mo including $5 of usage; Pro is $20/mo per workspace including $20 of usage. Compute is billed per second at roughly $20 per vCPU-month and $10 per GB of RAM per month (Railway pricing).
• Render is instance-based. The Hobby workspace is $0/mo plus compute, Pro is $25/mo plus compute and Scale is $499/mo plus compute. Web services and workers start at $7/mo for 512 MB and 0.5 CPU (Render pricing).
• Free tiers differ. Render has free web services (they spin down after 15 idle minutes) and a free Postgres that expires after 30 days. Railway gives a $5, 30-day trial, then $1 of credit per month (Render free docs, Railway free trial).
• Previews and teams. Render's full-stack preview environments need Pro ($25/mo). Railway has PR environments and unlimited seats on Pro ($20/mo).
• Our pick for most solo founders: Railway Hobby to start, Render if you want a flat bill or managed Postgres features.

Disclosure: ZeroRaised publishes this comparison and is a launch site for bootstrapped products. ZeroRaised has no commercial relationship with Railway or Render and earns nothing if you sign up for either. Facts come from the linked sources as checked on 10 Nov 2026.

The setup we are comparing#

Our free hosting guide already covers what each platform gives you for nothing. This post assumes you are past that point and running a small paid SaaS with four parts:

1. A web service (your app or API).
2. A Postgres database.
3. A background worker (emails, webhooks, queues).
4. A cron job (a cleanup or report every hour).

That is where the two pricing models diverge most. If you are still choosing the rest of your stack, our SaaS tech stack for solo founders shows where hosting fits.

Railway vs Render at a glance#

Sources: Railway pricing, Railway plans docs, Railway regions, Render pricing, Render regions.

Pricing: how each one bills you#

Railway: you pay for what runs#

Railway's pricing page lists the unit rates: memory at "$0.00000386 per GB/s", CPU at "$0.00000772 per vCPU/s", volumes at "$0.00000006 per GB/s" and egress at "$0.05 per GB (services)". Over a 30-day month that is about $10 per GB of RAM, $20 per vCPU and $0.15 per GB of volume. Builds are free.

The plan fee works as a floor, not a top-up. Railway's plans docs say "If your total resource usage at the end of your billing period is $5 or less, you will not be charged for resource usage", and also that "you always pay the $5 subscription fee" even if you use less. Included usage does not roll over. Hobby caps volume storage at 5 GB; Pro lets you self-serve volumes up to 1 TB (Railway volumes).

Render: you pick an instance size#

Render prices each service by its instance type. For web services, private services and background workers (Render pricing):

On top of compute you pay the workspace plan: Hobby $0/mo (1 seat, up to 25 services, 5 GB bandwidth), Pro $25/mo (unlimited seats, 25 GB bandwidth, full-stack previews) or Scale $499/mo. Extra bandwidth is $0.15 per GB and persistent disks are $0.25 per GB per month.

Our read: Render's model is easier to explain to an accountant. Railway's is cheaper when your services sit idle, which most indie apps do for most of the day.

Postgres on each#

Render runs Postgres as a managed product. Basic-256mb is $6/mo, Basic-1gb is $19/mo and Pro-4gb is $55/mo, with storage at $0.30 per GB. Point-in-time recovery covers 3 days on Hobby and 7 days on Pro (Render pricing). The free database has 1 GB of storage and no backups, and "Free Render Postgres databases expire 30 days after creation", with a 14-day grace period to upgrade (Render free docs).

Railway deploys Postgres from a template: "This deploys a single node that Railway maintains" (Railway PostgreSQL docs). You pay for its CPU, memory and volume like any other service. Volume backups can run every day (kept for 6 days), weekly (27 days) or monthly (89 days) (Railway backups). High availability is a separate conversion step.

One vendor-written line worth knowing, from Railway's own comparison page: "Railway does not publish a database uptime SLA" (Railway vs Render, written by Railway).

Our read: if your database is the business, Render's managed Postgres with point-in-time recovery is the calmer choice; for the cheapest small database, Railway usually wins. If you want a separate database host instead, see our free Postgres database roundup.

Workers, cron and sleeping services#

Background workers. On Render, workers use the same instance prices as web services, from $7/mo, with no free instance. On Railway a worker is just a service, billed on use.

Cron jobs. Render's cron docs say "There is a minimum monthly charge of $1 per cron job service" and runs are billed per second, with a run stopped after 12 hours. Railway's cron docs say "Scheduled runs must be at least 5 minutes apart in UTC" and a run is skipped if the previous one is still going.

Sleeping. Railway's serverless setting puts a service to sleep "somewhere between 5 and 10 minutes after its last outbound traffic", and "The first request sent to a slept service may return a 502 Bad Gateway response" (Railway serverless). On Render only free web services sleep: they spin down after 15 minutes without inbound traffic and take "about one minute" to wake.

Disks. On both, attaching storage costs you zero-downtime deploys. Render: "Adding a disk to a service prevents zero-downtime deploys" (Render disks). Railway: "Replicas cannot be used with volumes" and redeploys have "a small amount of downtime".

Worked example: the same small SaaS on both#

This is our illustrative arithmetic from the published unit prices above, not a quote from either vendor. Assumptions: low traffic, 10 GB of egress a month, a 5 GB database, and an hourly cron job that runs for 1 minute (720 minutes a month).

Railway (usage you might see at low traffic, on Hobby):

Hobby's $5 fee covers the first $5 of usage, so the bill is about $19/mo. On Pro, the $20 fee would cover all of it: $20/mo.

Render (fixed instances, on the Hobby workspace):

Move to Render Pro for previews or a teammate and it becomes $25 + $22.50 = $47.50/mo (bandwidth now covered by the 25 GB allowance). Swap Basic-256mb for Basic-1gb and add $13.

Our read: the Railway number depends on what your code really uses. An app sitting at 1.5 GB of RAM costs $15 a month in memory alone on Railway. Check your usage in week one before trusting any estimate.

Developer experience and the rest#

• Infrastructure as code. Render uses Blueprints: "By default, this file has the name render.yaml" (Render Blueprint spec). Railway's config-as-code page now opens with "Config as Code is deprecated" and "Prefer Infrastructure as Code", and says "Existing files keep working for legacy services until 2026-12-01" (Railway config as code). If you rely on railway.json or railway.toml, read that page before December.
• Builds. Railway "will always build with a Dockerfile if it finds one". Render includes 500 build minutes a month on Hobby.
• Preview environments. Render: "Preview environments require a Pro workspace plan or higher" (Render previews). Railway: PR environments are enabled in project settings and deleted when the PR closes (Railway environments).
• Compliance. "Railway is SOC 2 Type II certified and SOC 3 certified", and a HIPAA BAA is an add-on with a spend threshold (Railway compliance). Render lists a GDPR DPA and HIPAA-enabled workspaces on its higher plans at a "20% compute premium".

Pick Railway if / pick Render if#

This is our editorial advice.

Pick Railway if:

• Your services are idle most of the day and you want the bill to reflect that.
• You want to run several small side projects in one account for about $5 to $20 a month.
• You want PR environments and unlimited teammates without a $25 workspace fee.

Pick Render if:

• You want a fixed number on your invoice every month.
• You want managed Postgres with point-in-time recovery and clear instance sizes.
• You need a free web service for a demo or a portfolio project (and can live with the 15-minute spin-down).
• You want a Frankfurt region or a render.yaml file that describes your whole stack.

Migration notes#

Moving either way is mostly mechanical. Our checklist:

1. Deploy from a Dockerfile so the build is identical on both hosts.
2. Recreate environment variables on the new platform and point them at the new internal hostnames.
3. Put the app in maintenance mode, run pg_dump against the old database and pg_restore into the new one.
4. Move uploaded files to object storage first; both platforms tie volumes and disks to one instance.
5. Switch DNS and keep the old service up until traffic has moved.

Alternatives in brief#

• Fly.io: another container platform in the same space. We did not price it for this post, so check its own pricing page against the worked example above.
• A VPS plus Coolify: the cheapest route once you are comfortable running a server. Our best VPS for indie hackers guide compares the providers.

Frequently asked questions#

Is Railway cheaper than Render?#

Often, for small and idle-heavy apps. Railway bills for the CPU and memory you actually use, so a quiet web app, worker and database can fit in about $19/mo on Hobby in our worked example. Render charges fixed instance prices, so the same stack is about $23.25/mo on its $0 Hobby workspace. If your services run hot all month, Railway's usage bill can overtake Render's flat prices.

Does Render still have a free tier?#

Yes. Render lets you run free web services, one free Postgres database and one free Key Value instance per workspace. Free web services spin down after 15 minutes without inbound traffic and take about a minute to wake. Free Postgres has 1 GB of storage, no backups, and expires 30 days after creation, with a 14-day grace period to upgrade.

Does Railway have a free plan?#

Railway starts you on a 30-day free trial with a one-time $5 credit and no credit card. After that you drop to the Free plan, which includes $1 of usage credit per month, 0.5 GB of RAM and 1 vCPU per service, and one project. For a real product you will want Hobby at $5/mo.

Which is better for a background worker and cron jobs?#

Both handle them. Render has dedicated background worker and cron job service types: workers start at $7/mo and each cron job service has a $1/mo minimum, billed per second. On Railway a worker is just another service billed on usage, and a cron service runs on a schedule at least 5 minutes apart and is billed only while it runs.

Is it hard to move from Railway to Render or back?#

Not for a typical app. If you deploy from a Dockerfile, both platforms will build it. The real work is the database: dump Postgres with pg_dump, restore it with pg_restore on the new host, copy your environment variables, then switch DNS. Plan a short maintenance window for the database cutover.

Ship it, then launch it#

Once your app is live on either host, launch it on ZeroRaised, the launch directory for products built without VC money. For more hosting and stack comparisons with prices checked on the day, join the ZeroRaised newsletter.

Sources#

• Railway pricing, last checked 10 Nov 2026
• Railway plans documentation, last checked 10 Nov 2026
• Railway free trial documentation, last checked 10 Nov 2026
• Railway volumes, last checked 10 Nov 2026
• Railway backups, last checked 10 Nov 2026
• Railway PostgreSQL, last checked 10 Nov 2026
• Railway cron jobs, last checked 10 Nov 2026
• Railway serverless, last checked 10 Nov 2026
• Railway deployment regions, last checked 10 Nov 2026
• Railway environments, last checked 10 Nov 2026
• Railway config as code, last checked 10 Nov 2026
• Railway compliance, last checked 10 Nov 2026
• Railway vs Render (vendor-written), last checked 10 Nov 2026
• Render pricing, last checked 10 Nov 2026
• Render free instances, last checked 10 Nov 2026
• Render cron jobs, last checked 10 Nov 2026
• Render persistent disks, last checked 10 Nov 2026
• Render regions, last checked 10 Nov 2026
• Render Blueprint spec, last checked 10 Nov 2026
• Render preview environments, last checked 10 Nov 2026