bunny.net Edge and CDN
bunny.net puts a CDN, TLS certificates, DNS and a firewall in front of your app. Brewless uses it as the edge: pages that are the same for everybody are answered there, so your container can sleep.
By BunnyWay, Slovenia. Brewless sets this up on a deploy.
What Brewless does
A pull zone in front
Brewless sets up a pull zone in your own bunny.net account in front of the web container, routed through the EU only and accepting TLS 1.2 and newer.
Public pages at the edge
A page that is the same for every visitor is kept for an hour by default; every release empties the edge.
Warmed after a release
After a release goes live, every page of the sitemap is asked once through the edge, so crawlers find them in the cache.
Built files from storage
The built CSS and JavaScript go to a storage zone and are served from there, not from your container.
What you do
- Connect bunny.net on the Providers page.
- Keep public pages free of cookies and sessions, so the edge may keep them.
- Set edge.cache in brewless.yml if an hour is not right for you.
In your project
environments:
production:
edge:
cache: 1hQuestions
- Do visitors pass through Brewless?
- No. Visitors go from bunny.net straight to your containers at Scaleway. Brewless is never a hop for their traffic.
- Which pages does the edge keep?
- A GET without cookies or Authorization that is answered without a cookie, a session or a Cache-Control of the application's own. The documentation lists the rules.
Read more
Documentation The full guide on the blog bunny.net website
Other integrations
Lettermint Scaleway Transactional Email Scaleway Object Storage Mollie Meilisearch ClearAnalytics
Facts about the company checked on 5 November 2026.
Try Brewless with your Laravel app
Brewless is free to try with one application, production included; you start paying when you want your own domain or more. Register and deploy today.