Leaving Brewless. Nothing to move.
Your Laravel app runs in your own Scaleway and bunny.net accounts from the first deploy. Leaving means taking Brewless away, not moving your app: export, detach, and it keeps serving.
What is already yours
Most of what makes leaving a hosting platform hard never sits at Brewless in the first place.
The infrastructure
Containers, database, buckets, queues, registry and DNS are created in your own Scaleway project and bunny.net account.
The data
Your database and files never live at Brewless. They stay in your project, in the region you picked, so there is nothing to download from us.
The contract
Scaleway and bunny.net bill you directly, at their own prices. Ending Brewless does not end those contracts.
The secrets
They are in your own Secret Manager. Brewless keeps their names and revisions, never their values.
Three steps out
Each step works from the command line and from the console, and none of them touches what serves your visitors.
1. Export
Everything Brewless knows about an environment, as files: resources, domains, releases, the names of the variables and a README on deploying without Brewless. Exporting changes nothing, so run it any time.
brewless export production2. Take it over with Terraform
The export holds a main.tf that imports every resource as it is. With your own provider keys, terraform plan imports them and wants to change nothing.
terraform init
terraform plan3. Detach
Brewless stops deploying, rolling back, scaling and watching the environment. A last export is made first, and nothing at your providers is touched.
brewless detach productionWhat stops and what keeps running
Detaching ends what Brewless does. What your app needs to serve stays where it is.
| Stops | Keeps running |
|---|---|
| Deploying and rolling back through Brewless | Your containers and what they serve |
| Scaling through Brewless | Your database and its data |
| Watching for changes made elsewhere | Your domains and certificates, renewed by your providers |
| The test address under brewless.dev | The trigger that calls your worker every minute |
| Your secrets, in your own Secret Manager |
A database capacity boost that Brewless started gets its normal capacity back before the environment is let go, so no boost keeps running, and costing, with nobody to end it.
After that, a release is three plain calls to your provider: build and push an image, run the release container with it, and give the web and worker containers the same image. The command line client and the Laravel package that answers those calls are open source.
The terms when you switch
This is what our terms and our software already do today. Nothing here is a promise for later.
No exit or switching fee
Leaving costs nothing at Brewless. Exporting and detaching are free on every plan, the free plan included.
Stop at the end of any period
You can end the agreement at any moment, with effect at the end of the period you paid for. There is no other notice period.
Export before or when you stop
As often as you like, also just to see what Brewless holds. No secret values are in it: those never left your Secret Manager.
Ending never touches your accounts
What runs in your Scaleway and bunny.net accounts stays running. When your organisation ends, its data at Brewless is removed within 30 days; invoices are kept as tax law requires.
Open formats
The export is JSON and Terraform, and your provider keys are yours to revoke at Scaleway and bunny.net.
Coming back
The environment, its releases and the audit trail stay as a record. You adopt the resources again on the Resources page.
What the EU Data Act says about switching
The EU Data Act (Regulation (EU) 2023/2854) has rules for switching between cloud and other data processing services. They apply since 12 September 2025. In short:
Notice of at most two months
A customer can start a switch with a notice period of no more than two months.
A transition of 30 days
After the notice, the provider supports the switch for up to 30 days, and the customer gets at least 30 more days to retrieve their data.
Switching charges go
Until 12 January 2027 a provider may charge at most its own costs of a switch. From that date, charges for switching, egress included, are not allowed.
Exportable data
The provider has to make the customer's data and digital assets exportable, in a structured, commonly used and machine-readable format.
This is a summary for orientation, not legal advice. The text in the Official Journal is what counts.
What the EU Data Act means for your Laravel hosting The Data Act on EUR-Lex
Read more
Leaving Brewless, step by step Laravel hosting without lock-in How to host a Laravel app EU-sovereign