Render's April 2026 Pricing Overhaul: What a 3-Person and 15-Person Team Actually Pay Now

On April 23, 2026, Render did something most usage-based platforms don't: it made a core line item on the bill cheaper to look at. Per-seat workspace fees — $19/member on the old Professional plan, $29/member on Organization — are gone, replaced by flat monthly fees of $0 (Hobby), $25 (Pro), and $499 (Scale), with unlimited team members on any paid tier.

Read as a headline, that's a straightforward win: bigger teams no longer pay more just for existing. Read as a bill, it raises the obvious question — if workspace access got cheaper for most teams, where did Render make that money back? Run the actual numbers for a 3-person and a 15-person team, and the answer isn't "nowhere." It's bandwidth, and for one specific group of customers, it's the new Scale tier itself.

The Old Model vs. the New Model​

Here's the shape of the change, side by side:

Compute — the actual web service and worker instances, from a $7/month Starter box to a $450/month Pro Ultra box — sits outside all of this. Those prices didn't move in the April repricing. Everything above is the workspace layer: what you pay to have a team and a plan tier at all, before a single instance is provisioned.

What a 3-Person and a 15-Person Team Actually Pay​

The TODO-list version of this question is simple: take a small team and a mid-size team, price them under both models, and see what changes.

3-person team, on the old Professional plan: 3 members × $19/month = $57/month, before any usage.

3-person team, on the new Pro plan (assuming bandwidth stays under 25 GB): Flat $25/month. That's a 56% cut — and it doesn't matter if the team grows to 5 or 10 people, because Pro's fee doesn't move with headcount at all.

15-person team, on the old Professional plan: 15 members × $19/month = $285/month.

15-person team, on the new Pro plan (same bandwidth assumption): Still flat $25/month — a 91% cut. This is the case Render's own announcement leans on hardest, and it's real: for a team whose old bill scaled with headcount and stayed under the new bandwidth cap, the savings are dramatic and get better the bigger the team gets.

That's the flattering case. It's also not the whole story, because it assumes low bandwidth and ignores the plan track that priced in enterprise features.

The Sting: When Scale Costs More Than Organization Did​

Teams on legacy Organization weren't there for unlimited members alone — Organization was the plan with SOC 2/compliance access, and the new tier that carries the equivalent enterprise feature set (SSO, SCIM, advanced RBAC, HIPAA) is Scale, at a flat $499/month. Run the same 15-person recompute on that track instead:

15-person team, on the old Organization plan: 15 members × $29/month = $435/month.

15-person team, migrated to the new Scale plan: Flat $499/month — $64/month more, a 15% increase, before counting a single gigabyte of bandwidth overage.

That's not a rounding error, and it's not a hypothetical edge case: Hacker News threads on the change specifically flagged Render defaulting legacy Organization workspaces toward the $499 Scale tier regardless of team size. The breakeven is simple arithmetic — $499 ÷ $29/seat ≈ 17.2 members. Any Organization-track team below roughly 17 seats pays more under the new flat Scale fee than it did per-seat. A 15-person compliance-needing team is squarely inside that zone.

So the honest version of "Render's flat pricing is cheaper" is: cheaper if you were on Professional, and cheaper only above ~17 seats if you needed what Organization/Scale actually sells — compliance and access controls, not just more members.

Where the Margin Actually Went​

The original hypothesis going into this piece was that Render would recover the lost per-seat revenue somewhere in the bill that scales with usage rather than headcount — compute or bandwidth. The compute side turned out to be a non-event: Starter, Standard, and the Pro-tier instance prices are unchanged from before April 23. Bandwidth is where the lever actually moved, and Render said so directly in its own announcement:

"Our legacy plans included a large monthly bandwidth allowance, subsidized by seat fees, that most customers didn't use. We've reduced the bandwidth included on our new plans to make pricing fairer for all team sizes."

The numbers back that up. Legacy Hobby included 100 GB/month; the new Hobby tier includes 5 GB — a 20x cut. Legacy Professional/Organization included 500 GB/month; the new Pro tier includes 25 GB — also a 20x cut. The overage rate, $0.15/GB, is unchanged; only the free allowance shrank. That's the mechanism in one sentence: the per-seat fee that used to subsidize a large bandwidth pool is gone, so the bandwidth pool that fee was quietly funding got cut to match what a $25 flat fee can actually cover. Compute held flat — bandwidth did the work.

Predictably, that specific change is the one drawing pushback. A widely-shared Hacker News thread on the bandwidth cut called it "a major price hike for indie developers" — not wrong, for the subset of indie developers whose apps push meaningfully more than 25 GB/month.

The Bandwidth Sensitivity Nobody's Pricing Page Shows​

Every recompute above assumed a team stays under the new bandwidth cap. That's a real assumption to check, because it's exactly the assumption the flat-fee story depends on. Here's the same 3-person and 15-person Pro-plan bill at three bandwidth levels, each including the $0.15/GB overage past the 25 GB Pro allowance:

Two things fall out of that table. First, team size still dominates: a 15-person team comes out ahead at every bandwidth level tested, because $285/month of old per-seat fees was always going to absorb a lot of overage before the new flat fee catches up. Second, a small team that actually used its old 500 GB allowance — not hypothetically, but for real — doesn't just lose some of its savings. It ends up paying more than it did before, by a wide margin. The flat-fee pitch is a genuine win for a 3-person team using 20 GB/month; it's a 69% price increase for a 3-person team using 500 GB/month. Render's own $25/$499 headline doesn't distinguish between those two teams, but their invoices will.

No Seat Count, No Tier to Reprice​

The reason this whole exercise is possible — recomputing a vendor's bill for two team sizes and three bandwidth levels — is that Render's pricing has dimensions to move: a per-member fee that can become a flat fee, a bandwidth allowance that can shrink, an overage rate that can change independently of either. Every one of those dimensions exists because Render is selling access to infrastructure it owns and metering how much of it a given workspace consumes.

A team running on its own machines doesn't have those dials. There's no workspace tier to be migrated off of, no per-seat fee to eliminate because there was never a headcount-based invoice line to begin with, and bandwidth is whatever the box's own network provider charges — typically flat-rate or bundled into the server cost, not metered per GB by the platform layer sitting on top of it. That's not a feature Bex.co added; it's a structural consequence of the deploy target being hardware the team already owns rather than capacity a vendor leases back to them a gigabyte at a time.

Bex.co is the open-source, AI-native Render alternative — push a git repo, get a running HTTPS service on machines you own, with a Render-compatible API so migrating off per-seat or per-GB billing doesn't mean rewriting your deploy pipeline. Star the repo on GitHub or deploy your first app today.