# Cancel Brewless. See what stops.

Brewless deploys into Scaleway and bunny.net accounts you own. The infrastructure, the data and the contracts are in your name, and your app keeps serving if you stop using Brewless.

Almost nothing stops. Your app, its database, its files and its domain are in accounts that belong to you, and they keep running exactly as they were. What you lose is the deploying, not the app.

## Yours, and ours.

Every resource Brewless creates is made inside your own Scaleway project and your own bunny.net account. We hold the control plane, and that is the whole of what you stop paying for.

|  | Yours | Ours |
| --- | --- | --- |
| The app | The containers, their image and the registry they come from. | The deploy that put them there. |
| Data | Database, cache, queues, buckets and backups. | Nothing. We never hold a copy. |
| Secrets | Your Scaleway Secret Manager, with every revision. | The names and which revision is live. |
| The domain | Your DNS zone, your records and your certificates. | The automation that asked for them. |
| Billing | Scaleway and bunny.net invoice you directly. | One plan fee, from us. |
| History | What is live right now. | Release history, rollback, audit trail and drift checks. |

## Why it is built this way.

Owning the accounts is not a detail of the billing. It changes what happens to you in the cases that actually hurt.

- **If we disappear** — Your app keeps serving. Brewless is not in the path of visitor traffic, so there is no request of yours that depends on us being up, let alone on us still existing.
- **If you outgrow us** — You take the accounts and keep going. There is no migration out, because there is nothing of yours to migrate: it is already where it would end up.
- **If a client asks who holds their data** — You can answer with your own company name and a named provider per service, instead of explaining a chain of resellers.
- **If the bill grows** — You see the provider’s own prices on your own invoice. Brewless takes no percentage of it, so nothing about our fee moves when your traffic does.

## Leaving, step by step.

The EU Data Act gives cloud customers a right to switch with limited notice and a thirty-day transition. Here, leaving is mostly a matter of taking the keys back.

- Export what Brewless made as Terraform, so you have the whole setup written down in a form another tool or another team can pick up.
- Detach the application. Brewless stops managing it and stops deploying it, and every resource stays exactly where it is, running.
- Disconnect the provider keys you gave us, so nothing of ours can reach your accounts any more.
- Keep deploying however you like. The containers, the registry and the image are ordinary Scaleway resources at that point, and your domain never moved.
- There is no exit fee and no notice period beyond the month you are in.

## What we need from your accounts.

Brewless works through keys you create and can revoke. Nothing is hidden, and every mutation is written to the audit trail.

- **A Scaleway key** — Scoped to the project the application lives in, so an application cannot reach anything else in your organisation.
- **A bunny.net key** — For the pull zone in front of your app, your DNS zone and the certificates.
- **Nothing destructive by surprise** — A deploy shows a plan of what it will change before it changes it, and anything that removes a customer resource asks first.
- **Revocable at any moment** — Remove the key and Brewless can no longer act. Your app does not notice, because it was never reaching us in the first place.

## Questions about ownership

### What happens to my app if I stop paying Brewless?

It keeps serving. The containers, the database, the files and the domain are in your own accounts and nothing about them depends on us. You lose deploying, rollback, the release history, the audit trail and the console, and you keep the running application.

### Do I need my own Scaleway and bunny.net accounts?

Yes, and that is the point. Brewless deploys into accounts you create and connect, so the resources, the data and the contracts are in your name. Both providers bill you directly at their own list prices.

### Is there an exit fee or a notice period?

No exit fee, and no notice beyond the month you are in. The EU Data Act also sets a right to switch with a thirty-day transition, and from 2027 bans switching charges; because your app already runs in your own accounts, there is nothing here for either of those to undo.

### Can I get the whole setup as code?

Yes. Brewless exports everything it made for an application as Terraform, so the project, the containers, the database, the buckets and the DNS are written down in a form you can keep, review or hand to another team.

### Does Brewless hold a copy of my data?

No. The database, the cache, the buckets and the backups are all in your own Scaleway project. We hold your settings, your release history and your audit trail, and we never store the values of your application secrets.

### Can Brewless delete something of mine?

Only where you asked for it. A deploy shows a plan before it acts, anything that would remove a customer resource asks first, and every mutation lands in the audit trail with who asked for it and when.

## Read more

- [Leaving Brewless, and what the EU Data Act says](https://brewless.eu/exit)
- [Laravel hosting without lock-in](https://brewless.eu/blog/laravel-hosting-without-lock-in)
- [What the EU Data Act means for your Laravel hosting](https://brewless.eu/blog/eu-data-act-laravel-hosting)
- [How Brewless is secured](https://brewless.eu/security)
- [Brewless next to the other ways to host Laravel](https://brewless.eu/alternatives)
