Manage self-hosted deployments from build to domain connection by pointing to a GitHub repository
Imagine a scenario where pushing code triggers a server build, attaches a domain, and automatically issues a security certificate. OpenShip bundles this entire process into a single pipeline for self-hosted deployment. You can manage your server using a desktop app, a web dashboard, or a command-line tool, whichever you prefer.
Three execution modes based on use case
Deciding how to run OpenShip is the first step. If you want to use it alone on a single computer, the desktop app is the easiest option. In this case, the control plane runs on your local machine only while the app is open, while the actual application is deployed to an SSH-connected server or cloud. For team use or immediate deployment on push, choose the self-hosting method by installing directly on the server. This method is installed with the openship up command and runs as a container stack on Linux with Docker, or as a single process in other environments. If you do not want to manage anything directly, you can use OpenShip Cloud.
Automation from code push to security certification
OpenShip analyzes source code to automatically detect required build commands and ports. It reads package.json or framework settings even without a separate configuration file, and you can adjust details with openship.json if desired. The built app runs as a container or host process and opens only on the loopback address, not a public port. The edge server then handles domain routing and issues Let's Encrypt certificates. Even if domain or certificate issues arise, the deployment does not fail; only necessary actions are displayed, preventing app downtime. Via GitHub webhooks, only changed services are selectively rebuilt on every push to a branch.
Manage server infrastructure from a single dashboard
It is not just a deployment tool; it manages databases, domains, SSL, CDN, mail servers, and backups in the same place. It supports various languages such as Node, Python, Go, and Rust, as well as monorepo structures, and can deploy existing Docker Compose files as-is. The built-in mail server supports DKIM, SPF, and DMARC, allowing you to send emails without external mail services. Real-time monitoring lets you check build logs, container metrics, visitor locations, and response code distributions, with a stated overhead of approximately 1.4 microseconds per request. Cloud offers auto-scaling, while self-hosting provides multi-node readiness.
Items to check before adoption
OpenShip core is stated to be production-ready, and self-hosting is free. However, if you build the stack directly with Docker Compose, the API container accesses the host Docker socket, so it must run only on a trusted host. Additionally, using host operation features (port scanning, mail engine, etc.) requires an SSH channel from the container to the host; openship up sets this up automatically, but manual configuration requires additional steps. The license is Apache 2.0, and some included third-party components follow their own licenses. Multi-node clusters, load balancing UI, and visual CI/CD pipelines are noted as upcoming updates.
