What each week held
Read in 2 of the last 12 weeks. The other 10 were not read at all, and are drawn empty rather than as quiet.
The bar is observed claims in that week. A dashed marker is a week this company was not read at all — not a quiet one. Inferences and failed reads are in neither.
What it declares
- Postgres database
- Authentication
- Storage
- Edge Functions
- Realtime subscriptions
- Compute credit/spend cap controls
- SOC2/HIPAA compliance (Team/Enterprise)
As the company’s own pages describe it. Forge did not test any of these.
What users raised
The reading listed none.
Everything on record
6 observed claims, and 1 inference counted apart from them. Newest first; the tag on each row is what kind of claim you are reading.
- PRICINGINFERENCEOct 1, 2026
Core Supabase Pro ($25/mo) and Team ($599/mo) base pricing and standard usage meters (storage, egress, MAU rates) remain unchanged from the prior ledger entry as of September 2026 across multiple independent trackers.
makerkit.dev/blog/saas/supabase-pricing - PRODUCTFACTOct 1, 2026
Supabase is retiring the logs.all Management API endpoint on September 23, 2026 in favor of a new logs endpoint, requiring integrators to migrate.
Developers with scripts/integrations calling logs.all must update before the cutover or lose functionality.
github.com/supabase/supabase/pull/49656 - PRICINGFACTOct 1, 2026
Supabase is preparing to launch dedicated, finalized Logs Ingest pricing (plan quotas, overage rates, and billing examples) as a new metered line item, with the formal announcement embargoed until approximately September 15, 2026.
Adds a new usage-based cost dimension (log ingestion) for Pro/Team customers that didn't exist as a distinct billed item before, affecting anyone relying on Supabase's logging/observability features.
github.com/supabase/supabase/pull/49656 - COMPLAINTUSER OPINIONSep 2, 2026
Users report that heavy Lovable usage can burn through 100 monthly credits in a single debugging session, pushing real spend well past the advertised $25 sticker price, and some reviewers suggest weighing Lovable against flat-pricing alternatives like Cursor or Replit.
Baseline complaint theme in the adjacent AI-builder space around credit-based pricing unpredictability, useful context for Supabase's own usage-based billing narrative
www.eesel.ai/blog/lovable-pricing - PRICINGFACTSep 2, 2026
Lovable (an adjacent AI-app-builder tool sometimes discussed alongside backend platforms) uses a credit-based pricing model: Free gives 5 credits/day (about 2-4 prompts), and Pro starts at $25/month for 100 monthly credits, with actual spend varying heavily based on build complexity and AI error-driven credit burn.
Baseline positioning contrast: Lovable's usage-unpredictable credit model versus Supabase's flat-plus-metered-overage model, relevant if Supabase or competitors emphasize pricing predictability as a differentiator
www.eesel.ai/blog/lovable-pricing - PRICINGFACTSep 2, 2026
Paid Supabase plans include $10/month in compute credits covering one Micro instance, and the Pro Plan has a spend cap enabled by default to prevent runaway usage bills.
Baseline for how Supabase controls and communicates usage-based overage risk to buyers
supabase.com/pricing - PRICINGFACTSep 2, 2026
Supabase's current pricing structure is Free ($0, 2 projects, 500MB database, 50,000 MAUs, 5GB egress, auto-pause after 1 week idle), Pro ($25/month bundling Auth, Storage, Edge Functions, Realtime, and Postgres), Team ($599/month with higher MAU limits, SSO, audit logs), and custom-priced Enterprise with HIPAA and BYO-cloud options.
Establishes the baseline pricing rollup against which future Supabase pricing/packaging changes will be measured
supabase.com/pricing
A record of what Forge read in public about Supabase — its own pages and what people wrote about it. Nothing here is a test of the product, a ranking or a score, and Forge has no relationship with this company.