OpenShip

Product Introduction

1. Definition: OpenShip is an open-source, self-hostable Platform-as-a-Service (PaaS) and deployment automation platform. It functions as a unified control plane for building, deploying, and managing containerized applications across any infrastructure, from its managed cloud to your own virtual private servers (VPS), bare metal, or homelab.
2. Core Value Proposition: OpenShip exists to eliminate infrastructure complexity and vendor lock-in for developers and teams. Its primary value is enabling a "deploy anything, own everything" workflow, where you retain full control over your code, data, and runtime environment while benefiting from automated, Heroku-like developer experience. Key keywords include: self-hostable PaaS, zero vendor lock-in, open-source deployment, and hybrid cloud deployment.

Main Features

1. AI-Powered, Multi-Trigger Deployments: Deployment can be initiated via a standard git push, the openship up CLI command, a native desktop application (Mac/Windows), or an AI agent using the Model Context Protocol (MCP). The platform automatically detects your application stack (Node.js, Python, Go, Rust, Docker, etc.), installs dependencies, and runs builds locally on your machine or in the cloud, keeping production servers dedicated to serving traffic.
2. Immutable, Zero-Downtime Deployment Pipeline: Every build produces an immutable, versioned container image. This image is streamed via SSH to target servers (no remote agent required) and started as a fresh container on an isolated private network. The integrated edge router (OpenResty) handles domain routing, provides automatic Let's Encrypt SSL certificates, and swaps traffic to the new version with zero downtime. Previous versions remain warm for instant, one-click rollbacks.
3. Managed Built-in Services & Private Networking: Beyond the application runtime, OpenShip provisions and manages adjacent services—PostgreSQL, Redis, MongoDB/MySQL, S3-compatible object storage, and a full transactional mail server—on the same private network. These services are only accessible to your application, not the public internet, and include features like daily backups, point-in-time recovery, and automated upgrades.
4. Hybrid & Multi-Cloud Infrastructure Orchestration: The platform provides a single dashboard and CLI to manage applications deployed across a mix of OpenShip's managed cloud and your own infrastructure. You can seamlessly move workloads between these environments without code changes or rebuilds, enabling use cases like running production on your servers while using the cloud for preview deployments or burst capacity.
5. Comprehensive Observability & Security Controls: Features include real-time streaming logs, CPU/memory/network metrics, and an audit log for all actions. Security is built-in with a default-deny firewall, per-route rate limiting, automatic security headers (HSTS, CSP), DDoS protection at the edge, and an encrypted secrets vault. Role-based access control (RBAC) allows granular permissions down to the individual project level.

Problems Solved

1. Pain Point: Vendor lock-in and platform dependency. Many PaaS solutions (e.g., Vercel, Netlify, Heroku) create proprietary workflows and runtime environments, making it costly and technically difficult to migrate away. OpenShip solves this by using standard Docker/OCI containers and open-source components, allowing you to remove the platform entirely while your applications continue running.
2. Target Audience: DevOps engineers and platform teams in small to mid-size companies seeking to standardize deployments without heavy Kubernetes overhead; indie developers and startups needing a robust, cost-effective deployment platform they can run on affordable VPS providers (Hetzner, DigitalOcean); and enterprises with data sovereignty or compliance requirements that necessitate on-premises or private cloud hosting.
3. Use Cases: 1) Unified Multi-Environment Management: Managing staging, production, and client-specific deployments across different cloud regions and on-prem servers from one interface. 2) Cost-Optimized Hosting: Deploying applications on low-cost, high-performance bare metal or VPS while retaining a modern developer experience. 3) Legacy Application Modernization: Containerizing and automatically deploying existing applications (Rails, Laravel, Django) with added SSL, monitoring, and backup services. 4) Disaster Recovery & Migration: Easily replicating or moving entire application stacks between infrastructure providers or from cloud to on-prem with a single click.

Unique Advantages

1. Differentiation: Unlike managed-only platforms (Vercel, Netlify), OpenShip can be fully self-hosted. Unlike other self-hosted platforms (Coolify, Dokku, Dokploy), it requires no long-lived control-plane server; the orchestration logic runs from a desktop app or CLI, and it can adopt pre-existing running containers without rebuilding. Its built-in mail server and comprehensive edge rules (country blocking, hotlink protection) are also unique in the space.
2. Key Innovation: The "agentless" architecture using SSH for deployment and the ability to perform builds locally are significant technical differentiators. This removes the need for a persistent, always-on management daemon on your servers, enhancing security and simplicity. Furthermore, its deep integration with the Model Context Protocol (MCP) for AI-agent-driven deployments is a forward-looking innovation in developer tool automation.

Frequently Asked Questions (FAQ)

1. Is OpenShip really free to self-host? Yes, the core OpenShip platform is 100% open-source under the Apache 2.0 license and free to self-host indefinitely on your own infrastructure. You only pay for the underlying servers (e.g., from AWS, DigitalOcean, or Hetzner). The paid "Openship Cloud" plan is for those who want a fully managed experience without operating their own servers.
2. How does OpenShip handle database backups and high availability? For managed services like PostgreSQL and Redis, OpenShip performs automated daily backups and supports point-in-time recovery (PITR). For high-availability setups, it supports multi-server fan-out across regions. When self-hosting, you configure the backup schedules and replication topology, giving you full control over your data resilience strategy.
3. Can I use OpenShip with my existing Nginx or Traefik proxy? Yes. OpenShip is designed to coexist with existing infrastructure. You can point it at a server with an existing proxy (Nginx, Caddy, Traefik) on ports 80/443, and it will work alongside it. You can also later revert this configuration if needed, avoiding a "rip-and-replace" scenario.
4. What happens to my applications if I decide to stop using OpenShip? There is no lock-in. If you are self-hosting, your applications are standard Docker containers, your data is in standard volume mounts, and your configuration is in your openship.json file. Removing OpenShip simply removes the management layer; the containers, networks, and data persist and continue to run. You can manage them directly with Docker or adopt them with another tool.
5. Does the built-in mail server ensure good email deliverability? Yes. The OpenShip mail server is a full SMTP server that handles receiving and sending. For outbound mail, it relays through a high-reputation transactional email service like Amazon SES by default, ensuring emails land in inboxes. It also automatically configures the necessary SPF, DKIM, and DMARC DNS records for your domains.