Self-hosted deploys

Ship,
done.

Build on your computer. Run that exact image on your VPS.

Run the installer on your Linux server. Build and ship from your computer.

curl -fsSL https://server.shibumistack.dev/install | bash
Read source
›
渋み  ship
1 commit ready to push
test passed
check passed
Built and uploaded a1b2c3d (3 MiB, 9f2c41ab08e3)
Deployment complete
Shipped in 11 seconds (--rollback if needed)https://example.com

VPS deployment only

A small Linux server will do.

Connect over SSH. Caddy handles public traffic while each app listens on loopback.

2 imagesper app by default
12 hoursrollback retention
4 GiBdefault free-space floor
Example image storage by workload
WorkloadCurrentWith rollbackImage contents
Static site~6.2 MB~12.4 MBBusyBox and built site files. About 3 MB compressed.
Small Bun service~80–150 MB~160–300 MBBun Alpine, production packages, and app source.
Full-stack app~200–350 MB~400–700 MBRuntime, packages, built assets, and migrations.

Estimates include the current image and one similar rollback image. Shared layers may use less space. Leave room for the operating system, logs, databases, uploads, and the 4 GiB deployment floor.

Compare starter VPS optionsPrices vary by region, tax, and architecture
Starter VPS comparison
ProviderStarter planvCPURAMDiskFrom / month
netcupGermanyVPS nano G11s22 GB60 GB€3.08
OVHcloudFrance + globalVPS-124 GB40 GB$4.54
ScalewayFranceDEV1-S22 GB20 GB€6.34
VultrGlobalCloud Compute11 GB25 GB$5
Akamai LinodeGlobalNanode11 GB25 GB$5
DigitalOceanGlobalBasic Droplet11 GiB25 GiB$6
IONOSEurope + USVPS XS11 GB10 GB$2
one.comEurope · intro priceCloud server S24 GB100 GB$4.99

Hetzner's entry plan has room for several small apps. A 1 GB server can run a light prebuilt service, but check its memory use first. Prices vary by location, tax, processor, and billing. Check the final price before ordering.

How it works

A deploy, from start to finish.

Commit the app you tested locally, then run bun ship from its root. Your computer needs Bun, Git, SSH, and working Docker CLI, Compose and Buildx tools.

First, install shibumi-server on your Linux server and point the app's domain at it. Project setup asks for the SSH target and domain, checks the Compose service and health path, and shows a plan for confirmation. Review and commit any generated deployment files; non-interactive setup can pause there without deploying.

On later runs, bun ship runs your configured checks, builds the image locally and uploads it over SSH. The server verifies the image against the pushed commit and validates Compose before replacement. It checks health after starting the new container.

To restore the retained previous image, run bun ship --rollback. The default rollback window is 12 hours. It does not restore an earlier database or undo migrations.

›
渋み  ship
SSH target (user@server or alias) [email protected]
Save [email protected] locally and connect? Yes
Saved in ~/.config/shibumi on this computer · never committed
App domain myapp.com
Continue through SSH? Yes
Where should the app live? /home/user/shibumi/myapp.com
Found myapp.com on example-vps.com
Wrote shibumi-server.json
Committed Shibumi deployment setup
Next: bun ship
More technical detailsWhat happens during replacement, and what lives on disk

Before setup. You need a working SSH login, permission to approve server changes through sudo, and server-side read access to the app's repository. Prepare Git, rootless Podman, a Compose frontend, Caddy and systemd on Linux. The bootstrap installs Bun if it is missing; it does not provision a bare VPS. SSH uses your existing authentication, and sudo handles its own password prompt.

No app image registry. bun ship uploads your built image directly over SSH; you do not need to push it to Docker Hub or GHCR. Builds still pull their base images. Upload happens before Git push, and the server checks image identity against the exact pushed commit.

What runs on the server. Rootless Podman runs app containers, systemd runs the deployment service, and Caddy terminates TLS and proxies each domain. Keep app and deployment listeners on loopback; expose Caddy and SSH through your firewall.

The cutover, in order. Preflight, image, Compose and optional test failures stop before replacement. Startup or health failures happen after replacement starts and trigger restoration of the previous image.

  1. Free disk and memory floors: 4 GiB and 512 MiB.
  2. Image labels checked against the registered repository, branch, and pushed commit.
  3. Compose config validated.
  4. Optional app tests run inside the image.
  5. The health endpoint has to answer.

During replacement. Caddy retries the loopback upstream for up to 20 seconds. Startup or recovery can take longer, so requests may fail during a deployment. The server attempts to restore the previous image if startup or health checks fail; this is not a zero-downtime guarantee.

Rollback mechanics. Two tags per app: runtime/<app>:current and one rollback that survives service restarts and expires after 12 hours. bun ship --rollback swaps back without fetching or rebuilding anything.

What lives where. Your SSH target sits in ~/.config/shibumi/config.json, mode 0600, on your computer. Webhook secrets and server checkout paths stay on the server. Registered app settings go in shibumi-server.json alongside your deployment scripts and container files. Review it before publishing, and never add secrets.

{
  "version": 1,
  "provider": "shibumi-server",
  "server": { "hostname": "example-vps.com" },
  "domain": "myapp.com",
  "appId": "myapp-com",
  "repository": "github:you/myapp",
  "branch": "main",
  "webhookUrl": "https://myapp.com/hooks/github/myapp-com",
  "service": "app",
  "port": 9001,
  "healthPath": "/healthz",
  "deploymentMode": "prebuilt",
  "platform": "linux/arm64",
  "cutoverRequired": false,
  "trigger": "ship"
}

Linux server

Install shis*.

* shis = shibumi-server.

You need Bun, Git, rootless Podman, Caddy, and systemd. Prepare these tools before setup; the bootstrap installs Bun if it is missing. Run the command on the server over SSH. Updates preserve your settings and secrets.

curl -fsSL https://server.shibumistack.dev/install | bash

Next, connect a project with Shibumi Ship. Server operators can register one directly with shis add example.com.