Terms of service

Warning

Draft of 14 October 2026. These terms have not been reviewed by a lawyer yet and do not bind anyone until they have been and you have accepted them. Passages marked [FOR REVIEW] are open.

1. Who and what#

These terms apply between Coding Agency, Blankenstein 131, 7943 PE Meppel, the Netherlands (Chamber of Commerce number 50814281), which offers Brewless, and the organisation that uses it ("you").

Brewless is a control plane: software that deploys and operates your PHP applications in cloud accounts that are yours. You keep your own accounts at Scaleway and bunny.net and your own agreements with them. Brewless is not a party to those agreements and is not your hosting provider.

2. Your account#

You sign up as an organisation and invite your team. You are responsible for who you invite, for the roles you give them, and for what is done under their sign-ins. Keep your sign-in methods to yourself and tell us at once if you think someone else has access.

3. Your provider accounts and keys#

To work for you, Brewless needs API keys of your provider accounts. You decide which rights those keys have; our documentation says which are needed. You can disconnect a provider at any moment, after which Brewless no longer holds its key. To end the key's access for good, delete it at the provider itself.

What Brewless does in your accounts, it does on your instruction: a deploy, a rollback, a change of scale, a domain. It creates and changes resources; it does not remove resources of yours unless you explicitly ask for exactly that.

What your providers charge you is between you and them. Brewless shows estimates where it can; they are estimates.

4. What stays yours#

Your code, your data, your secrets and every resource in your accounts are yours. Brewless stores no copy of your application's data and not the value of any of your secrets. Our own software, its design and its documentation remain ours; the command line client and the packages that run inside your application are open source under their own licence.

5. Leaving#

You can stop at any moment. Before or when you do, you can export everything Brewless knows about an environment, including Terraform that describes its resources, and detach it. Your application keeps running in your accounts exactly as it was. What ends is what Brewless did: deploying, rolling back, scaling and watching for changes. Only the environment's test address under brewless.dev goes, because its record is in Brewless's own DNS zone.

6. Price and payment#

Brewless is free for one application, without an own domain, for one person. The plans Solo and Business cost what the pricing page shows when you start, per month or per year, in advance and excluding VAT; a year costs ten months. Enterprise, and anything beyond a plan's limits, is agreed with your organisation; the agreement sets its price and limits. Your cloud usage is not in these prices: Scaleway and bunny.net bill you for it directly.

The first period is paid at Mollie, which gives Mollie a mandate to collect the next periods by direct debit. The price you start with stays while your subscription runs, also when the plan costs more later. A larger plan starts at once, for the difference over the rest of the period; a smaller one with the next period. You can cancel at the end of any period. A payment that does not go through makes the subscription overdue; after 14 days without payment deploying stops until it is paid, while your applications keep running in your own accounts. Every payment gets an invoice from Coding Agency. [FOR REVIEW: the period of notice for a price change of a running subscription; the early-access price guarantee; interest and costs on late payment.]

7. Availability and support#

We work to keep Brewless available and to tell you beforehand about maintenance that you would notice. Because Brewless is not in the path of your visitors, your application keeps serving when Brewless itself is unreachable; you then cannot deploy or change anything through it until it is back. [FOR REVIEW: whether any availability figure is promised, and support hours.]

8. What you may not do#

Do not use Brewless to break the law, to attack or burden systems of others, or to get at data that is not yours; do not try to get around its limits or its security; do not resell it without our agreement. We may suspend an organisation that does, after telling you why, or at once when waiting would cause harm.

9. Personal data#

Our privacy statement says what personal data we hold as controller. Where we handle personal data on your behalf, the data processing agreement applies and is part of these terms.

10. Liability#

[FOR REVIEW: the whole of this section.] Brewless acts in your accounts with the rights you gave it, on your instruction. We are liable for direct damage that is the result of our failing to do what these terms promise, up to the amount you paid us in the twelve months before the damage arose. We are not liable for indirect damage, such as lost revenue or lost data in systems that are yours to back up, nor for what your providers do or fail to do. Nothing here limits liability for intent or gross negligence.

11. Ending#

You can end the agreement at any moment, with effect at the end of the month you paid for. We can end it with three months' notice, or at once when you seriously break these terms and do not put it right after we asked. Ending never touches what runs in your accounts.

12. Changes#

We may change these terms. We tell you by mail at least 30 days before a change takes effect; if you do not agree, you can end the agreement before that day.

13. Law and disputes#

Dutch law applies. Disputes go to the competent court in [FOR REVIEW: the district], unless the law says otherwise.