FinOps for Developers: Cutting Your Vercel, Supabase and Cloud Bills
November 7, 2026 · 8 min read
Most developers only look at their cloud bill when it surprises them. By then, the money is already spent.
FinOps is the habit of watching, understanding and controlling cloud costs as part of normal development work. This guide shows how Vercel and Supabase charge you, what usually drives the bill, and what you can change today to cut it. Prices below were checked in November 2026, so confirm them on the official pricing pages before you decide.
Quick Summary
Vercel bills Functions on Active CPU, Provisioned Memory and Invocations, so waiting on a database or API does not count as CPU time.
Caching is the cheapest optimization on Vercel, because a cached response does not run your function.
Supabase’s spend cap does not cover compute, and every extra project adds its own compute cost.
Egress, extra projects, add-ons and unused features are the most common sources of surprise bills.
A 30-minute monthly review catches most problems early.
FinOps in Plain Words
You do not need a finance background. Three habits cover most of it:
See it: Know what you pay for, and set budgets and alerts.
Trim it: Remove waste, such as unused projects, extra builds and uncached requests.
Keep it that way: Review usage every month and after every big release.
Part 1: Vercel
How Vercel bills you
On the Pro plan, you pay $20 per month and get $20 of included usage credit. Hobby is free, but it is meant for personal, non-commercial use and cannot buy extra usage. The main meters to watch:
Active CPU: starts at $0.128 per hour. Hobby includes 4 hours per month.
Provisioned Memory: starts at $0.0106 per GB-hour.
Function invocations: start at $0.60 per 1M.
Image optimization: transformations start at $0.05 per 1K, with cache reads and writes billed separately.
ISR: reads start at $0.40 per 1M and writes at $4 per 1M.
Fast Origin Transfer: starts at $0.06 per GB.
Seats: a developer seat is $20 per month on Pro, and viewer seats are unlimited.
Example: what a busy function costs
Say a function uses 100 ms of CPU per request and gets 1 million requests per month. That is 100,000 seconds, or about 27.8 hours of Active CPU, which comes to about $3.56 at list price. The invocations add $0.60. This ignores provisioned memory and your included credit, so treat it as a rough estimate. The point is that CPU time, not request count alone, drives the cost.
8 ways to cut your Vercel bill
1. Make sure Fluid compute is on. New projects use it by default, and it only counts CPU time while your code runs, not while it waits on I/O. Inherited templates and imported configurations can still pin you to the older runtime, so check your project settings.
2. Cache more. If a function response is cached, it does not run, so it costs no invocation and no function duration. In Next.js, use 'use cache' with cacheLife, or static generation, for pages that do not change per user.
3. Set a spend limit. New teams get a default on-demand budget of $200, with email, web and SMS alerts. You can also configure Vercel to pause all projects automatically at 100%. Lower the budget if you are a small project.
4. Control image optimization. Fewer image sizes and a longer cache TTL mean fewer transformations. Next.js 16 already helps: the default image cache TTL went from 60 seconds to 4 hours, and the default quality list was reduced to a single value.
5. Consider Flat Rate CDN on Pro. It gives you a fixed monthly price for the CDN, so traffic spikes do not raise your bill. Read the docs first to see if it fits your traffic.
6. Lower build costs. Basic build machines are $0.007 per minute on Pro, while larger ones cost more, up to $0.105 per minute for Turbo. Use the smallest machine that works, and skip builds for changes that do not affect the app. Turbopack’s disk cache also speeds up repeat builds in Next.js 16.3 and later.
7. Use viewer seats. Designers, managers and clients usually only need to look at previews, and viewer seats are free.
8. Turn off add-ons you do not use. Web Analytics events, Observability events and Speed Insights Plus all add up if you enable them everywhere.
Part 2: Supabase
How Supabase bills you
The Pro plan is $25 per month and includes $10 of compute credit, enough for one Micro instance. Included on Pro:
100,000 monthly active users, then $0.00325 per MAU
8 GB disk per project, then $0.125 per GB
250 GB egress, then $0.09 per GB
250 GB cached egress, then $0.03 per GB
100 GB file storage, then $0.0213 per GB
2 million Edge Function invocations, then $2 per million
Compute is billed per project and by the hour. Micro is $10 per month, Small is $15, Medium is $60, and Large (2 dedicated vCPUs) is $110.
Example: how the bill grows
One Pro project on Micro: $25 per month, because the $10 credit covers the compute.
Add a staging project on Small: about $40 per month.
Move production to Large and keep a Micro staging project: about $135 per month.
The plan fee barely changes. Compute is what moves the bill.
The spend cap gotcha
The spend cap is on by default on Pro. It covers items such as disk size, egress, Edge Function invocations and MAUs, but it does not apply to compute. It is also an all-or-nothing toggle, so you cannot set a dollar budget.
There is a second catch: with the cap on, you are not charged for going over, but your services can be restricted if you consistently exceed the quota. For a production app, decide deliberately. Many teams turn the cap off and watch usage closely instead.
7 ways to cut your Supabase bill
1. Right-size compute. Start small and scale up when you see real pressure. You can change size at any time, and billing is hourly.
2. Do not create projects you do not need. Each paid project adds compute. Use the Free plan for experiments, and delete or pause projects you no longer use. Free projects are paused after one week of inactivity, and you can have two active free projects.
3. Watch egress. Select only the columns you need, paginate large lists, and avoid sending large payloads on every request. Serve public files through Storage’s CDN, because cached egress costs $0.03 per GB compared with $0.09 for regular egress.
4. Keep the database small. Disk beyond 8 GB costs $0.125 per GB. Store files in Storage instead of database columns, and archive or delete old logs and event tables.
5. Use Branching carefully. Branches are billed per hour, so delete branches when you finish with them.
6. Skip add-ons you do not need. Point-in-time recovery starts at $100 per month, a custom domain is $10 per month, and each log drain is $60 per month.
7. Be careful with Realtime and image transformations. Realtime includes 500 peak connections and 5 million messages on Pro, and image transformations include 100 origin images before $5 per 1,000.
Part 3: Cloud Cost Habits That Work Everywhere
Set budgets and alerts on every account. Do this before you deploy anything.
Tag or name resources by project and environment, so you can tell which project is spending.
Delete idle resources. Old staging environments, test databases and unattached storage keep billing.
Match billing to usage. Provisioned servers charge for idle capacity. A 2026 analysis cited in a Vercel comparison put average cluster CPU utilization at about 8%. That comparison comes from a vendor, so check your own numbers, but the idea holds: idle capacity costs money.
Review after every launch. New features change traffic patterns and costs.
Your 30-Minute Monthly Cost Checklist
Open the usage page on Vercel and Supabase and check the top three meters.
Compare them with last month and find the biggest increase.
Check budgets and alerts are still set.
Delete unused projects, branches and preview deployments.
Review add-ons and seats.
Write down one change to make before next month.
Frequently Asked Questions
Is Vercel free for commercial projects?
The Hobby plan is for personal, non-commercial use. Commercial projects belong on Pro.
Does the Supabase spend cap cover compute?
No. Compute is billed per project regardless of the spend cap.
What is Active CPU on Vercel?
It is the CPU time your function actually uses. Time spent waiting on a database or API call is not counted.
What is the fastest way to reduce a Vercel bill?
Cache responses so functions do not run, then check images and build settings.
What is the fastest way to reduce a Supabase bill?
Check egress and the number of projects first, then compute size.
Conclusion
Most bills grow because of small, unseen things: an extra project, an uncached route, an add-on nobody uses. Set budgets, cache what you can, right-size what you run, and review your usage once a month. Check the official Vercel pricing and Supabase pricing pages before you decide, since rates change.