Supabase moves logs to usage-based pricing, with billing from early 2027

Supabase announced on September 25, 2026 that it is moving logs to usage-based pricing. You will pay for the volume of log data your project’s services produce, above a monthly allowance. Billing waits for a grace period that runs to the start of 2027. Supabase says more than 90% of projects are within the included limits.

What it will cost

Plan	Log ingest included	Above the allowance
Free	1 GB a month	Not billed
Pro	20 GB a month	$0.50 per GB
Team	20 GB a month	$0.50 per GB
Enterprise	20 GB a month	$0.50 per GB

Ingest is billed per byte, not rounded up to whole gigabytes, and shows on the invoice as “Logs Ingest”. The docs give an example: 27.48 GB in a month on a paid plan is 7.48 GB over, which costs $3.74.

Reading logs has a quota too

Querying logs isn’t billed separately, but it has a monthly allowance of 100 times your ingest. The Free plan’s 1 GB of ingest gives 100 GB of queries; a paid plan’s 20 GB gives 2,000 GB. If you go over, log access is degraded for the following month and returns to normal at the next billing cycle.

Who pays

On a paid plan with the Spend Cap turned off, and on Team or higher, overage is billed. On the Free plan, or on a paid plan with the Spend Cap on, Supabase sends a notice to your billing email and you enter a grace period instead.

During the soft launch, the dashboard shows your log usage but limits are not enforced. The changelog says organizations created after September 25, 2026 may get a separate go-live date, and the grace period isn’t guaranteed for them.

What to do

Open the usage page in the Supabase dashboard and check your log ingest for the last few months. If a project is near or above 20 GB, find out which service produces most of it before billing starts in early 2027.