Loading
Shipper
Declarative deployments for Forge & Ploi
An open-source deployment CLI and docs surface that lets teams define infrastructure in YAML, plan changes, and apply them across Forge, Ploi, cPanel, EasyPanel, and preview environments.
Tag
Open Source · DevTools
Duration
Ongoing
Role
Positioning · Frontend · DX
The product story is intentionally concrete: one YAML manifest, one terminal workflow, multiple providers, preview environments, and databases handled in the same surface.
License
MIT
Workflow
YAML-first
Providers
4+
◇ The problem
Where they were stuck.
Teams were still wiring deployment workflows together manually across provider dashboards, branch conventions, and GitHub Actions. Shipper needed a sharper product story around provider abstraction, previews, and config-as-code.
◇ Our approach
How we shipped it.
- 01
Distilled the repo, specs, and docs into a simple product narrative: deploy like infrastructure, ship like a pro.
- 02
Designed the core hero around the actual workflow instead of abstract DevOps imagery: a `shipper.yml` manifest paired with terminal `plan` and `apply` output.
- 03
Highlighted the capabilities developers care about most in practice: provider-agnostic deploys, PR previews, database lifecycle, config validation, and GitHub Actions support.
- 04
Shipped an open-source-ready marketing and documentation surface that makes the CLI legible before a user ever installs it.
◇ Stack
What it's made of.
PHPLaravel ZeroNext.jsTypeScriptMarkdown docsGitHub Actions
Next case study