Brev.dev / About Us · Why Join · Team Photos · Open Roles · Work Life · Apply

About Us

What are you building?

We’re building containers for development. We help you bring project isolation, reproducibility and standardization across your engineering team.

Using our CLI, define the dependencies and software that is needed to build your project, for each project. Then seamlessly switch between projects without anything breaking.

In a team, you can share your containers with other contributors to give them the same development environment. Let them start coding in under 15s, with zero-setup.

Because of the way we’ve built our product, we also give you 115x faster internet speed, and let you scale your RAM and CPU — making it faster to build and run your software.

How are you doing this?

We provision remote machines for development and connect your local computer to them.

Why haven’t others done this?

Actually most large companies have built some version of this in-house. Engineers at Facebook, Google, Amazon, Stripe, Workday etc. all develop with something like this.

The concept of coding on remote machines (aka cloud development environments) isn’t new, but is not widely adopted for two reasons:

  1. You’re never able to use your local tools, with all of your personal settings.
  2. You have to constantly think about the context of where your code is running. “Is it running on machine A or machine B? Ahh I have to go to machine A, connect it to machine B and then test it.”

These annoyances make it easy to snap out of remote development, and most people do. No-one wants to code in-browser on a web app, or SSH into a machine every-time and lose the personalization of their IDE.

**So what are you doing differently?**

We can only win if we first make a product that is (1) indiscernible from developing on your local computer, and then evolves to (2) feel better than developing software locally.

At present, we do this by creating a mesh network around your cloud computers, and include your computer as one of the nodes. This lets you access everything on localhost, and use any tools already on your computer — no matter where your code is actually running.

Cloud is an implementation detail, but an important one. It lets you think outside of your box 😉