---
title: What A Production App Costs
url: "/docs/comparisons/production-app-costs/"
canonical_url: https://docs.blossom88.com/docs/comparisons/production-app-costs/
markdown_url: https://docs.blossom88.com/docs/comparisons/production-app-costs.md
summary: One production Environment compared across Blossom and other platforms, with
  resources, assumptions and calculations
categories:
- comparisons
- pricing
---

# What A Production App Costs

One App, one production Environment. USD for 30 days (720 hours), before tax.
Comparison updated **October 23, 2026**. These are resource estimates, not quotes
or equal-performance claims. No staging or Redis is included.
The Blossom baseline uses **On demand**; default **Automatic** reserved capacity
adds billed deployment room beyond this steady-state estimate.

## The App

| Service | Resources per instance | Count |
| --- | --- | ---: |
| Web | 1 vCPU / 1.75 GB | 2 |
| Worker | 1 vCPU / 1.75 GB | 1 |
| Scheduler | 1 vCPU / 1.75 GB | 1 |
| PostgreSQL | 2 vCPU / 3.5 GB | 1 |

**50 GB database storage and 100 GB outbound traffic.** Blossom includes
unlimited team members; the Vercel estimate assumes three paid seats.
PostgreSQL uses shared Data capacity on Blossom. Memory labels use decimal GB:
3,500,000,000 bytes and 1,750,000,000 bytes. Each App container uses the
Medium preset; PostgreSQL uses Large.
Competitor plans round up where needed; CPU classes and memory units differ.

## The Totals

| Platform | 30 days | Basis |
| --- | ---: | --- |
| Blossom BYOC · Hetzner EU | **$25–75** | $0 Blossom management after the unused $20 credit, plus three provider Servers and disk |
| Blossom Cloud · Hetzner EU | **$103** | Two App units, one shared Data unit, disk and transfer |
| [Railway Pro](https://railway.com/pricing) | $77–238 | $77 at light use, $122 moderate, $238 full use |
| [Northflank Cloud](https://northflank.com/pricing) | $156 | $144 compute + $5.83 disk + $6 transfer |
| [Render Pro](https://render.com/pricing) | $226 | Team plan, four services, PostgreSQL, disk and transfer |
| [Vercel Pro](https://vercel.com/pricing) | $258 | Illustrative Frankfurt scenario; three seats and Neon PostgreSQL |
| [Heroku · Cedar](https://www.heroku.com/pricing/) | $1,050 | Selected memory-fitting dynos and Standard-0 PostgreSQL |

Builds, backup storage and temporary rollout/replacement capacity are extra
where charged. Included recovery and the explicitly modeled Neon history stay
in the totals. The two web replicas do not establish host redundancy or HA.

## How Blossom Fits It

Blossom bills whole capacity units. Each nominal 2 vCPU / 4 GB App unit leaves
3.5 GB for Containers after delivery reserve. This steady-state arrangement fits:

| Capacity | Workload | Reserved resources |
| --- | --- | --- |
| App unit 1 | Two web replicas | 2 vCPU / 3.5 GB |
| App unit 2 | Worker and scheduler | 2 vCPU / 3.5 GB |
| Data unit 1 | Shared PostgreSQL | 2 vCPU / 3.5 GB |

The four App containers fill two App units. PostgreSQL uses a separate Data
unit: three units total, represented here by three Servers.

Two App units ($60) + one Data unit ($35) + 50 GiB disk ($7.50) +
100 GB transfer ($0.20) = **$102.70** in Hetzner EU. DigitalOcean is
**$118.50**, Hetzner Singapore **$133.50**, and Hetzner US **$162.70**.
A rolling deployment can require temporary extra App capacity; its duration is
not modeled. Separate Builders also have their own bill.

For BYOC, two App units ($10) + one Shared Data unit ($10), minus the unused
$20 monthly credit, leave **$0 in Blossom management fees**. This assumes one
Organization with no other credit-consuming usage in that calendar month.
Provider charges remain paid: three CX23 Servers at $7.09 or CPX22 Servers at
$23.59, plus 50 GiB disk at $0.0767, produce **$25.105–74.605 total**, rounded
once to $25–75. These are dated October 2 supplier inputs, including primary
IPv4; cheap supply and actual hourly/monthly billing must be checked. Transfer
fits the provider's included EU allowance.

The total combines two bills: **$0 Blossom management** and approximately
**$25–75 to Hetzner**. Hosted images and backups are additional. Without
available credit, Blossom management is **$20**, bringing the combined
estimate to **$45–95**. Shared and Dedicated Data management both qualify.

This PostgreSQL allocation uses one Data unit’s full CPU allocation and
3,500,000,000 bytes of memory, using Blossom’s Large shared-data preset. Data
hosts leave 3,900,000,000 bytes after system reserve, so 400 MB remains spare.
The full CPU
allocation prevents another resource sharing this host. Smaller Databases
and Caches can share a unit.
Provider disk is billed separately.

## How The Others Were Priced

**Railway:** published per-second rates of $0.00000772/vCPU,
$0.00000386/GB memory and $0.00000006/GB volume, plus $0.05/GB egress.
The workload totals 6 vCPU and 10.5 decimal GB of requested memory.
Applying
10% CPU / 50% RAM gives **$77.31**; 25% / 75% gives **$121.58**;
100% / 100% gives **$237.89**. These are hypothetical average usage levels,
using decimal GB against the dated GB-labeled rate inputs. Provider unit
semantics remain an estimate assumption; the Blossom allocation uses exact decimal bytes. All exceed
Pro's $20 minimum, which includes usage; do not add another $20.
Database maintenance and recovery coverage differ from managed PostgreSQL.
[Rates](https://railway.com/pricing).

**Northflank:** four 1 vCPU / 2 GB plans at $24 each (two web, worker and
scheduler), plus 2 vCPU / 4 GB PostgreSQL at $48: **$144** compute.
50 GiB disk × $0.11657 + 100 GB egress × $0.06 gives **$155.8285** total.
Backup storage and extra build compute are excluded. These selected presets
supply more memory than the Blossom sizes. [Rates](https://northflank.com/pricing).

**Render:** four 1 CPU / 2 GB services at $25 each. Add a 2 CPU / 4 GB
PostgreSQL plan at $75, 49 GB of paid disk at $0.30 (1 GB included), the $25 Pro workspace,
and 75 GB of egress beyond its included 25 GB at $0.15: **$225.95**.
Seven-day PITR is included. [Compute pricing](https://render.com/pricing),
[workspace allowance](https://render.com/docs/new-workspace-plans).

**Heroku:** this is a **Cedar** example, not every Heroku offering. Four
Performance-M dynos at $250 provide 2.5 GB each for web, worker and scheduler.
Standard-0 PostgreSQL adds $50 with 2 vCPU, 4 GB RAM and 64 GB disk:
**$1,050**. CPU equivalence is not established by Heroku's compute multipliers.
Its database recovery coverage
differs; this is not a minimum bill for an app with smaller requirements.
[Selected plans](https://www.heroku.com/pricing/),
[PostgreSQL specifications](https://devcenter.heroku.com/articles/heroku-postgres-production-tier-technical-characterization).

## Vercel Estimate

**$258.33, rounded to $258.** One illustrative Frankfurt deployment, using
Functions for web, a Daemon for the worker and Cron for scheduling.
This changes the architecture; it is not two permanently reserved web replicas.
The existing 2 GB Cron Function already covers the larger scheduler memory
request. Its assumed work per invocation is unchanged, so this estimate stays
the same.

| Input | Assumption |
| --- | --- |
| Web | 500,000 requests; 100 ms active CPU, 500 ms duration, 2 GB per request |
| Worker | One 2 GB / 1 vCPU Daemon, 720 hours, average 10% CPU activity |
| Scheduler | 2 GB Cron Function every minute; 43,200 calls, 10 ms CPU and 100 ms duration each |
| Transfer | 100 GB uncached origin responses; visitor traffic and requests fit included CDN allowances |
| PostgreSQL | Neon Launch, fixed 2 CU / 8 GB, always on for 720 hours |
| Database storage | 50 GB data and an assumed 10 GB-month of retained restore history |

| Item | Arithmetic | 30 days |
| --- | --- | ---: |
| Pro seats | 3 × $20 | $60.00 |
| Active CPU | 86.008889 hours × $0.184 | $15.83 |
| Provisioned memory | 1,581.288889 GB-hours × $0.0152 | $24.04 |
| Invocations | 543,200 × $0.60 / million | $0.33 |
| Origin transfer | 100 GB × $0.06 | $6.00 |
| Team usage credit | Applied once | −$20.00 |
| Neon compute | 1,440 CU-hours × $0.106 | $152.64 |
| Neon data | 50 GB × $0.35 | $17.50 |
| Neon history | 10 GB-month × $0.20 | $2.00 |
| **Total before rounding individual lines** | | **$258.33** |

Web memory assumes no concurrent-request sharing; concurrency may lower it.
Worker memory remains billed while idle. Neon rounds up to 8 GB to meet the
2 vCPU target. Increasing worker CPU activity from 10% to 25% adds **$19.87**;
the bar is not a cap. Daemons are in public beta. Compatibility and recovery
capabilities require their own evaluation.

Vercel inputs checked October 22; Neon pricing rechecked October 23, 2026:
[Vercel seats and credit](https://vercel.com/docs/plans/pro-plan),
[Frankfurt rates](https://vercel.com/docs/pricing/regional-pricing/fra1),
[Function billing](https://vercel.com/docs/functions/usage-and-pricing),
[Daemons](https://vercel.com/docs/daemons/limits),
[Neon rates](https://neon.com/pricing),
[compute units](https://neon.com/blog/new-usage-based-pricing),
[restore history](https://neon.com/docs/postgres/backup-restore/history-window).

## What You Get

A visible workload behind every bar. Compare the resources, usage assumptions
and included services, then adjust your own budget in the
[Blossom calculator](https://app.blossom88.com/pricing/calculator).