Skip to content

Hosting

Your factory. Your servers.

DevBench runs on a host you control and deploys to the cloud you already have: AWS, a server over SSH, or DevBench compute for previews.

Runs on your server. Deploys to the cloud you already have.

One container per workspace, on a host you control.

Previews run on DevBench compute, free and throwaway.

Where should it run?

DevBench compute

Previews, free and throwaway.

Free previews for the whole team to test in.

What you need

  • The workspace's repos.

What DevBench does

  • Runs every repo as containers you can click through.
  • Replaced by the next deploy, stopped when idle.

Who may press it

  • Anyone can deploy a preview.

  • Agents can deploy previews, not environments.

devbench
  • $ devbench deploy

    Deploy this workspace's repos as live test containers. The same as the Deploy button.

What runs on your host.

DevBench runs on a machine you control, with Docker. Your code leaves it only when you deploy.

Outside

Your host · A machine with Docker

Leaves the host

Control plane · Runs on your host

Runs on your host in Docker. The chat updates live.

Memory is the constraint

Idle workspaces and previews stop to free memory.

Invite-only

Your owner creates the organization and invites the team.

Model-agnostic

You choose the model. Nothing else depends on it.

A preview for every branch. Then the real thing.

Every repo runs as a container you can click through. Each deploy replaces the last.

  • Throwaway
  • Free
  • Not public
  • Stopped when idle

Refused before it exists. Updated, not recreated. Stopped, not deleted.

Preview runs on DevBench compute. Environments has one row per branch.

Where a row can point

Deployed elsewhere, by default

Your own pipeline deploys it. DevBench keeps the record.

DevBench compute

Free previews the whole team can open and test in.

AWS or a provider

A site or server on AWS, or a machine you reach over SSH.

Three rules against common deploy mistakes

  1. Refusals happen before anything is created.

    Missing permissions show up first.

  2. A redeploy is an update.

    It updates the existing site or server, and never makes a new one.

  3. Stop does not delete.

    Stop marks the deployment stopped and deletes nothing.

An unknown target fails with an error. It never falls back to DevBench compute.

DevBench does not guess how to restart your app.

Your team writes an update script for each environment. Without one, the deploy is refused.

an environment's update script
set -euo pipefail                       # DevBench adds this line
cd /srv/app
git fetch origin "$DEVBENCH_BRANCH"
git checkout -q "$DEVBENCH_BRANCH"
git pull --ff-only
npm ci && npm run build
sudo systemctl restart app             # yours: systemd, pm2, compose, make…

What it brings that an SSH client does not

  • The host key is checked on every connection.

  • A failed step stops the script before any restart.

  • Commands run as you wrote them.

  • The branch and environment are passed in, so one script serves them all.

AWS

Connect the account. Switch on what it may build. Check first.

Credentials say who DevBench is in an account. Switches say what it may build there.

What it may build

S3 static site
One bucket per site, behind CloudFront.
S3 shared site
Several sites in one bucket, each with its own CloudFront distribution.
Lightsail
Fixed-price instances and managed databases.
RDS
Managed Postgres, MySQL and MariaDB.
EC2
Plain virtual machines for any app server.
Elastic Beanstalk
Load-balanced, auto-scaling environments.

Use an IAM user's keys, or a role DevBench can assume.

Switching a capability on checks the account first

  1. 1

    Permissions are checked first

    Checks the permissions without changing anything.

  2. 2

    A read-only check, if needed

    The result is a warning, never a pass.

  3. 3

    Missing permissions are listed

    As a policy you can paste.

Re-checked on a schedule

Each AWS connection is checked again on a schedule. A failure reaches the owners.

Resources

Lists what already exists in the account. Each item can be linked to the part of the app it serves.

devbench cloud
  • $ devbench cloud can

    What this workspace may do in the cloud, and how far.

  • $ devbench cloud list

    Deployments that already exist in your cloud accounts.

  • $ devbench cloud link <id> <repo>[/<dir>]

    Record which part a resource serves.

  • $ devbench cloud call <service> <Operation>

    One AWS call, made through DevBench.

A VPS you already rent, and the accounts machines come from.

DevBench deploys to it the same way it deploys to an instance it created.

  • SSH

    Any machine you can reach over SSH

    Connecting asks forHost, port, user, a key or a password

  • Hetzner Cloud

    Supplies machines

    Connecting asks forA workspace API token

  • DigitalOcean

    Supplies machines

    Connecting asks forA personal access token

  • Vultr

    Supplies machines

    Connecting asks forAn API key

  • Supabase

    A Supabase workspace

    Connecting asks forWorkspace URL, service role key, anon key

  • MongoDB

    Atlas or your own mongod

    Connecting asks forA connection string

A capability means the software is installed

Each capability is checked by running its tool. A missing package shows the command that installs it.

capabilities
docker
A Docker Engine this user can talk to
nodejs
Node and npm
python_app
Python 3 and the venv module, a separate package on Debian
static_site
nginx, and certbot for automatic HTTPS
postgres
The Postgres client, and a server answering locally

The vendor accounts supply machines. You choose a size and region at deploy time.

Apps

The repos that make up one application, and how each part runs.

An App groups the repos of one application.

A recipe per part

Each part has its own recipe. Write it by hand, or let DevBench propose one. Nothing changes until you apply it.

Databases and seed SQL

Each App owns its databases and seed SQL. Schema changes go in a migration.

devbench deploy
  • $ devbench deploy

    Deploy this workspace's repos as live test containers. The same as the Deploy button.

  • $ devbench deploy config list

    Every deployable part of this workspace and where it goes.

  • $ devbench deploy config generate

    Read a repo and propose how each part builds and runs.

  • $ devbench deploy config apply <id>

    Apply a proposal.

  • $ devbench deploy config set <repo>[/<dir>] --start … --build …

    Create or edit one part's recipe.

  • $ devbench deploy seed set --file <path>

    Replace the seed data.

Set up with you

Start with one real project.

We set up your factory with you and ship one project from your roadmap.