What our catalogue holds
These are curated rows, not readings. We state no difference between the two columns because we have not checked either of them.
| Catalogue field | AWS S3 | Supabase Storage |
|---|---|---|
| Category | Storage | Storage |
| Where it runs | Object Storage | Object Storage |
| Pricing string, uncheckedWrong on 43 of our 190 rows. Not a price of ours. | Free (5GB 12mo) / $0.023/GB-mo | Free (1GB) / Included in Pro |
| Vendor page | aws.amazon.com | supabase.com |
What this page does not answer
We have not researched AWS S3 or Supabase Storage, and we track neither repository. Our catalogue holds a name, a category and a link for each, and nothing else that we have checked: no commit history, no licence, no release and no confirmed price. So this page states no difference between the two and names no winner, and we ask search engines not to index it until one of them has data. Tools enter the pipeline in the order people search for them, and this page changes on the next build after that happens.
How we check this page
We publish a fact only with the source we read it from and the date we read it. This page holds neither, so it holds no fact of ours.
Related comparisons
Pairs we can answer for come first.