Short answer: a weekend project costs about the price of a domain, and a small live app usually lands between 50 and 90 dollars a month once two or three services cross onto paid tiers. The jump is almost never caused by usage. It is caused by a subscription floor: a paid plan you needed for one feature, billed whether or not anyone visits.
Everything below is the provider's own public list price at the time of writing, September 2026. Pricing pages change, free tiers get restructured and regional pricing differs, so treat these as the shape of the problem and confirm the numbers on the provider's page before you commit to anything.
The five, at list price
| Service | Free tier | First paid tier | What actually pushes you up |
|---|---|---|---|
| Vercel | Hobby, for non-commercial projects | Pro, 20 dollars per user per month | Commercial use, team members, bandwidth and function execution above the included allowance |
| Supabase | Free project, pauses after a period of inactivity | Pro, 25 dollars per month | Not wanting the project to pause, plus database size, extra compute and a second project |
| Resend | A few thousand emails a month, with a daily cap | From 20 dollars per month | The daily cap more often than the monthly one, and multiple sending domains |
| Cloudflare Workers | A daily request allowance on the free plan | Workers Paid, 5 dollars per month | Request volume, CPU time, and moving from a toy to a real API |
| Cloudflare R2 | A small monthly storage and operations allowance | Per GB stored plus per operation, no egress charge | Stored volume and how chatty your code is, not how much you serve |
| Twilio | None, trial credit only | Pay as you go | A monthly charge per phone number, a per message charge, carrier fees and US registration |
What the free tiers really cut off at
The headline number is rarely the constraint. Vercel's Hobby plan is generous on bandwidth and restrictive on what counts as commercial, so the moment your project takes money it is a Pro plan conversation. Supabase's free project is a genuinely usable Postgres database, and the thing that pushes people to Pro is not size but pausing after inactivity, which is fatal for a demo link you share occasionally.
Resend and most email providers apply a daily cap as well as a monthly one, so a batch send of two thousand messages fails on a plan that nominally allows several thousand a month. Cloudflare Workers meters per day on the free plan, so a burst of traffic on one afternoon can exhaust an allowance that looks huge in monthly terms.
Read for the unit, not the number. Per day, per project, per user, per domain and per region all change the answer by more than the headline price does.
Twilio is a different shape
Twilio has no free tier, and its pricing is the one that surprises people most because it has four components rather than one. You pay a small monthly rental for each phone number, a per message charge for each outbound SMS segment, a carrier fee that the mobile networks charge on top, and, for sending to US numbers, a registration process called A2P 10DLC with both one-time and recurring costs.
At the time of writing a US local number rents for a little over a dollar a month and a US SMS segment costs well under a cent before carrier fees. Those numbers are small, but the registration is the part to plan for: it takes days, it requires business details, and unregistered traffic gets filtered rather than delivered. A verification code flow you assumed was a two hour job is a two week job if you did not start the paperwork.
Also remember a message longer than 160 characters is billed as multiple segments, and that emoji drop the limit further. Check the current numbers on Twilio's pricing page, and budget the fees rather than the per message rate.
Three realistic monthly totals
The weekend project. Free hosting, free database, free email allowance, a domain. Roughly one dollar a month amortised, plus whatever your coding agent subscription costs, which is usually the largest single line and is easy to forget because it feels like a personal tool.
The small live app. Hosting on a paid plan because it is commercial, a database on Pro because it must not pause, email on the first paid tier, Workers Paid, and a few dollars of storage and model usage. That is roughly 70 to 75 dollars a month at list price for perhaps a few hundred users. Notice that almost all of it is subscription floor rather than metered usage.
The app that sends SMS. Add the number rental, the per message cost and the registration fees. For a few thousand verification codes a month the messaging spend is small, in the tens of dollars, and the operational overhead is large.
The uncomfortable conclusion is that at small scale you are mostly not paying for compute. You are paying five subscription floors, and the way to lower the bill is to remove a vendor, not to optimise a query.
The line nobody counts: your own tools
Before any of the infrastructure, most people building this way are paying for the agent itself. A coding assistant subscription is typically around twenty dollars a month per person, more for the higher usage tiers, and if you also call a model API directly from your application that is a second, separate line with a completely different pricing model. It is worth putting both into the same budget as the infrastructure, because on a small project the tooling frequently costs more than everything it built.
The same goes for the domain, any design or image tool in the loop, and the app store or business registration fees if you ever ship to a store. None of these are infrastructure, all of them are the cost of the app existing, and leaving them out is how a project that felt free turns out to cost a hundred and fifty dollars a month.
Where the bill actually surprises people
- Per seat hosting. Adding one collaborator adds a full seat price on several platforms at once.
- A second environment billed as a second project. Staging often doubles the database line.
- Model API usage inside the product. The one genuinely variable line, and the one an agent can multiply overnight.
- Storage operations. Cheap per operation, and a loop that lists a bucket on every request makes millions of them.
- Abandoned projects. The most common overspend by a distance, and the easiest to fix.
What this looks like on one bill
None of these prices change when you run them through Squiid, which is the point. Metered usage is paid from prepaid credits at the provider's list price with no markup, and subscription plans such as a database Pro plan pass through at the provider's own price with no fee added. Squiid charges separately and visibly: nothing a month on the free plan with a 15 percent fee when you top up credits, 19.97 dollars a month on Solo where that fee starts at 8 percent and falls to 3.5 percent as spend grows, or from 29.97 dollars per seat on Team where the ladder runs a point lower.
So the small live app above stays roughly 70 dollars of provider cost, and you can see all of it in one dashboard, on one invoice, with a balance that pauses rather than overdrawing. Whether the platform fee is worth it depends on how much the five sign-ups, five keys and five invoices are costing you in attention. The list prices are the list prices either way.