Openship
Changelog

What's new

Features, fixes, and improvements shipping in Openship.

Jul 1
2026
v0.2.0featurebreaking

Cloud-as-source & flexible workspaces

Cloud projects are now fully owned by Openship Cloud, with a clean gateway model between self-hosted instances and the cloud.

  • Cloud-as-source — a cloud project's data lives on the cloud; your self-hosted instance is a gateway that proxies to it as the org owner. No more split ownership.
  • Born-on-cloud — deploying a project to the cloud promotes it to the SaaS first, so it never exists as a "local project reaching into the cloud."
  • Promote / bring-home — move a project between self-hosted and cloud; it's always canonical in exactly one place.
  • Flexible workspaces — invite collaborators to your personal workspace directly, or create a separate team organization — your choice.
  • Leak-hardened boundary — proxied requests forward no local identity headers; a documented no-leak invariant keeps local and cloud cleanly separated.

Breaking: the previous per-project "transfer" flow is replaced by promote/bring-home. Existing cloud-linked projects are unaffected.

Jun 22
2026
v0.1.1fixsecurity

Security patch & self-hosted improvements

  • Security — updated nodemailer to patch a denial-of-service advisory.
  • Versioning — deployments now carry a human-friendly version, assigned on a successful ship (per commit).
  • Self-hosted — project state is saved on the self-hosted server, with SSH tunnels and remote GitHub clone support.
Jun 1
2026
v0.1.0feature

Openship is here

The first public release of Openship — an open-source deployment platform.

  • Deploy from the CLI, the web dashboard, or the desktop app.
  • Ship to your own machine or an SSH-connected server.
  • Choose Docker or bare-process isolation per project.
  • Custom domains with automatic TLS.