The short version#
Vibecoding solves building. It does not solve shipping.
After two evenings with Lovable, Cursor or Claude Code you have a working thing. Then come the questions no prompt answers: where do the uploaded images live? Why does the page take eight seconds in Brazil? What does this cost me if a thousand people show up tomorrow? And why is my frontend sending every visitor IP to Google, because the model dutifully added a Google Fonts link?
bunny.net covers exactly that gap, at prices where a side project does not hurt. This post sorts out which building block solves which problem, with the currently published prices.
On whether vibecoding holds up at all we wrote something else. This is about the step after.
The actual problem after building#
The usual vibecoding stacks stop where shipping starts. Your host's free tier carries you until the first real traffic. Static assets then sit in the same bundle as the code, uploads land somewhere, and latency outside your home region interests nobody until someone complains.
Those are four separate problems: delivery, storage, compute and privacy. bunny.net has a building block for each, and you can take them individually.
Delivery: the CDN#
Two networks to choose from, and the difference matters for small projects.
Standard Network, 119 locations, billed by region:
| Region | Price per GB |
|---|---|
| Europe and North America | $0.01 |
| Asia and Oceania | $0.03 |
| South America | $0.045 |
| Middle East and Africa | $0.06 |
Volume Network, 10 locations, one global rate: $0.005 per GB for the first 500 TB, then tiered down to $0.002 above 1 PB.
For a side project with a European audience that means 100 GB of delivered traffic costs one dollar. The monthly minimum is $1, so there is no base fee that eats a small project.
The volume tier is half the price but with ten locations instead of 119. Good for downloads and large files, not for interactive applications with a worldwide audience.
Storage: Edge Storage#
This is where the uploads your vibecoded project produces live.
Standard (HDD): $0.01 per GB per region for up to two regions, each additional region $0.005 per GB. Up to nine replication regions.
Edge (SSD): $0.02 per GB per region, up to 15 regions.
Two details that make the difference, and that you know painfully differently from the large providers: there are no API egress charges and none per request. And traffic from Edge Storage to the Bunny CDN is free. So you do not pay twice when an image travels from storage through the CDN to the user.
Anyone who has taken apart an S3 bill knows the request and egress line items are the surprise, not the disk space.
Compute: Magic Containers#
If your project needs a backend rather than only static files, Docker containers run here across 41 regions.
| Item | Price |
|---|---|
| CPU | $0.02 per core per hour |
| RAM | $0.005 per GB per hour |
| Storage | $0.10 per GB per month |
| Egress | $0.01 to $0.06 per GB by region |
A continuously running small container with one core and one GB of RAM lands around $18 per month. That is no bargain against a hobby tier, but it is an honest price for something that runs permanently and can drive several containers with shared storage as one application.
Privacy: Bunny Fonts#
The building block that saves the most trouble in the German-speaking market, and costs nothing.
Code-generating models reliably put a Google Fonts link in the head. That sends every visitor's IP address to Google on every page load, and that was precisely the basis of the German Google Fonts warning-letter waves.
Bunny Fonts is a Google Fonts API-compatible alternative: you swap the CSS import or the link tag, done. No account needed, permanently free, built and hosted in Europe, and per the vendor without logging, cookies or third-party sharing.
This is the one item from this post worth doing even if you use nothing else from bunny.net. It is a find and replace.
Combinations that make sense#
Static site with a few images. CDN Standard plus Bunny Fonts. Realistically under $2 a month.
App with user uploads. Single-region Edge Storage plus CDN. Images move free from storage into the CDN, and you pay storage and delivered traffic separately and traceably.
Project with its own backend. Magic Containers for the API, storage for the files, CDN in front. From here it is worth watching the egress region, because it drives the price harder than compute time does.
Video in the project. Bunny Stream exists as a separate product for that. We did not check its terms, so no number appears here.
Where it does not fit#
bunny.net is infrastructure, not an application host. There is no git-push deployment, no preview environment per branch, no built-in database with auth the way Supabase does it. If you want the convenience of Vercel or Netlify, you will not find it here.
The case where it pays off is the other one: you already have a host that handles deployment, and you want to pull assets, uploads and delivery out of it because they are expensive or inflexible there.
What this post does not cover#
We took the prices from the public pricing pages and did not settle a bill ourselves. What a real monthly invoice comes to depends on the usage profile, and the example figures above are back-of-envelope estimates, not quotes.
We did not examine Bunny Stream, Bunny Shield, Edge Scripting, Bunny DNS or the SQLite-compatible Bunny Database. The products exist, but without our own check we write no assessment of them.
Also open: a defensible price comparison against Cloudflare R2 and Amazon S3. That needs a defined load profile, otherwise you compare tariff lines instead of invoices. That is its own post.
Disclosure: the link to bunny.net is an affiliate link. That changes nothing about the prices quoted or the assessment; the terms come from the vendor's public pricing pages.
