Is it cheaper to run our entire backend on AWS RDS or switch to a managed Supabase instance given our current database size of fifty gigabytes?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
Is it cheaper to run our entire backend on AWS RDS or switch to a managed Supabase instance given our current database size of fifty gigabytes?
2 real searches · 1 real-search pass
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
ChatGPT real searches (2)
Classes come from the query-classifier (a local Laya model). 2 of 2 calls are low-confidence (under 50%) — hover a query in the table to see its confidence.
Searches and sources
ChatGPT2 real searches · gpt-6
2026 AWS RDS PostgreSQL pricing instance storage gp3 backup pricing official AWS Google ↗
2026 Supabase pricing Pro Team compute disk storage egress official Google ↗
- Pricing & Fees · supabase.com
- Compute and Disk · supabase.com
- Manage Disk size usage · supabase.com
- About billing on Supabase · supabase.com
- Amazon RDS for PostgreSQL Pricing · aws.amazon.com
- Managed Relational Database - Amazon RDS Pricing · aws.amazon.com
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
2026 AWS RDS PostgreSQL pricing instance storage gp3 backup pricing official AWS OBSERVED | Google ↗ AI Mode ↗ | — | Comparison | — | — | 1x of 1 | |
2026 Supabase pricing Pro Team compute disk storage egress official OBSERVED | Google ↗ AI Mode ↗ | — | Other / navigational | — | — | 1x of 1 |