MongoDB Atlas Vector Search vs Supabase Vector (pgvector) pricing
Both are in vector database apis. MongoDB Atlas Vector Search is billed atlas cluster consumption-based; Supabase Vector (pgvector) is billed bundled in postgres plan (storage-based). Numbers below are copied from each vendor's pricing page.
MongoDB Atlas Vector SearchFree tier or trial
- Free tier
- M0 cluster: 512MB storage, shared
- Billed
- Atlas cluster consumption-based
- Best for
- Vector search inside operational MongoDB
- Verified
- Jun 27, 2026
Supabase Vector (pgvector)Free tier or trial
- Free tier
- Free project: 500MB DB, pgvector included
- Billed
- Bundled in Postgres plan (storage-based)
- Best for
- Postgres-native embeddings, no separate service
- Verified
- Jun 27, 2026
MongoDB Atlas Vector Search plans
| Plan | Price | What it covers |
|---|---|---|
| Free (M0) | $0/mo | 512 MB storage, shared RAM/vCPU; for learning and prototyping. Vector Search available on shared tiers with limits. |
| Flex | $8-$30/mo | Usage-based ($0.011-$0.041/hr), 5 GB storage, tiered by ops/sec; for dev/test and unpredictable traffic. |
| Dedicated (M10+) | from $0.08/hr (~$57/mo) | M10 = 2 vCPU / 2 GB RAM; scales to M300 (96 vCPU / 384 GB) at $21.85/hr. Required for production with 99.995% SLA. |
| Vector Search Nodes (High-CPU) | $0.12-$3.26/hr per node | Dedicated search compute, billed separately, two-node minimum. S20 ($0.12) to S80 (64 vCPU / 128 GB, $3.26). |
| Vector Search Nodes (Storage-optimized) | ~$1.04/hr for s50 (2 nodes) | s50 = 32 GB RAM / 4 vCPU used in MongoDB benchmarks for scalar-quantized 15.3M-vector workloads. |
- Pricing is the most common complaint across G2/PeerSpot - expensive and hard to predict versus self-hosting
- HNSW indexes need ~1.2-1.5x raw vector size in RAM and must fit in memory, making memory planning critical and upgrades costly
- Production vector workloads require separately-billed Search Nodes with a two-node minimum, adding base cost
Source: https://www.mongodb.com/pricing
Supabase Vector (pgvector) plans
| Plan | Price | What it covers |
|---|---|---|
| Free | $0/mo | 2 active projects, 500 MB database storage each, 50,000 MAU; pgvector available; projects paused after 1 week of inactivity. No uptime SLA. |
| Pro | $25/mo per org | 8 GB database, 100 GB storage, 100K MAU included; includes $10/mo compute credits (covers one Micro instance); usage-based overages; daily backups. |
| Team | $599/mo per org | Pro features plus SOC2 / ISO 27001, SSO, audit logs, 14-day PITR backup retention, and priority support. |
| Enterprise | Custom | Custom pricing with designated support, HIPAA, BYO-cloud options, and the 99.9% uptime SLA with service credits. |
- Good query latency requires the index to fit in RAM, pushing you to larger, costlier compute add-ons
- Performance degrades and p99 tail latency grows beyond roughly 5–50M vectors on a single node, not ideal for billion-scale search
- A real 99.9% uptime SLA is Enterprise-only; lower tiers get no contractual guarantee
Source: https://supabase.com/pricing