All 162 Dependencies
Every package Openship depends on, ranked by repo health score.
Openship is an open-source deployment platform that replicates the push-to-deploy experience of managed PaaS providers like Heroku or Vercel on infrastructure you control. Point it at a GitHub repo, a local folder, or a prebuilt artifact and it runs one pipeline end to end: it detects the stack from package.json, framework config, lockfiles, and any docker-compose.yml or openship.json; builds a Docker image or bare release; runs it as a loopback-only container or supervised host process; and routes it through an OpenResty edge that issues Let's Encrypt certificates without ever failing the deploy on a DNS or cert hiccup. A GitHub webhook re-runs the pipeline on every push, rebuilding only the services a monorepo push actually touched.
The project is explicit about separating how you run Openship itself from where your apps run. Solo developers can run a desktop app that drives remote servers over SSH with no public surface at all; teams that want CI/CD, multiple users, or to host apps on the same box run `openship up`, which auto-selects a Docker Compose stack (Postgres, Redis, API, dashboard, and a containerized edge) on Linux or a lightweight bare-mode process everywhere else. The same backend is exposed through a web dashboard, a scriptable CLI, an MCP endpoint for AI agents, and a REST API, so automation and human operators share one source of truth for deployments, domains, and permissions.
Beyond builds and routing, Openship bundles the rest of an application platform: managed Postgres/MySQL/MongoDB/Redis, automatic domains with wildcard TLS, an edge CDN with HTTP/3 and Brotli, scheduled backups with one-click restore, real-time build/container monitoring, and a self-hosted mail server (an iRedMail + Zero Email pairing) so teams can drop Mailgun or SES entirely. Every build is frozen into a snapshot, so redeploys and rollbacks re-run exactly what previously shipped rather than re-resolving configuration on the fly.
Openship supports Node, Python, Go, Rust, PHP, Ruby, Java, .NET, and existing Docker Compose files, and can target a VPS, a dedicated or colo server, multiple servers, or Openship Cloud for teams that don't want to run anything themselves. Self-hosting is Apache-2.0 licensed and free, with no license key gating the deployment, routing, backup, or mail-server functionality.