Documentation

Philosophy

Beaker Studio is designed to be a practical deployment platform for ordinary software developers. By taking an opinionated approach, we were able to simplify essential configuration down to the same modest docker compose.yaml file that teams already use for local development. A consequence of this is that Beaker Studio is not a replacement for the <1% of cloud environments that benefit from complex configuration systems. At the same time, Beaker Studio avoids the mistakes of oversimplified deployment platforms by relying on proven open technology instead of gimmicks. If you can run your software on your laptop with docker compose, then you can build and deploy it with Beaker Studio. There are some exceptions to this, but we aim for as high of compatibility with the specification as possible.

Our focus on practicality extends beyond the developer experience and is at the forefront of every technical decision. Beaker Studio was designed from the ground up to be private and secure because that is just how it should be. One example of this is we encrypt environment secrets with AES-256-GCM and Scrypt in such a way that we cannot independently decrypt them at rest. Another way we prioritize customer safety is by not downloading your code to our servers in the first place. Instead of acting as a cloud hosting reseller, Beaker Studio builds and runs your code directly on your AWS account. This keeps your code in your hands while also allowing you to use the full breadth of features that AWS provides.

Last but not least, we are always here in case you need help. Please do not hesitate to contact us if you have questions not answered in the docs, or would just like to provide feedback.

Thank you,
–Evan Byrne, Founder