~/rivestack $ _
Postgres for AI workloads.
Without the platform tax.
// Dedicated PostgreSQL on NVMe with tuned pgvector — semantic search, table editor, and AI-assisted SQL editor built in. Fixed pricing from $29/mo, migration help included.
Free tier · no credit card · pgvector ready in 60 seconds
qps
~4,465
p50
3.5 ms
search> vector databases for RAG_
0.892Vector search in production
0.864RAG architecture patterns
0.821Building AI search engines
~3.5ms · HNSW index used
2–5 ms
p50 vector search at recall@10 0.90+
1M
vectors served hot at ~2 ms p50 (Scale)
65%+
lower cost vs. Supabase at same compute
EU
Hosted in Germany · data stays in EU
# if any of this sounds familiar
Your pgvector setup is probably costing you.
// Vector workloads don't fit neatly into general-purpose Postgres pricing. Most teams we talk to are losing money, losing sleep, or both.
Your Supabase bill is climbing
Compute add-ons, storage, egress, and vector index memory keep adding up. The pgvector workload you run for one feature is now your biggest Supabase line item.
Neon cold starts are killing your RAG latency
Serverless Postgres is elegant until the first query of the day takes 2 seconds. Usage-based pricing feels cheap until it isn't.
Pinecone is expensive and you want SQL back
You're paying for a dedicated vector database while your app data lives in Postgres. One more service, one more bill, one more copy of the data to keep in sync.
Self-hosting pgvector became a second job
You chose a VPS to save money. Now you maintain Patroni, backups, PITR, upgrades, and HNSW tuning at 2am instead of shipping.
Migrating from Supabase, Neon, or Pinecone?
We'll plan the move. Free.
Send us your row counts, dimensions, QPS targets, and what's hurting today — you'll get a plan back, usually within 48 hours.
$ get my workload reviewFree. No call required. No sales pitch. If Rivestack isn't a fit, we'll say so in the same reply.
- Plan recommendation for your row count + dimensions
- Expected QPS, latency, and index memory
- Side-by-side cost vs. your current provider
- Migration path (pg_dump, logical replication, or cutover plan)
# rivestack vs. what you have today
// save 65%+ vs Supabase at the same compute
| Rivestack | Supabase | Neon | |
|---|---|---|---|
| Monthly cost | $49 | ~$105 | ~$69+ |
| Compute | 2 vCPU · 4 GB | Shared · 1 GB* | Serverless |
| Storage | NVMe | gp3 SSD | Cloud SSD |
| pgvector | Tuned (HNSW) | Extension only | Extension only |
| Backups | Daily + 14d PITR | Daily | Yes |
| Vector perf | ~1,185 QPS* · 3.2ms p50 | Shared SSD | Serverless |
| Terraform | ✓ | ✓ | ✗ |
// * Vector perf on a Starter node (2 vCPU / 4 GB, AMD) at recall@10 0.90, 4 clients; every region runs the same AMD line. Supabase $25 base + ~$80/mo compute add-on for 2 vCPU / 4 GB. Neon usage-based, ~$69+ at moderate usage. Every number is measured and reproducible — full tables at /pgvector-benchmarks-measured. Also runnable with pgvector-bench — we don't publish competitor benchmarks we haven't run. Full methodology →
Supabase and Neon are excellent platforms with broader feature sets — auth, storage, edge functions, realtime. If you need those, use them. If you just need fast Postgres with pgvector, that's all we do.
# semantic search, built into your database
// pgvector + HNSW on your own dedicated NVMe Postgres. No second database to run or sync.
- One-click sample dataset. Run a real semantic query before you write a line of code.
- Embeddings generated for you. Text embeds into your vector column via the table editor or the embed API (OpenAI text-embedding-3-small, 1536-d) — you never hand-build a vector.
- Numbers measured by Postgres. Query time comes straight from EXPLAIN ANALYZE.
search> how do I deploy LLMs in production
1Serving LLMs in prod: a practical guide0.0419
2Scaling inference without burning cash0.0683
3From notebook to production API0.1102
4Lessons shipping a RAG pipeline0.1394
in-DB query time
index hit
measured, not guessed
// in-DB query time measured with pgvector-bench — not end-to-end latency.
# works with your stack
// it's just PostgreSQL. Use your existing driver.
import psycopg2
conn = psycopg2.connect("postgresql://appuser@db-7q9m2p.eu.rivestack.io/primary")
cur = conn.cursor()
# pgvector is already enabled — just create your table
cur.execute("""CREATE TABLE docs (
id BIGSERIAL PRIMARY KEY,
text TEXT NOT NULL,
emb vector(1536)
)""")
# Insert a document with its embedding
cur.execute(
"INSERT INTO docs (text, emb) VALUES (%s, %s::vector)",
("deploy LLMs in production", embedding)
)# table editor — no SQL required
- Browse rows in a fast, sortable grid
- Filter by any column — =, contains, ranges, is empty
- Edit a whole row in a side panel, or insert and delete rows
- No SQL needed — but the AI-assisted SQL Editor is one click away
| id | name | |
|---|---|---|
| 1 | Alice Johnson | alice@x.com |
| 2 | Bob Smith | bob@x.com |
| 3 | Carol Williams | carol@x.com |
| 4 | Dan Lee | dan@x.com |
| 5 | Erin Davis | erin@x.com |
# provision with terraform
> export RIVESTACK_TOKEN="rs_live_xxx"
> terraform init
✔ rivestack provider installed
> terraform apply -auto-approve
✔ creating cluster: demo-db (eu-1 • core-solo • size-s)...
✔ pgvector enabled (HNSW)
✔ snapshots & PITR configured
✅ done in 34.8s
> terraform output -raw database_url
postgresql://appuser:***@db-iris-12.eu-1.rivestack.cloud:5432/primary?sslmode=require
Manage it like the rest of your infra.
// Create, scale, and destroy clusters with one file and one command — no clicking through dashboards.
Built in France · Infrastructure in EU, US-East and Singapore
# what early users say
5.0 on Product Hunt"RiveStack does care about you, no matter if you are on a paid or free plan…the guys do their best to make you happy, and your project succeed. Their support is as lightning fast as their database."
Serhii Boiko
@sboyko · Product Hunt
"RiveStack is lightning fast, Postgres is online in seconds with pgvector ready for AI. The SQL tooling is solid and the AI query helper nails prompts…truly production-ready"
ILYAS AMRAOUI
@ilyas_amraoui · Product Hunt
"delivers impressively fast provisioning, databases are prd/dev ready to connect, saving me setup time. SQL tooling is solid, and the AI-assisted query generation responded accurately to my prompts."
Red
@red17 · Product Hunt
# fixed monthly pricing
// One price per node. No per-query billing, no egress surcharges, no vector-count overage. The bill on day 30 is the same as the quote on day 1.
Prices shown are EU Central, our lowest region. US-East and Singapore are priced higher — full pricing.
Shared
$0/mo
For testing, prototyping, and small personal projects.
$ start- Shared CPU · 256 MB RAM
- pgvector enabled
- 2 GB storage
- ~100K vectors (1536d)
- Community support
- SSL encrypted
Solo
$29/mo
Your own single-tenant PostgreSQL VM — for real apps that don't need HA yet.
$ start- 1 vCPU · 2 GB RAM
- 30 GB NVMe storage
- Single-tenant VM · local NVMe
- pgvector enabled
- Daily backups + 7d PITR
- SSL encrypted
Starter // popular
$49/node/mo
For production apps that need a dedicated node today and failover tomorrow.
$ start- 2 vCPU · 4 GB RAM per node
- 55 GB NVMe storage
- ~300K vectors (1536d)
- pgvector tuned (HNSW)
- HA-ready (Patroni failover)
- Daily backups + 14d PITR
- Monitoring dashboard
- Terraform provider
Growth
$85/node/mo
For workloads that outgrew Starter — double the compute and storage.
$ start- 4 vCPU · 8 GB RAM per node
- 135 GB NVMe storage
- ~600K vectors (1536d)
- pgvector tuned (HNSW)
- HA-ready (Patroni failover)
- Daily backups + 14d PITR
- Priority support
- Custom PostgreSQL config
Scale
$159/node/mo
Our biggest node — 1M vectors served hot at ~2ms p50.
$ start- 8 vCPU · 16 GB RAM per node
- 295 GB NVMe storage
- ~1M vectors (1536d)
- pgvector tuned (HNSW)
- HA-ready (Patroni failover)
- Daily backups + 14d PITR
- Priority support
- Custom PostgreSQL config
# faq
drop your data → get a working thing.