Introduction

Brewless deploys and runs PHP applications on European cloud infrastructure: Scaleway for the application itself and bunny.net for the edge in front of it. Both run in your own accounts. Brewless is the control plane that builds your releases, puts them live and keeps an eye on them.

What Brewless does#

• Builds and releases. brewless deploy production builds the current commit, runs your migrations and switches traffic once the new release answers healthy.
• Rollbacks. Any release that was live can be put back with one command.
• Environment variables. Kept in your own Secret Manager, pushed and pulled from the command line or edited in the console.
• Queues and schedule. Workers and scheduled tasks run next to your web container.
• Scaling. You set the bounds; your provider scales within them, down to zero if you like.
• Domains. Your own domain on an environment, with a certificate.
• Logs and commands. Read logs live and run one-off console commands in an environment.

What stays yours#

You own the Scaleway project and the bunny.net account, and both providers bill you directly. That has three consequences worth knowing from the start:

• Brewless is not in the path of your visitors. A request goes from the visitor to bunny.net to your container. It never passes through Brewless.
• Your application keeps running without Brewless. If you stop using Brewless, everything in your accounts stays where it is and keeps serving traffic.
• Brewless does not keep your secrets. It knows the names of your environment variables, never their values.

Note

Laravel is the framework that is supported today. See Frameworks for the current list.

Where to go next#

• How Brewless works explains the parts and who runs what.
• Quickstart takes a Laravel application from nothing to a live release.