OpenShip Cloud

Product Introduction

1. Definition: OpenShip Cloud is a managed Platform-as-a-Service (PaaS) and Infrastructure-as-a-Service (IaaS) hybrid, built on the open-source OpenShip deployment platform. It provides a fully managed cloud environment for building, deploying, and scaling web applications, containers, and databases.
2. Core Value Proposition: It exists to eliminate the operational overhead of self-hosting while preserving its core benefits: control, data ownership, and zero vendor lock-in. It delivers the simplicity of managed hosting (like Vercel or Railway) with the architectural flexibility and migration freedom of self-hosted platforms (like Coolify or CapRover), all at a transparent, affordable price point.

Main Features

1. Hybrid, Agentless Deployment: OpenShip Cloud uses a unique agentless architecture. The build process can occur on your local machine or in OpenShip's managed cloud, producing an immutable Docker/OCI image. This image is then streamed via secure SSH to your target infrastructure—which can be OpenShip Cloud servers or your own VPS, bare metal, or homelab. No persistent agent or daemon is required on the production server.
2. Built-in Managed Services & Private Networking: Beyond application runtimes, the platform includes managed, auto-provisioned data services like PostgreSQL, Redis, and a full transactional mail server. These services are wired to your applications over an isolated, private network, ensuring they are never exposed to the public internet and simplifying secure service discovery.
3. One-Click Cloud ⇄ Self-Hosted Migration: This is a foundational technical capability. Applications are packaged as standard Docker containers with declarative configuration (openship.json). You can migrate a live application between OpenShip Cloud and a self-hosted server (or between your own servers) with a single click, without rebuilding or reconfiguring, enabling true workload portability.
4. Full-Featured Edge & Routing Layer: The platform includes a managed edge layer (OpenResty/Nginx-based) that handles domain routing, automatic Let's Encrypt SSL certificate provisioning and renewal, and advanced traffic rules. This includes per-route rate limiting, geographic and user-agent filtering, and hotlink protection, applied dynamically without reloads.
5. AI-Native & MCP (Model Context Protocol) Integration: Deployment and management can be triggered not just via Git, CLI (openship up), or a desktop app, but also through AI agents using the MCP standard. This allows AI assistants like those in Claude or Cursor to directly execute deployments, view logs, and manage infrastructure.

Problems Solved

1. Pain Point: The trade-off between convenience and control. Developers and small teams are forced to choose between easy-but-locking managed platforms and flexible-but-complex self-hosted solutions that require significant DevOps overhead.
2. Target Audience: Indie Hackers & Startup CTOs who need rapid deployment but are wary of future lock-in and unpredictable costs; DevOps Engineers in SMEs who want to standardize deployment workflows across cloud and on-premise infrastructure; Open-Source Project Maintainers who need to provide easy deployment options for their users without ceding control.
3. Use Cases: Migrating from Heroku to a more cost-effective and controllable platform without rewriting applications. Hybrid Cloud Deployment, where sensitive data resides on a private VPS while public-facing apps run on scalable cloud infrastructure, managed from a single pane. Agency Workflow, where client projects need to be deployed to the client's own infrastructure eventually, but managed efficiently during development.

Unique Advantages

1. Strengths & Limitations (Pros & Cons):

   • Pros: Unprecedented migration freedom eliminates platform risk. The inclusion of a managed mail server with unlimited domains is a significant differentiator. The agentless, SSH-based deployment to owned servers is simpler and more secure than agent-based models. The open-source core guarantees auditability and exit options.
   • Cons: As a newer platform, its ecosystem and third-party integrations are less mature than established giants like Vercel. The breadth of built-in services (databases, mail, Redis) means operational complexity is internalized by OpenShip, which could be a single point of failure compared to using dedicated, best-in-class SaaS for each service. Advanced enterprise features like SAML SSO are likely still evolving.

2. Key Alternatives & Differentiation:

   • vs. Vercel/Netlify (Managed Frontend Cloud): OpenShip Cloud supports any stack (backend, databases, workers) not just frontends/JAMstack. It offers true hybrid deployment, whereas Vercel is a closed, managed-only cloud. OpenShip includes native data services and mail; Vercel requires add-ons.
   • vs. Coolify/Dokploy (Self-Hosted PaaS): These are primarily self-hosted control panels you must manage yourself. OpenShip Cloud provides the managed control plane and optional compute, reducing your operational burden to zero. It offers a more polished, integrated experience and one-click migration to/from its cloud.
   • vs. Railway/Render (Managed Full-Stack Cloud): These are direct competitors in the "easy full-stack cloud" space. OpenShip's key differentiation is the explicit, first-class ability to deploy to your own infrastructure with the same workflow and the one-click migration path, offering a tangible off-ramp they lack.

Frequently Asked Questions (FAQ)

1. How does OpenShip Cloud pricing compare to Vercel or Railway? OpenShip Cloud uses a transparent credit-based system starting at $5/month, focusing on compute and build time. Crucially, it avoids per-domain fees and includes a mail server, which can lead to significant savings compared to platforms that charge for these add-ons or require external services.
2. Can I use OpenShip Cloud with my existing DigitalOcean or AWS servers? Yes. OpenShip Cloud's primary hybrid feature is connecting your own servers via SSH. You can point it at any Linux-based VPS (DigitalOcean, Linode, AWS EC2, Hetzner) or bare-metal server, and it will deploy and manage applications there without requiring a pre-installed agent.
3. What happens to my data if I cancel my OpenShip Cloud subscription? If your apps are running on OpenShip Cloud's infrastructure, you would need to migrate them to your own servers before cancellation. The platform is designed for this exact scenario. If your apps are already on your servers, cancellation only affects access to the managed control plane; your applications and data continue running uninterrupted on your infrastructure.
4. Is the OpenShip Cloud mail server reliable for production email? Yes, it is designed for production. It sets up a full mail server (like Mailcow) on your infrastructure, handling mailboxes and webmail. For reliable delivery, it relays outbound mail through a high-reputation service like Amazon SES, configuring SPF, DKIM, and DMARC automatically to ensure inbox placement.
5. How does OpenShip Cloud handle database backups and high availability? For managed databases on OpenShip Cloud, the platform handles automated backups. For databases on your own connected servers, you are responsible for implementing backup strategies, though OpenShip provides tools to facilitate this. High-availability setups for core platform services are a managed concern for OpenShip Cloud; for self-hosted deployments, you must architect your own HA.