Deploy a Full CI/CD Platform with One Command Using OpenShip Desktop App

Introduction

Public PaaS services have become increasingly frustrating due to rising prices, feature cuts, and disappearing free tiers, while keeping code and data in third‑party hands. OpenShip addresses these pain points by offering a self‑hosted deployment platform with built‑in CI/CD, written in TypeScript and boasting over 8 000 GitHub stars.

Key Features

Technology Stack Detection

OpenShip reads package.json, framework configs, lock files, docker-compose.yml, and an optional openship.json to infer the appropriate package manager, build commands, and service ports. Supported frameworks include Next.js, Nuxt, SvelteKit, Remix, AdonisJS, Django, Ruby on Rails, Laravel, Symfony, Blazor, and Phoenix; languages span Node, Python, Go, Rust, PHP, Ruby, Java, .NET, plus Docker and monorepos.

Build and Release

The platform can perform local builds and upload artifacts, or build directly on the target server. Build configurations are frozen into snapshots, enabling exact reproducible rollbacks. Applications run in containers bound to loopback addresses, never exposing public ports.

Routing and TLS

OpenResty serves as the edge gateway, handling reverse proxy and TLS termination. Let’s Encrypt certificates are obtained and renewed automatically. Since routing and certificates are processed after the application starts, DNS or certificate failures do not abort deployments; they are merely marked as “needs attention.”

Automatic Deploy on Push

After linking a GitHub webhook, every push to a configured branch triggers a new pipeline run. In monorepos, only the services affected by the changes are rebuilt.

Database and Backend Management

PostgreSQL, MySQL, MongoDB, Redis, workers, WebSockets, and file storage are all manageable from the same panel, eliminating the need for separate database services.

Domain, SSL, CDN, and Email

OpenShip supports unlimited domains, wildcard certificates with zero‑configuration renewal, edge caching with HTTP/3, Brotli compression, instant cache purge, and a built‑in SMTP server with DKIM, SPF, and DMARC configuration, removing the need for external services like Cloudflare or Mailgun.

Backup, Monitoring, and Scaling

Scheduled backups of databases and volumes can be restored with a single click. Build logs stream live to the UI, and container metrics are displayed in real time. The OpenShip Cloud offering includes automatic scaling, while the self‑hosted version reserves multi‑node clustering capabilities, with load‑balancing UI and private networking on the roadmap.

Docker Compose Compatibility

Existing docker-compose.yml files can be dropped directly into OpenShip without modification.

Quick Start

Download the desktop app for macOS, Windows, or Linux, then run a single command to install OpenShip:

curl -fsSL https://get.openship.io | sh
openship

The installer launches an interactive wizard that creates the first admin account, binds a domain, and registers OpenShip as a system service. Subsequent commands include openship open (open the panel), openship stop (stop the service), and openship update (upgrade).

Deploying a project requires two steps:

cd your-project
openship init
openship deploy

For Docker‑centric workflows, the compose file can be used directly:

git clone https://github.com/oblien/openship.git && cd openship
cp .env.example .env
# edit .env as needed
docker compose --env-file .env -f docker/docker-compose.yml up -d

Use Cases

Ideal for personal side projects that need continuous online availability without paying monthly PaaS fees—run the desktop app on a $5 VPS. Small internal tools for teams can also benefit, as code pushes trigger automatic deployments and the web panel provides status visibility. Users who want to avoid vendor lock‑in appreciate that all code, data, and infrastructure remain under their control, and the Apache 2.0 license permits commercial use.

Author’s Assessment

The UI is notably cleaner than many 8k‑star projects, and core functionality works out of the box despite some missing documentation. Compared with Coolify and Dokku, OpenShip separates the control panel from the build runner, allowing the server to focus solely on running applications, which conserves resources. Drawbacks include the lack of multi‑node clustering, load‑balancing UI, and visual CI/CD pipelines—features listed on the roadmap but not yet released. Single‑node production use is stable, but large‑scale teams may need to wait for future updates.

Open Source Repository

https://github.com/oblien/openship