Self-hosted deployment platform
OpenShip
Build, deploy, route, secure, and monitor apps from one control plane.
OpenShip is an Apache-2.0 deployment platform with desktop, web, CLI, API, and MCP interfaces for building applications, deploying them to servers, routing domains, managing TLS, and operating supporting services.
Screenshots
How it works
- Step 1
Choose the control plane
Run the desktop app for a local solo workflow or install an always-on self-hosted server for teams and push-to-deploy.
- Step 2
Connect a source and target
Select a GitHub repository, local folder, or artifact and connect the approved server or OpenShip Cloud target.
- Step 3
Detect, build, and run
OpenShip detects the stack, freezes resolved configuration, builds the application, and runs it as a container or supervised process.
- Step 4
Route and operate
Attach domains and TLS, observe logs and resources, and manage deployments, rollbacks, data services, and backups.
Capabilities and scenarios
- Desktop, web dashboard, CLI, REST API, and MCP interfaces
- Stack detection and reproducible deployment snapshots
- Container or bare-process deployment
- Domain routing and Let's Encrypt TLS
- Push-to-deploy, logs, monitoring, backups, and rollbacks
Good starting points
Deploy personal projects to a VPS
Operate an internal self-hosted deployment control plane
Add push-to-deploy and preview environments to a team workflow
Automate deployment tasks through CLI, API, or MCP
Fit and limitations
Fit at a glance
- Project type
- Self-hosted deployment platform
- Repository set
- 1 repository
- Runtime status
- Unverified
! Known limitations
- Collected from public repository documentation; runtime behavior was not executed for this publication.
- Compose mode mounts the host Docker socket and must run only on a trusted host.
- DNS, TLS, email, backups, and public networking require operational ownership outside the application.
- The project is pre-1.0 and its documentation says some advanced features are still coming.
? Confirm before starting
- Choose desktop, bare, Compose, or managed mode before setup.
- A supported desktop system or a user-controlled server; Linux and Docker are required for the documented Compose hosting mode.
- Approved SSH access, DNS, public ports, storage, and backup policy when deploying to a server.
- Never publish server keys, admin credentials, Docker socket access, application secrets, or deployment data.
Repository set
These repositories form the complete project workflow. Follow setup order and include optional services only when the confirmed goal needs them.
oblien/openship
Deployment control plane, dashboard, desktop app, CLI, API, edge, and documentation
- Default branch
- main
- Captured revision
- v0.4.8; commit 3d64ba6a23464f94b1fbf0951a10e54facb2e161
- Author / maintainer
- OpenShip contributors
- License
- Apache-2.0
Catalog updated 2026-07-29. Reconfirm licenses, revisions, environment requirements, and runtime behavior from each repository before starting.