← All Posts
· Nearbase Team

Simpler Pricing: One Price, Every Region

We trimmed our instance catalog and made pricing identical in every region. Fewer, clearer choices — and the same price whether you deploy in Tokyo, Dubai, or Virginia.

Nearbase simpler pricing — one price in every region

Good pricing should be easy to reason about. Today we’re making Nearbase pricing simpler in two ways: a tighter instance catalog and one price in every region.

No action needed on your part. Running instances keep their locked-in price, and everything you rely on keeps working. This is about making the next instance you create easier to choose and easier to predict.

One price, every region

Until now, the price of an instance depended a little on where you deployed it — a quirk inherited from how underlying costs vary by region. It meant you could end up price-shopping across regions instead of choosing the region that’s actually closest to your users.

That’s backwards. Where your database lives should be a latency and compliance decision, not a pricing one.

So we’ve made it uniform: a given instance class and storage size now costs exactly the same in all 10 regions — Tokyo, Seoul, Singapore, Kuala Lumpur, Jakarta, Manila, Bangkok, Hong Kong, Dubai, and Virginia. Pick the region nearest your users (or required by your compliance needs) and the price doesn’t move.

A tighter, clearer catalog

We also took a hard look at our instance lineup and trimmed it from 17 classes down to 13. A smaller menu isn’t about taking choices away — it’s about removing the choices that only ever caused hesitation.

The catalog now breaks down cleanly into three groups:

  • General Purpose — Economy (ARM). The cheapest way to run a real managed Postgres, starting at around $14/month including storage. Perfect for side projects, staging, internal tools, and trials.
  • General Purpose — Standard. Balanced CPU and memory for production web apps, APIs, and SaaS workloads. A clean ladder from 2 vCPU all the way to 8 vCPU / 32 GB.
  • Dedicated. Dedicated CPU with 8 GB of RAM per vCPU, from 2 vCPU / 16 GB up to 32 vCPU / 256 GB — for analytics, reporting, and latency-sensitive production databases.

Every class follows a predictable doubling pattern, so sizing up is obvious: when you outgrow one rung, the next one is right there.

Why we cut classes

The four classes we removed were redundant, not useful:

  • Duplicates. A couple of sizes existed twice with different names and prices for the exact same CPU and memory. We kept the better-priced one and dropped the confusing twin.
  • Odd-shaped sizes. A few classes had memory-to-CPU ratios that didn’t line up with any clean ladder, so they were hard to compare and rarely the right answer.

For every class we removed, there’s an equal-or-better option at the same or lower price. And since you can change instance class at any time without a data migration, nothing here boxes you in.

What this means for you

  • Running instances are unaffected. Your price was locked in at creation and doesn’t change.
  • New instances are simpler to price. Choose a class, choose storage, and the number is the same in every region.
  • No lock-in, as always. Flat monthly pricing, prorated refund on deletion, and free scaling between classes.

Try it on the pricing calculator — switch regions and watch the price hold steady. Then pick the region closest to your users and ship.

Questions or feedback? We’re in Discord.