Release directly from your machine

Go ship yourself.

Delivery Boy runs on your laptop or in your CI and talks straight to your targets. Keep the release in .deliver.yml, use your own tools and credentials, and add a hosted service only when you want one.

Read the quick start

Free CLI · MIT licensed · no account, daemon, or hosted runner

.deliver.yml

$ deliver plan

production · web
  01  build Hugo site
  02  package release
  03  check server access
  04  upload and verify
  05  activate release
  06  check live URL

$ deliver deploy
  ✓ preflight
  ✓ build
  ✓ stage
  ✓ activate
  ✓ verify

release succeeded

Run it yourselfRelease from your laptop, workstation, or CI

Connect directlyUse your own tools, targets, and secret stores

Add Teams if neededThe hosted service stays optional

A release you can inspect

Your deploy is code.
Keep it with the code.

Put the release contract in .deliver.yml. Review changes with the rest of the project, then ask Delivery Boy to compile it into a plan.

Describe

Name the targets, services, secrets, checks, and release order in one file.

Preview

Print every local command, upload, remote step, live switch, and check without running them.

Preflight

Find missing tools, inputs, secrets, and server access before the release changes anything.

Release

Build and stage complete artifacts, switch them live, verify production, and roll back on failure.

Use the stack you have

One release can contain more than one shape.

A site, a Compose stack, an nginx change, and a signed Mac app can belong to one ordered plan. Delivery Boy calls the tools that already do each job well.

Hugo

Build, package, stage, and switch a static site without a partial-copy window.

Files

Ship prepared directories and artifacts as versioned releases.

Docker Compose

Keep Compose files intact while Delivery Boy builds, ships, starts, and checks them.

nginx

Issue TLS, stage changes, validate the full config, and restore it if reload fails.

macOS

Build, sign, notarize, and publish an app and its Sparkle feed.

›_

Commands

Add the project-specific local and SSH steps that make your release yours.

Free CLI

Your release does not pass through us.

The CLI runs where you run it and connects straight to your targets. Keep targets and steps with your code, and resolve secrets from tools you already trust. Delivery Boy Teams will remain optional.

Read the CLI quick start →

deliver initDetect the project and prepare a configdeliver planPrint the release without running itdeliver preflightCheck requirements and accessdeliver deployBuild, stage, activate, and verifydeliver rollbackRestore the prior release

Paid Teams · private preview

Add shared control without giving up the local CLI.

Delivery Boy Teams is a planned hosted service for groups that want shared history, approvals, schedules, notifications, and isolated runners. It adds teamwork around the CLI; it does not become a requirement for releasing. Public signup and billing are not open yet.

What Teams will add →

Shared run historyRole-based approvalsSchedulesIsolated runnersSlackNotifications

Keep the release in your hands.

Print the plan, review every step, then run it from your own machine.