What Is Brewless? The Beginner's Guide to Serverless Laravel Hosting on European Clouds

CodexFuse Team · 2026-11-05T09:43:51.325Z · 15 min read min read

What Is Brewless? The Beginner's Guide to Serverless Laravel Hosting on European Clouds

What Is Brewless, Exactly?

If you searched for what is brewless, the short answer is that Brewless is a deployment platform that runs a Laravel app serverless on European-owned clouds, in cloud accounts you own yourself. It puts your app on Scaleway Serverless Containers, puts a European edge network in front of it, and charges from €15 a month for the control plane that builds, releases, and scales it. Your code, your data, and your cloud bills stay in your own accounts, and Brewless never sits in the path of your visitors' traffic.

This brewless explained guide covers the product only, and every fact in it comes from the Brewless homepage, its EU-sovereign tutorial, or its public CLI repository, all fetched on November 5, 2026.

Brewless Laravel hosting is serverless in the plain sense of the word: containers start when a request arrives and go away when traffic goes quiet. AWS calls this model Lambda, and Brewless uses the same idea with Scaleway Serverless Containers instead.

The same idea of a small, standard tool that any program can use shows up across the CodexFuse toolbox: a SHA-256 hash generator turns any input into a fingerprint any tool can check. If the app you deploy runs on a server rather than your laptop, it usually lives on VPS hosting, where you control the software it runs.

Why EU Sovereign Laravel Hosting Exists

EU sovereign Laravel hosting exists because some Laravel teams want more than a data centre inside the EU: they want the company that runs it to be European too. Brewless argues that a European region of an American cloud is still run by a company that must answer to US law, and that the US CLOUD Act lets US authorities require a US company to hand over data it controls, wherever in the world that data is stored.

The vendor's definition has three parts, and all three must hold. The data must sit in the EU, the provider must be owned and headquartered in the EU, and the contract must be in your own name.

That is the whole pitch in one line. Brewless is a Laravel-only deployment tool built for teams that accept this definition and want their app to live by it, without managing servers themselves.

How Does Brewless Work? The Own-Accounts Model

Brewless works as a control plane, not as a host. You hold the contracts with both cloud providers directly, you pay them directly for what your app uses, and Brewless only builds, deploys, and watches the app that runs inside your accounts.

The own-accounts model is the whole value proposition, so it is worth stating plainly. Your code goes from your machine straight into your own Scaleway project and is built there. It never passes through Brewless, your secrets stay in your own Secret Manager, and visitor traffic goes from the edge straight to your containers.

Brewless charges separately for deploying and running the app, and it adds nothing on top of your cloud bill. If you cancel, you stop paying for the control plane only: the deploys, release history, rollback, dashboard, audit trail, and drift checks go away, and the app itself keeps running where it is.

The model also gives you a clean exit. A single command, brewless export production, exports everything Brewless knows as a folder with Terraform, and brewless detach production stops Brewless managing an environment while it keeps running.

The Two Clouds Under the Hood: Scaleway and bunny.net

Brewless deploys Laravel to Scaleway and puts a European edge network in front of it. Scaleway is a French company, headquartered in Paris, and its edge partner is a Slovenian company, headquartered in Ljubljana, so both providers are European companies under European law.

Scaleway runs the app itself. Serverless Containers run the web app, the release commands, the queue worker, and the scheduler, while Serverless Jobs build each release inside your own project.

The edge layer is optional, and recommended. It handles DNS, the CDN, TLS certificates, and Shield, its firewall, and its edge locations can be limited to Europe.

The Brewless CLI: From Install to First Deploy in Five Steps

The Brewless CLI is the main way you drive a deploy. It is a public, MIT-licensed command-line client, and its repository on GitHub was created on October 7, 2026, which makes the product 29 days old at the time of writing, with 126 commits and 38 releases behind it.

1. Install it with composer global require brewless/cli. You need PHP 8.3 or newer and git on the machine.
2. Sign in with brewless login acme, where acme is your organisation name. You approve the sign-in in the console, and the token it gives your machine lives for 90 days.
3. Run brewless init in your Laravel project. It reads composer.json, asks which environments, region, database, and queue setup you want, creates them in your Scaleway project, and writes a brewless.yml that you commit. The file holds no secrets.
4. Push your environment variables with brewless env:push production. They go into your own Scaleway Secret Manager, and Brewless keeps only their names and revisions, never their values.
5. Deploy with brewless deploy production. Only what is committed is deployed, the migrations run as their own step, and the new release goes live only after it answers healthy.

Coming from Vapor, brewless init reads your vapor.yml and writes the matching brewless.yml, and it prints anything it cannot carry over, with what to do instead. Nothing at Vapor or AWS is read or changed.

The CLI-first workflow will feel familiar if you already drive projects from the terminal. Our guide on how to use Claude Code covers a similar agent-driven way of working from the command line.

What Happens During a Deploy?

A deploy has five stages, and a failure at any stage before the switch leaves the old release live. The current commit is packed with git archive, so only committed code ever ships.

The archive is uploaded straight into a private bucket of your own Scaleway project through a link valid for fifteen minutes, and the source never passes through Brewless. A job in your project then builds the image and pushes it to your registry.

Release commands, including migrations, run on the new image next. If a migration fails, nothing changes for visitors, and the old release stays live. The web container then switches to the new image, must answer healthy, and only then do the workers follow.

Which Regions Can You Deploy To?

Brewless deploys to four Scaleway regions, and you pick one per environment with a single line in brewless.yml. Paris, Amsterdam, Warsaw, and Milan are the options, and your containers, database, queue, and bucket all go to the region you pick.

Paris has the most, because the serverless database, which sleeps when nobody asks, is only available there so far. In the other regions you use Managed PostgreSQL, and Queues are not in Warsaw or Milan yet.

The region choice is also a sovereignty choice. The app and database sit in the region you picked, and the vendor's own example puts both in Amsterdam, but the edge provider answers DNS lookups from its worldwide network, which the vendor flags itself.

What Does Brewless Cost? Two Bills, Not One

Brewless costs from €15 a month, and that figure is the Solo tier of the control plane, not the total cost of hosting. The cloud bill from both providers is separate, pay-as-you-go, and billed to you directly.

All prices are per month and exclude VAT, and every plan includes unlimited environments. Pay per year and you get two months free, so Solo costs 10 × €15 = €150 a year instead of 12 × €15 = €180, a saving of €30, and Business costs 10 × €49 = €490 instead of 12 × €49 = €588, a saving of €98.

One application is free to try, production included, with no credit card, and you start paying when you want your own domain or more. Teams that start now keep the launch price for as long as they stay, according to brewless.eu.

The cloud bill itself is driven by use: the app and workers by use, the serverless database by use and nothing while it sleeps, a managed database node at a fixed amount plus storage, and the CDN per gigabyte delivered. A quiet app can therefore cost very little beyond the €15, while a busy one will not.

Brewless vs Vapor vs Forge vs Bref: Which Fits Your App?

The brewless vs vapor question is really a question about which cloud your app runs on. Both deploy Laravel serverless, but Vapor runs on AWS Lambda, an American cloud, while Brewless runs on Scaleway, a French one, and that difference is the whole point of Brewless.

The brewless vs forge question is a different one, because Forge is not serverless at all. Forge provisions and manages VPS servers that you keep running around the clock, while Brewless and Vapor both scale to zero when traffic goes quiet.

Vapor's Unlimited plan costs $39 a month, or $399 a year, which is $69 less than 12 × $39 = $468, and AWS costs sit on top of that. Forge's Hobby plan costs $12 a month, Growth $19, and Business $39, with the server bill separate, and all three prices were verified on Forge's own pricing page on November 5, 2026.

Bref is the do-it-yourself route: it runs PHP on Lambda through runtimes you deploy yourself, with no control plane to pay for. That freedom costs your time instead, which is why most teams pick a platform and pay for it.

What Changes When Laravel Goes Serverless?

Serverless changes where Laravel keeps state, and almost nothing else. A serverless container keeps nothing on its own disk between requests, and two copies of your app do not share one, so anything that must survive a request has to live outside the container.

Sessions and cache go in the database, which is Laravel's default since version 11, or in Redis. If your .env still says file, change it to SESSION_DRIVER=database and CACHE_STORE=database, and add the sessions and cache tables with php artisan make:session-table and php artisan make:cache-table on an older app.

Files go on the s3 disk, because Scaleway Object Storage speaks the S3 API, so Laravel's own s3 disk works as it is, with FILESYSTEM_DISK=s3 and the AWS_* variables that Brewless sets when it creates the bucket. You also need composer require league/flysystem-aws-s3-v3 "^3.0" and composer require brewless/laravel.

Queues, the scheduler, and migrations keep working as they are. The scheduler is read from your app on each deploy, the worker is called only at the moments a task is due, and jobs are handed to the worker the moment they are queued.

Cold starts are the trade-off. Containers start when a request comes in, so the first visitor can wait, and Brewless answers that by letting you set a minimum replica count, so one container stays warm through the night. That warmth costs money, which is the honest price of removing the wait.

Outside events still reach the app the usual way. A payment confirmation or a form submission often arrives as a webhook, and our explainer on what a webhook is covers how those callbacks reach a serverless app.

The Weakest Link: When "EU-Sovereign" Is Not the Whole Story

Sovereignty is only as strong as the weakest link, and Brewless says so itself. If your app sends mail, payments, or analytics through a service outside the EU, that data leaves the EU, and Brewless will not call your setup fully sovereign when it is not.

The vendor names the usual suspects. Mail can go through an EU provider, and Brewless itself sends its mail through Lettermint, while Mollie in the Netherlands is the obvious payment choice for Laravel apps in Europe. Analytics should be a cookieless, EU-hosted tool, or none at all.

Two more gaps are easy to miss. The edge provider answers DNS lookups from its worldwide network, so those lookups see your account details, though not your visitors' traffic, and your team's own tools, from source hosting to chat to a developer's laptop abroad, are a separate question from where the app runs.

None of this makes the sovereignty argument empty. It makes it a spectrum, and the honest version of Brewless is a platform that keeps the app itself inside EU-owned clouds while leaving the rest of the chain up to you.

Who Should Use Brewless — and Who Should Not

Brewless fits Laravel teams that want serverless hosting and care who owns the cloud it runs on. If your customers, your regulator, or your own principles ask for EU-owned infrastructure, and you run Laravel and nothing else, it is the shortest path to that setup.

It also fits teams leaving Vapor for sovereignty reasons, because brewless init can read a vapor.yml and write the matching brewless.yml. The migration is a conversion, not a rewrite, though anything the converter cannot carry over is printed once, with what to do instead.

It does not fit everyone. If your app is not Laravel, Brewless says so plainly: it is Laravel-only on purpose, and it is not for you. If you need WebSockets through Reverb, that support is planned, not shipped, and if you need a track record, remember the CLI repository is 29 days old and the product's tutorial is 10 days old.

If your bottleneck is throwaway sandboxes for agent runs rather than hosting, see how to use E2B for that job instead. Brewless deploys production apps; it is not a sandbox.

The verdict is simple: Brewless is a young, honest, narrowly focused tool, serverless Laravel on European-owned clouds, in accounts you own, with a clean exit. For the teams it is built for, that is enough, and for everyone else, Vapor, Forge, or Bref is the better call.

Sources

All sources were fetched on November 5, 2026. Prices and product details are as stated on those pages on that date.

• Brewless homepage, including pricing and architecture — brewless.eu
• Brewless tutorial, "How to host a Laravel app EU-sovereign", published October 26, 2026 — brewless.eu/blog/eu-sovereign-laravel-hosting
• Brewless CLI repository, MIT licence, created October 7, 2026 — github.com/brewless/cli
• Laravel Vapor homepage, including pricing — vapor.laravel.com
• Laravel Vapor documentation, introduction — docs.vapor.build/introduction.html
• Laravel Forge homepage — forge.laravel.com
• Laravel Forge pricing — forge.laravel.com/pricing
• Bref homepage — bref.sh
• Scaleway Serverless Containers — scaleway.com/en/serverless-containers
• bunny.net homepage — bunny.net
• Scaleway company facts — Wikipedia: Scaleway
• bunny.net company facts — CB Insights: bunny.net

Frequently Asked Questions

Is Brewless the same as Laravel Vapor?

No. Both deploy Laravel serverless, but Vapor runs on AWS Lambda, an American cloud, and costs $39 a month plus AWS usage, while Brewless runs on Scaleway Serverless Containers, a French cloud, with a European edge network in front, and costs from €15 a month plus cloud usage. The difference that matters is sovereignty: Vapor keeps your app under US law, Brewless keeps it under European law.

How much does Brewless cost in total?

The Brewless control plane starts at €15 a month for Solo, and your Scaleway and bunny.net usage is billed separately, directly to you. A quiet app costs little beyond the €15, because the serverless database charges nothing while it sleeps and containers scale to zero, while a busy app pays for what it uses. One application is free to try, production included, with no credit card.

What happens to my app if I cancel Brewless?

It keeps running. Everything is set up in your own Scaleway and bunny.net accounts, so cancelling only stops the control plane: the deploys, release history, rollback, dashboard, audit trail, and drift checks. You can also export everything Brewless knows as Terraform with brewless export production, or detach an environment with brewless detach production.

Does Brewless work with my existing Laravel app?

Yes, if it is Laravel. Brewless is Laravel-only on purpose, reads your schedule from the app, and runs your migrations on every deploy. You need to store sessions and cache in the database or Redis instead of files, and put files on the s3 disk, because a serverless container keeps nothing on its own disk between requests.

Can I deploy Laravel Scaleway-only, without bunny.net?

Yes. The edge layer is optional, though recommended, because it adds the CDN, DNS, TLS certificates, and Shield firewall in front of your app. Without it, your app still runs on Scaleway Serverless Containers in your own account, and you arrange DNS and certificates yourself.