OpenShip v0.9.1

Openship is an open source application deployment platform that simplifies building, deploying, operating, and scaling applications on your own infrastructure. It combines Git-based deployments, container management, SSL automation, application monitoring, managed services, and a modern web interface into a single platform. Designed as an alternative to managed platforms such as Vercel, Netlify, and Render, Openship gives developers full ownership of their infrastructure while maintaining a streamlined deployment experience.

Deploying applications to self-managed servers often requires configuring Docker, reverse proxies, SSL certificates, deployment pipelines, and monitoring separately. Openship brings these capabilities together into a unified platform that works with cloud VPS providers, dedicated servers, and homelabs.

Unlike many self-hosted deployment tools that install build agents directly on production servers, Openship builds application images externally and deploys immutable containers over SSH. This keeps production systems focused on serving applications while simplifying rollbacks and updates.

The platform is fully open source under the AGPL-3.0 license and supports both self-hosting and managed cloud hosting.

Key Features of Openship

Git-Based Deployments

Applications are deployed automatically from Git repositories. Every commit can trigger a build, resulting in versioned container images that are easy to deploy or roll back.

Deploy Anywhere

Openship supports deployment to:

  • Virtual private servers

  • Dedicated servers

  • Home labs

  • Cloud virtual machines

  • Openship Cloud

The deployment workflow remains consistent regardless of the hosting environment.

Zero Downtime Deployments

The platform automatically routes traffic to newly deployed containers after they are ready, reducing downtime during updates. Previous versions remain available for quick rollback if necessary.

Automatic SSL

SSL certificates are automatically provisioned through Let's Encrypt, eliminating manual certificate management for hosted applications.

Integrated Monitoring

Developers can monitor deployments, view application logs, inspect metrics, and manage previous releases directly from the web dashboard, desktop application, or CLI.

Managed Infrastructure Services

Beyond application deployment, Openship includes managed services such as PostgreSQL, MySQL, Redis, MongoDB, and a built-in transactional email service with support for multiple domains.

Multiple Interfaces

Users can manage infrastructure through:

  • Web dashboard

  • Desktop application

  • Command-line interface

  • REST API

  • MCP integration for AI agents

This flexibility makes Openship suitable for both manual administration and automation workflows.

Open Source

Every component of the platform is publicly available, allowing organizations to audit the source code, customize functionality, and avoid vendor lock-in.

Download OpenShip v0.9.1 - Software Mirrors

OpenShip v0.9.1 for Windows

Openship-win32-x64.zip | 218.46 MB

OpenShip v0.9.1 for macOS

Openship-x64.dmg | 236.98 MB

Openship-arm64.dmg | 229.73 MB

OpenShip v0.9.1 for Linux

Openship.AppImage | 184.84 MB

openship-v0.9.1-linux-amd64.tar.gz | 67.26 MB

openship-email-v0.9.1-linux-amd64.tar.gz | 72.57 MB

Openship-arm64.AppImage | 185.44 MB

Others Download related to OpenShip v0.9.1

openship-dashboard-v0.9.1.tar.gz | 37.19 MB

openship-cli-v0.9.1.tar.gz | 38.58 MB

OpenShip v0.9.1 Source Code

OpenShip v0.9.1 Source code (zip)

OpenShip v0.9.1 Source code (tar.gz)

OpenShip v0.9.1 Release Notes:

This patch adds a public app catalog, Russian dashboard support and runtime image controls. It fixes workflow saves and Cloud recovery, updates webmail live, and improves routing, build capacity and image handling during redeployments. These notes cover all changes since 0.9.0.

Apps, language and workflow setup

  • Browse apps before installing — the public website now has an Apps directory
with search, category filters and individual pages showing features, included services and app overviews. Installation opens the existing Cloud setup flow; self-hosted users can follow the installation guide. Returning to the directory preserves search and category selections.
  • Russian language support — select Russian during onboarding or in dashboard
language settings. Dashboard translations cover workflow setup, Cloud reconnect and webmail recovery, and a Russian README is available alongside the existing localized introductions.
  • Save custom Actions workflows — new standalone workflows initialize their
name from validated YAML, so valid starter workflows can be saved after setup. Missing names, runners, files, source validation or access settings now have inline guidance that leads back to the relevant control or editor. Repository setup also offers a direct custom-workflow option.

Cloud and webmail recovery

  • Continue app installs and plan selection after sign-in — app and plan links
retain their destination through login, registration, verification, password reset and 2FA. App installation resumes its confirmed configuration, server and existing draft after checkout; failed retries remain recoverable. Plan links select an offer for review, with an explicit action still required to purchase.
  • Reconnect saved Cloud server links — disconnected links show a Cloud sign-in
action, with separate guidance for account mismatches and temporary failures. Live controls wait for a verified connection, and reconnecting reuses the saved server link. Controls missing from an older Cloud API show availability guidance; refreshing retries reads without repeating a write.
  • Recover an existing webmail app — when a mail registration loses its webmail
link, select an accessible existing app on the same mail server and hostname and choose Reconnect and deploy. Recovery reuses the project, credentials and persistent volumes while preserving domain ownership and permission checks.

Runtime configuration and deployment safety

  • Select matching runtime versions and custom production images — generated
PHP builds support PHP 8.3 and 8.4 through the generic runtimeVersion setting. Docker source builds offer an advanced runtimeImage override. Stack-selected recipes validate actual runtime capabilities and compatibility before activation; invalid settings do not partially update the project, and retained-image rollback preserves the original version and image configuration.
  • Recover Cloud Actions from connected instances — Desktop and self-hosted
clients forward Cloud workflow and runner operations to their owning Cloud instance, with the same scope and permission checks.
  • Use the server's actual available build capacity — automatic Cloud builds
account for running workloads and pending CPU reservations before choosing their worker size. Build setup also reports the effective workspace capacity.
  • Recheck deployment health — project status and workload selection reuse
current startup-health verification while retaining earlier warnings for review.
  • Track current container images during Compose redeploys — cached Docker
inventory preserves immutable image identity, so port preflight and rollback can verify running services safely.
  • Receive live inbox changes — webmail refreshes after IMAP IDLE events, with
event streams flushed through buffering proxies and correct folder routing.
  • Simplify the project Backup page — the existing project header supplies
its title, removing the duplicated backup heading and description.
  • Validate declared runtime roles — stack-role configuration rejects missing
kinds, empty commands, incomplete exec probes and invalid replica counts. This is configuration/detection support for future role execution.
  • Preserve domains that route only specific paths — migrations now discover
and retain domains with exact or prefix routes and no catch-all service. OpenResty and Cloud routing preserve those paths; unmatched requests return 404. Omitting an existing source catch-all requires a decision before project creation or source container changes. Routing retries keep the previous complete table when a selected upstream is unavailable.
  • Refresh deployment images before replacing services — manual Docker
redeploys refresh mutable registry tags while preserving locally built images and pinned rollback artifacts. Full redeploys keep otherwise unchanged external services, including databases, running when their actual image content matches. Docker validates every replacement image and freezes its reference before activating any service; failed preparation leaves existing containers running. Image preparation is all-or-nothing, while container replacement remains sequential rather than a transaction across the whole stack.

Performance and User Experience

Openship provides a polished user experience that lowers the barrier to self-hosting modern applications. The interface is clean, deployments are straightforward, and infrastructure management is considerably simpler than manually configuring Docker, reverse proxies, certificates, and monitoring tools.

One of its strongest advantages is keeping production servers free from build workloads. Images are built separately and transferred to the deployment target, improving reliability and reducing resource usage on live servers.

The project is under active development, with new features such as clustering and horizontal scaling planned for future releases. Community feedback has been largely positive, particularly regarding its ease of use and modern approach to self-hosted deployments.

Pros

  • Free and open source.

  • Supports deployment to your own infrastructure.

  • Zero downtime deployments.

  • Automatic SSL certificate management.

  • Git-based deployment workflow.

  • Built-in monitoring and rollback.

  • CLI, web, desktop, REST API, and MCP support.

  • No vendor lock-in.

  • Active development.

Cons

  • Still a relatively new platform.

  • Advanced clustering features are still under development.

  • Best suited for containerized applications.

  • Smaller community than established deployment platforms.

Who Should Use Openship?

Openship is an excellent choice for developers, DevOps engineers, startups, agencies, and organizations that want a modern deployment experience without relying entirely on managed cloud platforms.

It is especially appealing to users who want the simplicity of services like Vercel while maintaining complete ownership of their servers, applications, and deployment pipeline.

Final Verdict

Openship successfully bridges the gap between traditional self-hosting and modern cloud deployment platforms. Its Git-driven workflow, automated infrastructure management, integrated monitoring, and open source philosophy provide an impressive developer experience without sacrificing control.

Although the platform is still evolving, it already delivers a compelling alternative to commercial deployment services and has strong potential to become a leading open source application platform.

OpenShip v0.9.1
Free
Software Informations:
Developer:

Operating System:
Windows / macOS / Linux
Date Added:
2026-10-14T01:03:59.724Z
Categories:

Post a Comment/Report Broken Link: