My $200M-funded competitors charge 3× more than me. Here's how.

I'm a solo founder running a managed PostgreSQL service for AI workloads. My competitors (Supabase, Neon, AWS) have raised hundreds of millions in funding. They charge $100-150/month for the same specs I offer at $35.

This isn't a VC-funded race to the bottom. I'm profitable on every customer. The truth about how is pretty unsexy.

The setup

I'm a DevOps engineer by day. I manage Kubernetes clusters and CI/CD pipelines for 5,000 developers at my consulting job. On the side, I built Rivestack, a managed PostgreSQL service with pgvector, which is the vector search extension every AI app needs right now.

The market timing is good. The entire industry is moving from dedicated vector databases like Pinecone and Weaviate to "just use Postgres with pgvector." Every week there's a new blog post about someone ditching their vector DB and going back to Postgres.

But every managed Postgres provider that offers pgvector charges a premium for it. Supabase charges about $105/month for a dedicated instance with 2 vCPU and 4 GB RAM. AWS RDS is $150+. Neon's serverless model makes costs unpredictable at scale.

I kept looking at those prices thinking: does it actually cost that much to run a dedicated Postgres instance?

The math that makes it work

It doesn't.

The big cloud providers (AWS, GCP) charge massive margins on compute. A 2 vCPU / 4 GB instance costs them pennies but they charge you $70-100/month. Then Supabase or Neon adds their margin on top.

I cut out the hyperscaler entirely. I run on dedicated servers in ISO 27001 certified data centers. NVMe storage, not cloud SSDs. The raw infrastructure cost for a dedicated Postgres instance with 2 vCPU, 4 GB RAM, and 55 GB NVMe is way less than what the big players charge.

That's the entire competitive advantage. No magic, no proprietary technology. Just a different infrastructure choice that gives me real margins at $35/month while Supabase needs $105 for the same specs.

What I actually built

The product isn't complicated. Every instance gets:

PostgreSQL 18 with pgvector 0.8 pre-configured
NVMe storage (500K+ IOPS vs 3,000 on cloud SSDs, which matters a lot for vector index scans)
Automated daily backups with 14-day point-in-time recovery
HA support with Patroni
Monitoring with Prometheus and Grafana
SSL and a Terraform provider

The whole stack is open-source: Patroni for high availability, pgBackRest for backups, Prometheus for monitoring. Same tools that run Postgres at scale everywhere. My DevOps background is the moat. I know how to automate all of this so it runs without me touching it.

The pricing decision that kept me up at night

I launched at $29/month. Then my infrastructure provider raised prices by 30%.

My margin on the $29 Starter plan dropped to dangerous levels. Like, one unexpected cost and I'm losing money per customer.

I had zero paying customers at that point. The conventional wisdom says "don't raise prices until you have traction." But I sat down and did the math:

At $29 I was making about $3-4 margin per customer. That's not a business, that's volunteering. At $35 I'd make $10+ per customer. Still 3× cheaper than Supabase. Still the cheapest dedicated pgvector you can get.

So I raised prices before getting a single paying customer.

Nobody choosing between Rivestack at $35 and Supabase at $105 cares about a $6 difference from my old price. The story is exactly the same: same specs, fraction of the cost. But that extra $6 per customer is the difference between a sustainable business and one that bleeds cash.

I'm glad I did it early. Raising prices on existing customers later is way harder.

Being honest about what I'm not

My landing page has a comparison table showing Rivestack vs Supabase vs Neon vs AWS RDS. In that table, there's a row for SOC2 compliance. Under Rivestack it says "Not yet."

Below the table there's a note that says something like: Supabase and Neon are excellent platforms with much broader feature sets. If you need auth, storage, edge functions, use them. Rivestack is for teams that need fast, affordable, dedicated pgvector and nothing else getting in the way.

I'm literally telling potential customers to use my competitors if they're a better fit.

Sounds insane. But it might be the most effective marketing decision I made. Developers are so used to being sold to that honesty becomes the differentiator.

When someone reads "Not yet" under SOC2, they suddenly trust the rest of the page more. The benchmark numbers become believable. The pricing becomes believable. Everything gets a credibility boost from the one moment where I told the truth that hurt.

The demo that does the selling

I built ask.rivestack.io, a semantic search tool over 30 days of Hacker News content. It runs on a Rivestack free tier cluster. You type a query, it searches about 3,600 stories using OpenAI embeddings and HNSW vector indexes, and returns results in under 50ms.

This costs me nothing to run (it's on the free tier) and it's more convincing than any landing page copy I could write. When someone asks "does pgvector actually perform well?" I just link the demo. They can feel the speed themselves.

Build the proof, not the pitch. That's what I keep telling myself.

Where I am now

One week after launch:

1 signup (free tier)
A handful of landing page visits from Dev.to, Indie Hackers, and Hacker News
Zero revenue

I'm not going to pretend that's great. But I'm also not panicking. Most SaaS products take 3-6 months to get their first 10 paying customers through organic marketing. I have a full-time consulting income that covers all my bills. Rivestack doesn't need to pay my rent next month. It needs to prove that someone will pay $35/month for managed pgvector.

If that proof comes in 2 months or 6 months, either is fine. I have runway.

The model I'm building toward

I don't want to build a startup. I want to build a machine.

The infrastructure is automated. Provisioning, backups, monitoring, failover, all of it runs without me. My goal is to eventually hire one person at a modest salary to handle support and monitoring, and run this as a mostly-passive business alongside my consulting work.

If it grows to $5,000-15,000 MRR, that's life-changing money on top of my salary. If someone wants to acquire it at that point, I'll probably sell. If it plateaus at $2,000 MRR, I'll keep it running because the margins make it worth it at any scale.

Not every SaaS needs to be a VC-backed rocket ship. Some can just be good, profitable businesses that run quietly.

What I'd tell you if you're considering something similar

Find the margin gap. Every industry has products where the big players charge 3-5× what it actually costs to deliver. Usually it's because they're building on AWS/GCP and passing along the cloud tax plus their own margin. If you can deliver the same thing on cheaper infrastructure with solid automation, you have a real business.

Be honest about your weaknesses. It builds more trust than hiding them. Developers especially can smell BS from miles away.

Build the proof, not the pitch. A working demo beats a landing page. A benchmark with methodology beats marketing claims.

Do the margin math before you launch. I almost launched at $29 with $3 margins. That would have been a slow death. Know your unit economics cold before you put a price on anything.

Don't wait for perfection. I launched without SOC2, without a fancy dashboard, without half the features I want to build. The product works, the backups are solid, the performance is real. Everything else can come later.

If you want to see the landing page and comparison table: rivestack.io
If you want to try the demo: ask.rivestack.io

Happy to answer questions about the infrastructure setup, pricing decisions, or competing with funded companies as a solo founder.