Brewless is open

Since today, anyone with a work address can register for Brewless. No waiting list and no invitation: you sign up, connect your own Scaleway account and deploy your first Laravel application, free for one application. This post says what you get and how to get from a project on your machine to a live release.

What is Brewless?#

Brewless deploys and runs Laravel applications on European infrastructure: Scaleway for the application and bunny.net for the edge in front of it. Both run in your own accounts and bill you directly. Brewless is the control plane: it builds releases, runs migrations, puts releases live, rolls them back and keeps an eye on them.

It is never in the path of your visitors. A request goes from bunny.net to your container at Scaleway, and Brewless does not see it. Application secrets go into the Secret Manager of your own Scaleway project; Brewless keeps their names, never their values. How that fits together is on How Brewless works.

What does the free plan include?#

One application with every environment you want, production included. It gets a test address from Brewless, such as acme-shop-production.brewless.dev, from the first deploy. You start paying when you want your own domain or more.

Prices exclude VAT, and every plan has unlimited environments. Teams that start now keep the launch price for as long as they stay. That is on top of what Scaleway and bunny.net charge for what your app uses, at their own list prices, on your own bill. Brewless adds nothing to that bill and takes no percentage of it.

Note

Cancel any month and your application keeps running. It lives in your accounts, so leaving Brewless means you stop deploying through it, not that anything is switched off.

How do I start in five minutes?#

Five steps, each one described in full in the quickstart.

1. Register on brewless.eu/register with your work address and choose a console address, such as acme.
2. Confirm with the link in the mail. Your organisation is created and its console opens at acme.brewless.eu.
3. Connect Scaleway on the Providers page, with the API key of an IAM application you make for Brewless. Connecting providers says which rights it needs.
4. Connect your project from its root with the command line client:

composer global require brewless/cli
brewless login acme
brewless init

init detects Laravel, creates the application, asks which environments it should have and writes brewless.yml. After one yes it makes the database, queue and bucket in your own Scaleway project.

5. Deploy what you committed:

brewless deploy production

The client prints each step and ends with the address of the environment. The Applications page of the console keeps a checklist of these steps, ticked off as you take them.

Tip

Coming from Laravel Vapor? With a vapor.yml in the project, init offers to start from it. See Moving from Laravel Vapor.

Why a passkey or an authenticator app?#

A Brewless console holds the keys to your cloud accounts, so a mailbox alone is not enough to get in. Every account uses a second factor besides the mail: a passkey, or an authenticator app with recovery codes. You set it up at your first sign-in, before the console opens. Members explains how to add more and what to do when you lose one.

What is next?#

Registration is open; the rest of the product is what it was yesterday. Brewless supports Laravel only, and what is planned is listed as planned in the documentation. Questions go to hi@brewless.eu, and they reach me.