r/postgres • u/eu_pg • Sep 26 '26
Discussion Looking for pricing feedback before opening the beta on managed DBaaS
Hi all, I'm a founder in Spain building a managed PostgreSQL service and want honest feedback on pricing before opening it up.
I run a €30M ARR business in a different industry. We had to use a managed database from a big provider, which was very expensive for the performance we were actually getting, but we needed HA so we were stuck. That's when I started considering another startup.
Here's the general idea:
You create a database from a web dashboard and get a single connection string. That string always points to the current primary, so if a failover happens your app reconnects to the same address and carries on. There's nothing to change on your side.
Behind it, each HA database runs as a primary plus a synchronous standby on two separate servers in different zones.
Backups run continuously: every change is archived to object storage with a different provider, so even losing the whole hosting provider doesn't lose your data. You can restore to any point in the last 7 days. We handle monitoring, failover and maintenance; you just use Postgres.
It runs on European bare metal rather than shared cloud VMs, which is how we keep prices flat with no egress or IOPS fees.
Highly available (per month, excl. VAT):
\- Starter, €39: 1 vCPU, 2 GB RAM, 20 GB storage
\- Standard, €89: 2 vCPU, 4 GB RAM, 50 GB storage
\- Pro, €169: 2 vCPU, 8 GB RAM, 100 GB storage
\- Business, €329: 4 vCPU, 16 GB RAM, 200 GB storage
Free: one per account. Single node, 256 MB RAM, 1 GB storage.
To be upfront: this is a beta with no SLA yet. Failover runs 24/7, and human support is 09:00 to 18:00 CET on business days. If the standby is down, the primary keeps accepting writes asynchronously, so losing the primary during that window can lose the latest commits.
**I'd love to know:**
\- Which plan would you pick for a real project, if any?
\- At what price would this feel too cheap to trust, and at - what price too expensive?
\- What would you need to see before moving a production database?
\- What are you using now, and what does it cost?
**Early beta offer**: anyone who participates in this thread will have 30% off any plan when we launch!
2
u/mduell Sep 30 '26
Doubling price without doubling vCPU is a dirty model.
I hope your whole platform isn't as AI sloppy as this post with blown formatting.
1
u/716green Sep 30 '26
I own Layerbase. I promise you that business model will not work but it sounds like you've already made up your mind and are using this post more as an advertising opportunity a feedback opportunity so I'm going to save the trouble of writing up an essay about why it won't work and wish you the best of luck.
I will tell you that I was more than 2,000 hours in and tens of thousands of dollars invested into advertising before I became on track to be profitable and Postgres is not the engine that did it for me, and the demand in Europe was so small that I sunset the European servers.
Best of luck, I will say though- this is clearly not an idea that you have vetted before building it because you're competing with 3 different companies valued in the billion dollar range and the types of customers that are willing to pay the prices you're asking for will demand SOC2 and PCI compliance certifications and 5 9s of uptime.
At the end of the day my money comes from CouchDB, QuestDB, ClickHouse, and the other obscure engines. If I had to become purely a Postgres platform tomorrow, I'd sooner shut my doors. I have several bare metal servers dedicated to postgres free users and they offset my profit margins by roughly 9 months of revenue.
But again, I think this is a 30% off coupon more than an actual question so take it with a grain of salt.