Heroku licence cost after the Salesforce acquisition

Heroku is the odd one out among the Salesforce-family products because it does not have a seat price. There is no per-user figure to multiply by headcount, which is why renewal conversations about it often go wrong: finance looks for a user count, finds none and assumes the platform licence covers it. It does not. Heroku was acquired in 2010 and remains a separate platform with its own pricing. This guide covers that pricing only. The services side, meaning building, moving or integrating an app, is on the sibling pages linked at the end.

#What you are actually buying

A Heroku bill is assembled from four kinds of line. Dynos are the containers that run your code. Data services, chiefly Postgres, hold your data. Add-ons from the marketplace supply everything else, from logging to caching. And on top sit optional commercial layers: Private Spaces for network isolation, Heroku Enterprise for team access and compliance controls, and paid support plans.

Heroku's pricing page lists most of these with a price per month. We read it on 13 October 2026, and the figures below are US dollars. As with every vendor price list, they are subject to change.

The page shows two dyno families, Cedar and a newer Kubernetes-based family called Fir. Both are priced, and the Fir entries we read start at US$25 a month for a classic one-CPU dyno and also require a Private Space. Ask which family a quote is built on, because migrating between them is engineering work, not a licence toggle.

#Data services are a second bill

Dynos are rarely the largest line for a data-heavy application. The same page lists Postgres by plan.

The step from Essential to Standard is the step from a shared server with a stated maximum downtime of four hours a month to a dedicated one. The step to Premium adds high availability. Those are availability decisions as much as price decisions, and the right one depends on what an hour of downtime costs your business. Heroku also sells a key-value store, Kafka and, more recently, managed inference and agent services, each with its own price list.

#A worked example

Consider a customer portal with two web dynos at Standard-2X, one background worker at Standard-1X and a Standard-0 Postgres database. At list that is 2 times 50, plus 25, plus 50, which is US$175 a month, or US$2,100 a year. Upgrade the database to Premium-0 for high availability and the monthly figure is 100 plus 25 plus 200, or US$325, so US$3,900 a year. Add a few marketplace add-ons and a support plan and the total grows again.

Now move the same workload into a Private Space because a security review demands network isolation. The Private dyno prices apply and the Space itself is charged on top. We did not find a Private Space price on the page we read, so ask for it explicitly in any quote. The point of the example is not the totals. It is that each architectural decision has a licence consequence, and the licence cannot be sized without the architecture.

#Three application shapes at list price

Putting numbers beside shapes makes the licence conversation concrete. The table uses the list prices above, excludes add-ons, support and any Private Space, and is an illustration of arithmetic rather than a quote.

The spread is more than a hundredfold, and nothing in it depends on how many people work at the company. That is the point. A Heroku licence is a statement about workload, and any budget that tries to derive it from headcount will be wrong in one direction or the other. The internal tool is a rounding error that nobody should spend a negotiation on. The portal is where discipline starts to pay, because a decision to run one web dyno fewer or to defer high availability moves the figure by a visible amount. The high-traffic service is where you should be talking to the account team about Enterprise and credits, because a predictable annual spend of this size is exactly what a committed pool is for.

#Reading a Heroku quote line by line

When a quote arrives, resist the instinct to read the total first. Read the lines. For each dyno line, check the type, the family, the quantity and whether it is meant to run all month or only for a window. For each data line, check the plan and whether it is the production database or a copy. For add-ons, check that every one has a named owner and a reason to exist. For anything that mentions a Private Space or Shield, check that the Space itself is priced and that the number of dynos you need actually fits the way it is sold.

Then look for what is missing. A quote with no support line is a quote that assumes nothing will go wrong. A quote with no staging environment is a quote for something that will be tested in production. A quote with no mention of the Salesforce connection means the sync licence and the Salesforce API headroom have not been thought about, and they will arrive later as separate bills.

#Contract and renewal mechanics

Self-serve Heroku accounts are billed monthly against usage, which means you can reduce spend by removing a dyno. Enterprise agreements are different: they are annual commitments with a pool of credits, and what you can change mid-term depends on the paper. Ask whether credits can be spent on any service, whether unused credits expire at term end, whether you can buy additional credits at the committed rate and who in your organisation can approve that purchase. Ask also what happens to the price of the platform if you add a Private Space or move to Shield partway through the year.

If you are coming from a direct account to Enterprise, ask for a side-by-side showing the same workload on both. Enterprise is not automatically cheaper, and its value often sits in access control, compliance and support rather than in the unit rate. Decide which of those you actually need before you let the unit rate drive the choice.

#Enterprise, credits and support

Heroku Enterprise is a separate commercial layer. The vendor describes it as a platform delivered with enhanced compliance, security and team access. It changes how add-ons are bought, and the page puts it this way: "For Enterprise customers, the Heroku Elements Marketplace uses add-on credits." One credit equals US$1 worth of any service. In practice credits give a central team a single pool to allocate across applications rather than a card on every project, and they are a sensible way to keep spend visible.

Support is priced separately too. Basic Support is free for all customers. Enterprise customers can buy Success Plans at three levels, Standard, Premier and Signature, for faster response times. If an application is mission critical, put the support level into the cost model on day one, because discovering it during an outage is the expensive way to learn.

#Heroku Connect and the Salesforce link

For Salesforce customers the most relevant product is Heroku Connect, which syncs data between Heroku Postgres and Salesforce. The pricing page says you can start free with a Demo Edition and upgrade to Enterprise or Shield editions, which are available exclusively to Heroku Enterprise customers. The Connect licence is therefore a downstream decision from the Enterprise decision, and it should be priced as its own line. The data volume you sync, the number of mapped objects and your Salesforce API limits are the technical factors that determine which edition you need.

It is worth being plain about names here. The Salesforce Help page for Data 360 says: "As of October 14, 2025, Data Cloud has been rebranded to Data 360." Data 360 is priced in its own credits and has no connection to Heroku dynos. A sandbox refresh copies CRM metadata and does not clone a Heroku application, so a test environment that needs the app needs its own dynos and database on its own line.

#Overage and billing traps

Because Heroku is usage-shaped, the traps are about scale rather than about seat counts. Auto-scaling a web tier to handle a marketing spike can multiply the dyno line for that month. A runaway worker or a forgotten staging app keeps billing until somebody removes it. A database sized for peak when typical load is a fifth of it is a quiet overspend. And add-ons from the marketplace are billed per their own plans, so a developer who adds one for a prototype can create a recurring cost nobody reviews.

Four habits keep this under control. Tag every application with a cost owner. Review the dyno list and add-on list monthly. Set scaling limits rather than leaving them open. And separate production from everything else so that the cheap Eco and Basic dynos are used where they belong, and not where their sleep behaviour would hurt customers.

#How to right-size

Start from workload shape. A steady web application with a predictable daytime peak fits Standard dynos with a modest scaling ceiling. A job queue that bursts overnight may want Performance dynos for predictability or a cheaper dyno plus patience. A prototype or internal tool can live on Basic or Eco. Match the dyno to the traffic, then match the database to the cost of downtime, then add support to match the cost of an incident.

Test with production-like load for a week before committing to an Enterprise agreement, because Enterprise is a commitment and the load profile is the number you most need. Ask the account team to model your expected consumption in credits, with the assumptions listed, and compare it to what the same stack costs on direct pricing.

#How to compare Heroku offers

When comparing a Heroku quote with the same app on another cloud, count everything: compute, database, add-ons, support, network isolation, engineering time to operate what the platform would otherwise operate for you, and the one-off cost of moving. Heroku's pitch is that you stop managing infrastructure, so a comparison that counts only raw compute will always favour the alternative and will always be incomplete. Equally, a comparison that ignores Heroku's per-unit premium at scale is incomplete in the other direction.

Compare offers from Heroku itself on cost at forecast load, cost at double that load, the credit price for additional purchases, the term, and what happens to unused credits. Get the Private Space price in writing.

#Where to go next

The services side of keeping an app on Heroku is on the Heroku page. For what the acquisition was, see what happened to Heroku. For the records an app reads and writes, see integrating Heroku with Salesforce, and for whether to move an app, see should I migrate from Heroku.