OpenShip v0.9.122026-11-12
Critical update for build-secret protection, database upgrade repairs and
backup/restore reliability. Includes all changes since 0.9.11, with reviewed
source-image update PRs, platform imports, mail improvements and a translated
website.
Build security
- Pass generated Docker build environments through temporary BuildKit secrets instead of
embedding values in Dockerfiles or image history. Mask configured values in streamed
logs, error summaries and failure notifications, including split and multiline output.
Preserve Cloud worker limits, parallel server builds and cleanup after cancellation.
- Attribute REST audit events to the personal access token used, and audit token
reads through the existing authorization path.
- Preserve private edge-vhost permissions and verify access with unprivileged
workers. Keep tunnel hostnames out of unsupported password-protection flows.
Runtime and source updates
- Keep image services with missing deployment digests visible as unverified. Inspect the
running image through the existing deployment runtime to detect moved tags, with bounded
reads and no deployment-row writes. Show unavailable update status without an update badge.
- Propose Dockerfile and Compose image changes through reviewed GitHub pull
requests. Check repository access first and guide users to reconnect or update
their GitHub installation when the required permissions are missing.
- Apply security fixes to managed runtime versions instead of repeatedly refreshing
an unchanged image. Distinguish a runtime that is absent from a failed probe.
Deployments and infrastructure
- Allow webhook and CLI deployments to approve reviewed Compose source changes
through the shared approval flow.
- Keep branch and Compose-path controls available after an unsuccessful first
scan, reject blank required build commands, and offer Static Site for folder uploads.
- Keep token-authenticated repository clones on HTTPS even when a server's global
Git configuration rewrites GitHub URLs to SSH.
- Recover orphaned builds through shared worker ownership, preserve application
runtime/log access when adding services, and scope shared image-export paths.
- Scale managed build-cache budgets with available disk and expose server cache
settings. Improve local image exports without sharing another build's output.
- Let edge upgrades finish safely after an SSH disconnect. Preserve owned mounts
in imported Cloud workloads and explain host paths that cannot be imported safely.
- Support hosted Jobs on Manage-connected SSH servers. Match BullMQ repeatable
jobs by name so changing a cron schedule removes the previous schedule.
- Accept bounded YAML aliases in imported GitHub workflows, show the latest run
for every workflow, and avoid duplicate GitHub-owned workflow webhook payloads.
- Recover failed installed-CLI updates and verify release installation and updates
on disposable VPS instances before publishing images and packages.
Domains
- Configure static HTML, JSON or text responses on a domain through its normal
route editor, including maintenance and verification responses without an app container.
- Avoid rewriting unchanged edge route files and repeating remote reads during a
registration. Preserve exact file contents and permissions while retaining route
validation, reloads, certificate activation and transactional rollback.
- DigitalOcean DNS — connect a DigitalOcean token in Settings → Connections to preview
and apply a custom domain's records and issue DNS-verified HTTPS automatically, as with
Cloudflare. Each record OpenShip creates is paired with an _openship-owner TXT marker,
so removing a domain deletes only OpenShip's own records.
Imports, backups and database upgrades
- Improve platform imports, including Railway and Vercel setup, source and
destination review, progress reporting and cancellation.
- Keep migration environment fields visible while entering missing secrets, with
a plain section heading instead of a nested disclosure that collapses during editing.
- Preserve source project boundaries during platform imports: one project contains
its native services, private DNS, encrypted service environments and separate volumes.
Keep service environment values scoped correctly during source builds too.
- Carry imported custom domains and aliases through the existing migration routing
flow, pending normal verification. Show DNS cutover guidance and replacement
notices for Railway and Vercel URLs in review and saved migration progress.
- Restore portable instance exports with their server credentials and workspace
ownership. Normalize restored data for the destination schema and keep the
instance import and server selection views consistent.
- Repair missing workspace and security-advisory fields on upgrades, including
databases whose earlier migrations were already marked as applied.
- Serialize backup execution per destination to prevent connection exhaustion.
Recover orphaned Cloud backup activities through the existing ownership checks.
- Complete local mail backups and portable restores through the shared backup
orchestration, including target-server mail configuration and real mail round trips.
- Prevent browser autofill of backup destination credentials and keep destination
menus visible outside their cards.
Mail
- Preserve mail logs and Fail2ban ban history across engine updates, and remove
Dovecot's stale PID file before startup.
- List all signed-in mailboxes and keep account menus usable when they overflow.
- Correct webmail message colors in light/dark themes and when printing, and
refresh security dependencies.
- Protect support intake and add mailbox sender blocking.
Assistants
- Reuse managed agent setup for custom API connections and report the actual
runtime setup state.
- Find agent CLIs installed outside the macOS GUI PATH, restore public BuildKit
pulls, and correct scoped Claude startup.
- Allow reviewed repository patches to delete regular files through the existing
review and validation flow.
- Add OpenShip plugins for Codex and Claude Code.
Dashboard, billing and website
- Keep the shared destination dropdown available with one server or Cloud plan,
with Add server in its menu across deployment and migration flows.
- Refresh deployment state after navigation and browser resume. Unify project
settings and shared environment controls with the existing service views.
- Keep plan overview, usage and payments together under Plans & billing, align
Cloud plan presentation across the website and dashboard, and retain payment
recovery for expired renewals.
- Improve deployment, verification and cancellation emails, and standardize the
Referral experience.
- Translate website content into the existing supported languages, with localized
URLs, navigation and product screenshots. Correct Arabic layout and preserve
English framework names. Documentation remains in English.
- Add migration guidance for teams moving an existing app, group website
navigation, and provide a direct Start on Cloud action.
- Use the BytesMap SDK for unified Cloud telemetry and remove PostHog.
Upgrade notes
- Update the API (including all replicas), dashboard and Desktop app together.
This release includes control-plane database migrations; keep a current
instance/database backup before upgrading.
- Build-secret protection applies to new builds. Rebuild older application images
to use the updated build flow; upgrading does not rewrite existing images.
- Dockerfile and Compose image pins remain controlled by the repository. Review
and merge a source-update PR when the fix requires a source change, then deploy
that revision. Refreshing an unchanged pin does not change its runtime version.
- Update the mail engine as well to receive mail startup, log persistence and
restore fixes.
Openship v0.9.11 — Recommended update2026-11-06
Recommended update for Desktop sign-in recovery, assistant connections, repository
scans and deployment reliability. Includes every change merged into main since
0.9.10, with mail administration improvements and clearer runtime security updates.
Assistants and Desktop
- Codex sign-in on hosted instances — use device-code sign-in on Cloud, VPS
and remote assistant hosts, while keeping browser sign-in on the local Desktop
host. Explain the available method in AI connections, use the shared ChatGPT
mark, and update the Mindwire runtime and SDK to 0.1.61.
- Desktop account recovery — preserve verified sign-ins during refresh and
startup, and remember the administrator selected through Desktop's authenticated
sign-in. Missing or stale Local User cookies recover to that saved identity
without selecting an unrelated user's session or changing account permissions.
- Claude Code on macOS — make the system keychain available inside the
isolated assistant home so sign-in can complete.
- Investigations and questions — start an explicitly requested deployment
investigation when the assistant is ready. Answer agent questions above the
composer while retaining drafts, separate answer state and retry behavior. Keep
expanded questions focused and the latest-messages control readable.
- Assistant workspace setup — keep connection setup inline and use the shared
drawer for agents and automations. Preserve unfinished configuration and the
underlying chat, recover access to changed specialists, and refresh activation
reviews when saved settings change.
Deployments, routing and security
- Compose command updates — resolve authored command expressions against the
current service environment during deployment and Apply environment. Preserve
referenced file defaults and explicit command edits without exposing internal
source metadata as environment values.
- Environment apply failures — show structured startup, health, restart and
OOM evidence while retaining the existing replacement and rollback flow. Keep
credentials and unrestricted provider error text out of responses, monitoring,
notification failures and backup diagnostics.
- Static environment changes — offer Rebuild and redeploy for static sites
and single-app Cloud deployments whose variables cannot be applied through a
runtime-only refresh. Open the new build's progress and retain retry controls.
- Static 404 behavior — add an explicit SPA fallback setting to shared routing
controls, the API and openship.json. Keep SPA fallback enabled by default;
disabling it returns real 404 responses and uses 404.html when available.
- Compose edge inventory — inspect loopback upstream ports through the edge's
own connection, including mounted Docker sockets without host SSH. Quarantine
existing routes before allocating ports and continue refusing unreadable or
ambiguous inventory.
- Private repository scans — allow the only eligible connected server's
stored token when an organization has no local server. Ask for an explicit
server when several qualify, retain the choice across scan retries, and keep
public reads anonymous when no credential is needed.
- Parked Docker imports — offer an explicit finish-without-restart decision
for imports awaiting cutover. Keep originals untouched and provide actionable
guidance when a parked migration prevents project deletion.
- Cloud host boundaries — enforce shared safeguards against local workload
execution on the SaaS API host while retaining authorized managed-server and
SSH execution. Keep command availability probes separate from execution.
- Conditional security reviews — distinguish PHP's conditional session
upload-progress review from confirmed runtime vulnerabilities. Share advisory
guidance while retaining each service's confidence, progress and actions;
offer saved configuration and an editable, scoped Fix with AI request without
automatic submission. High and Critical warnings retain their priority.
- Database removal conflicts — reread controller state after explicit
Kubernetes version conflicts during database cleanup. Retain object identity,
ownership, generation and operation fences while tolerating status-only updates.
Mail and application catalog
- Fail2ban management — on self-hosted mail installations, inspect jail
counters and banned addresses from Health, the API, SDK and MCP. Review the exact
address and jail
before banning or unbanning; stale observations disable changes until refreshed.
- Direct alias senders — allow active direct aliases to authorize their owning
mailbox consistently across mail sender checks. Disabled aliases, external
forwards, catch-alls and alias chains grant no sender identity. Clarify the
distinction between incoming forwarding and direct-alias sending in the UI.
- Appwrite setup — deduplicate generated credential writes and verify owner
bootstrap before reporting success. Exclude the optional Geo service while its
upstream PHP runtime remains affected, and document the geolocation limitation.
- Security refresh verification — reject unchanged-image refreshes, track
manual remediation through deployment and runtime inspection, and show progress
or a verified failure instead of silently repeating an ineffective update.
Validate Compose hostname availability against scoped Cloud ownership receipts.
- Supabase images — update the catalog's Storage, Meta and Studio image pins
for the bundled Node.js/Brotli security fixes.
- RabbitMQ readiness — run probes as the image's RabbitMQ user and wait for
the management listener, avoiding the startup Erlang-cookie ownership race.
Dashboard, billing and documentation
- Theme restoration — render the saved base theme and background on the server
through a validated cookie. Preserve custom theme caching, System mode and
unsaved previews without flashing Light on refresh.
- Checkout returns — retain the purchasing organization, server and payment
receipt through hosted checkout and authorized organization switching. Keep
checkout retries tied to their original payment contract.
- Gateway failures — request JSON from the API and explain upstream proxy
errors with recovery guidance instead of showing an opaque status or HTML page.
- First-deployment analytics — wait for an active deployment before reading
traffic for a reserved domain. Start reads when deployment activates and retain
existing traffic during redeploys; genuine provider failures remain errors.
- Quickstart wording — remove an abrupt line break in the setup description.
Upgrade notes
- Update the API (including all replicas), dashboard and Desktop app together.
This patch adds no new control-plane database migration.
- If an older Desktop installation already shows only Local User and has no
saved authenticated identity, use Back to setup, Continue with Cloud and sign
in once. This preserves existing data and records the owner for future recovery.
- Apply direct-alias sender policy changes by updating the managed mail engine
image as well as the control plane. Custom SQL and host-native mail policies
remain operator-managed.
- Redeploy an existing generated static-site container after changing its SPA
fallback setting. Existing sites retain SPA behavior until explicitly changed.
- Runtime security refreshes verify the deployed result; an image that still
contains the affected runtime requires a corrected image configuration rather
than repeated redeployment. Appwrite's optional Geo service remains excluded.
Openship v0.9.10 — Recommended update2026-11-04
Recommended patch for Cloud assistant startup, recovery and OAuth consent
failures in 0.9.9. Also fixes deployments, routing and restores, and includes every
change merged into main since 0.9.9, with additional catalog applications and
optional calendar/contact sync.
Cloud, agents and GitHub Actions
- Cloud assistant recovery — preserve executable launcher permissions during
workspace uploads and recover dead assistant endpoints after checking health
inside the guest. Keep reachable busy daemons and existing profiles intact.
- Consent callbacks — let the consent form own OAuth continuation so automatic
navigation cannot consume the same callback twice.
- Customer email senders — use the SMTP transport's authorized sender by
default. Optional SMTPSUPPORTFROM and SMTPBILLINGFROM aliases require
send-as permission on that SMTP account; aliases stay out of the Cloud relay.
- Referral pricing — show referral discounts consistently in plan cards for
monthly and annual billing, using the existing shared pricing calculation.
- Pull request Actions — verify the executed merge against the captured base
and head, and publish Checks on the pull request head. Preserve trusted workflow
selection, fork restrictions and per-attempt Check identity.
Deployments, domains and backups
- Compose reconfiguration — retain existing DNS setup when redeploying to the
same destination; request setup only for new hostnames. Normalize saved endpoint
ports before submitting the deployment so source-review redeploys no longer fail
with Expected string.
- Stored image deployments — retain stored image-only Compose services and
their environment when a containerized controller cannot read the original
local directory. Source-built services still require their build inputs.
- Service www redirects — share the apex/www controls across the wizard and
Add domain form, and support editing existing service redirects. Preserve
portless redirect intent, reject missing targets and loops before service
writes, and commit domain API changes with their service endpoint atomically.
- Wildcard route rules — enforce the configured wildcard virtual host's
policies when no exact-host policy exists, while preserving exact-host overrides.
- Volume restore safety — finish and validate the incoming archive before
clearing destination contents. Failed, truncated or timed-out uploads preserve
existing data; temporary staging files are cleaned up on completion or failure.
Catalog, mail and dashboard
- Application catalog — add Appwrite, Prometheus, Alertmanager, VictoriaMetrics,
Loki, OpenTelemetry Collector, Beszel, Listmonk and pgAdmin4, with setup guidance,
service icons and runtime smoke coverage.
- Catalog port routing — publish Listmonk and pgAdmin4 on their own host ports
instead of accidentally reusing another service's port.
- Calendar and contacts — add an optional Radicale template and setup guidance
for calendar/contact sync alongside the existing mail installation.
- Error details — add a copy action to error toasts for sharing diagnostics.
Upgrade notes
- Update the API, dashboard and all API replicas together. This patch adds no new
database migration. When upgrading from before 0.9.9, also follow that release's
authentication, connection and SMTP upgrade notes below.
- Volume restores now require enough temporary disk space to stage the incoming
archive before extraction. Extraction after validation is not transactional.
- Release verification retains the published 0.9.9 Compose template so the update
gate tests the actual previous installation, including stored data and routes.
Openship v0.9.9 — Critical update2026-11-03
Critical security update covering authentication, Cloud connection approvals,
server isolation and encrypted email delivery. Includes all changes merged into
main since 0.9.8, plus deployment, billing, assistant and dashboard improvements.
Security
- Authentication dependencies — upgrade Better Auth and its plugins/adapters
to 1.7.15 and the Hono Node adapter to 2.1.3. Address OAuth state, proxy,
consent, rate-limit and static-path middleware advisories.
- OAuth and sign-in compatibility — use the provider's supported APIs for
resources, signing, PKCE and refresh rotation. Preserve GET/POST authorization
parameters, silent-request validation, signed login/MFA continuation, OIDC
callbacks and existing MCP endpoint aliases. Register resources and token
issuers from trusted instance configuration, while retaining HTTP setup and
desktop loopback support.
- Cloud connection approval — require explicit approval before connecting
Desktop to a Cloud account. Headless CLI connections require the code shown
in the terminal, bound to an expiring, single-use request and its PKCE proof.
Recheck the approving session against live state. Share Better Auth's cookie
and session handling across bridges and preserve issued bearer lifetimes.
- Client identity and limits — apply auth rate limits to the client's IP,
using the existing trusted-proxy boundary. Normalize linked-instance IP
fingerprints without combining distinct IPv6 hosts.
- Server isolation — resolve shared network/PID namespaces only through
services in the same stack; reject authored raw container references and host
namespaces. Restrict host bind mounts across HTTP, MCP, native SDK and background
deployment paths. Managed Docker repository mounts remain confined to prepared
project storage. Reading local source contents or environment values over HTTP
requires instance authority.
- Encrypted SMTP — require TLS for authenticated mail delivery, including
verified STARTTLS on submission ports. Refuse a plaintext fallback when the
server cannot provide the required encryption.
- Umami catalog — update the PostgreSQL image to 2.20.2 and verify the
catalog's configuration remains compatible.
Security advisories and host maintenance
- Reviewed host patches — inspect supported Ubuntu hosts, review the exact
package changes, and apply scoped security fixes through the dashboard, CLI,
SDK or MCP. Verify signed advisory data, trusted package origins, current
permissions and server state before execution. A kernel reboot requires a
separate review; unsupported hosts retain manual guidance.
- Observable maintenance — persist task steps and bounded logs, reconnect to
running jobs, and verify the resulting package/kernel state. Keep pending
reboots visible and expose maintenance runs from the server and Monitoring.
- Advisory preferences — let workspace owners/admins pause advisory checks,
and save each user's banner visibility preference. Show scan freshness and
availability accurately, preserve upstream severity, and explain when an
application runtime must change before refreshing images can fix a finding.
Deployments and host support
- Compose source review — show added, changed and removed source services
before redeploying. Reject a stale review, preserve saved settings when adopting
an older baseline, and retire removed services only after a successful cutover.
Preserve volumes and keep archived services available to rollback handling.
- Pinned Git builds — fetch a requested commit even when it is outside the
cloned branch. Improve submodule preparation and credential handling across
local and remote build paths.
- Edge recovery — preserve unreadable virtual-host configurations during
cleanup, and avoid identifying similarly named application containers as the
OpenShip edge.
- Arch-family hosts — use pacman for Arch/Manjaro package preparation and
component version checks instead of Debian commands.
- Fresh GeoIP data — refresh and validate the country database before creating
release tags, with a scheduled refresh workflow for ongoing updates.
- Release verification — retain the published 0.9.8 Compose template for real
upgrade tests. Retry transient Apple ticket-validation failures while still
requiring a successfully validated installer before publication.
Cloud, billing and email
- Checkout recovery — cancel unconfirmed purchases without manual cleanup,
and recover the billing workspace after removing a canceled checkout's server.
Preserve payment verification and scoped provider ownership.
- Provisioning escalation — send exhausted provisioning failures to support
once, retaining the recovery context without duplicate escalation.
- Customer emails — welcome verified Cloud signups and confirmed purchasers,
and send separate payment/renewal notices with scoped billing links. Queue mail
durably, deduplicate webhook events, recheck the recipient's verified ownership,
and retry delivery failures. The billing provider remains the invoice issuer.
- Cloud plan guidance — update the public plan descriptions and Hobby plan
guidance, and make plan-selection hints more compact in the dashboard.
Assistants and dashboard
- Connected model discovery — list models through the connected assistant
runtime and MCP, keeping connection setup and agent selection consistent.
- Agents on paid Cloud servers — prepare and run agents on an existing paid
instance while preserving host access checks, profiles and sign-ins.
- Compact tool activity — keep routine assistant lookups inline, with detailed
previews available when useful instead of expanding every tool result into a card.
- Domains and referrals — simplify domain actions and plan guidance. Use
consistent referral wording across the dashboard and website, and place referral
code entry below the plan controls.
Upgrade notes
- Deploy the API, dashboard and all API replicas together. The OAuth migration
preserves accounts and client registrations but expires legacy access/refresh
tokens: reconnect existing MCP clients, assistant connections and chat connectors.
Some older confidential clients may need to register again. Check for duplicate
(providerid, accountid) account pairs before upgrading from Better Auth 1.6.
- Replace authored container: namespace references with service:<name> for a
service in the same stack. Host bind mounts are disabled by default. Operators
of trusted self-hosted instances can explicitly enable
OPENSHIPALLOWHOSTBINDMOUNTS=true; Cloud host mounts remain restricted.
- Authenticated SMTP must support verified TLS/STARTTLS. Configure a TLS-capable
submission endpoint if the previous endpoint only accepted plaintext delivery.
Openship v0.9.8 — Recommended update2026-11-02
Recommended patch restoring scoped agent creation and agent-backed automations
introduced in 0.9.7.
- Compatible assistant runtime — update all Mindwire dependencies to 0.1.60,
which supports the required bot protocol 9 and application-managed tools.
OpenShip provisions the matching runtime on local and remote assistant hosts
while preserving existing profiles and sign-ins.
- Release verification — create, edit and reopen scoped Codex and Claude
profiles against the actual released daemon, and verify scoped agent creation
and reuse over SSH before publishing. Keep the protocol and permission checks.
Openship v0.9.7 — Recommended update2026-11-01
Recommended update introducing scoped AI agents, reviewed automations, and chat
app integrations. Includes dependency security updates and all 0.9.6 fixes.
- Agent characters — choose from 16 original flat bots with distinct silhouettes,
gazes and expressions. Give default specialists a stable individual look across
the switcher, automation setup and tool results, and preserve the chosen character
when saving a new agent. Keep the chat header to the agent's name and role.
- Monitoring AI shortcuts — prepare scoped repairs from the shorter Fix with AI
action on app issues and a read-only workspace health report from the Monitoring
header. Keep status labels in a dedicated column and move actions below details
when the list is narrow.
- Assistant action handoffs — offer a compact inline review when enabling saved
automations, approve the exact revisions together, and continue the task in the
same chat. Recheck existing permissions and reject stale batches atomically.
Clarify that authorized MCP actions should be executed and verified, not handed
back as manual instructions. Simplify the chat header and float the composer
above the transcript without reducing its scrolling area.
- AI Agents workspace — switch between the general assistant, specialists and
automations in a collapsible 340px right column. Resume each agent's last valid chat,
browse conversations from the header’s history drawer, and inspect automation runs with
their existing investigation chats. Use a right drawer on mobile and keep agent
configuration in the shared drawer. Simplify the conversation header and preserve
scoped navigation, fresh requests and paused flow controls.
- Automation editing — show Trigger, Investigate, Respond and Notify as compact
connected settings rows, with fields expanding in place and full-width hover/focus.
Keep saved summaries visible while fields load, and use matching skeletons across
the agents workspace, conversations and editors. Edit a selected automation inline
in AI Agents using the same forms, permissions and save checks as the dedicated
editor. Use one app/status line and Save/Cancel toolbar, and return to run history
after editing. Reuse the row summary in expanded chat previews. Chat-created flows
stay paused until reviewed.
- Investigate with AI — open a prepared assistant request from failed deployment
headers, failed app setup pages and active app issues. Keep the original app and
deployment context through setup, use existing permissions, and scope the handoff
to its originating account and workspace. Logs and errors stay out of shortcut URLs.
- Scoped assistant agents — create specialists with saved instructions, an AI
connection and named resource permissions. Assign tasks or select a specialist
in an automation. Each task uses one inspectable conversation, including live
follow-ups, through the existing Assistant and MCP execution path. Add agent and
automation tools to the normal API, inline task links, and paused flow drafts
for user review. Bound each task to its original authority; recheck scope changes,
deduplicate requests, and revoke temporary execution tokens on completion or agent edits.
Manage agents in an animated drawer, expand creation and editing across the screen,
choose a flat character avatar, and open scoped chats in the main assistant workspace.
The chat header identifies the active assistant or specialist and the current conversation.
Keep connection management in the overflow menu and Assistant settings.
- AI Agents introduction — show what agents can do through selectable deployment,
investigation and automation examples. Keep one enable action, a compact host choice
and original Codex/Claude Code marks. Put setup first on mobile and show a
permissions-shaped skeleton while access setup loads.
- Native harness identity — show Codex and Claude Code with their native marks
across the composer, connections, history and agent settings. Preserve the
harness’s original authentication prompts, including ChatGPT sign-in for Codex.
- Assistant live chat and composer — smooth incoming text and scrolling, expand
live thinking, and show animated tool activity with reduced-motion support. Attach,
paste or drop images with removable previews, and switch models between replies
in the same conversation. Images use Mindwire's conversation-bound uploads on the
selected agent host; size/type validation and existing workspace permissions apply.
Show immediate send progress and keep activity visible between replies and tool steps;
use a solid stop icon.
Clear the composer on send and reset conversation input to a medium-height, two-line field;
restore failed submissions with their original attachments for retry.
- Assistant Markdown — render streaming replies with Streamdown, syntax-highlighted
code, readable tables and nested lists across light, dim and dark themes. Keep copy
controls tied to completed text and retain safe links without loading model-supplied
images or executing raw HTML.
- Assistant access and tool results — stop offering instance-only diagnostics
to workspace-scoped MCP connections. Keep the shared instance authorization gate
for direct calls, and refresh completed chats after permission edits. Retire stale
access requests and carry the last request into a new chat as an unsent draft.
Add expandable tool activity, per-call request/result inspection, and inline app,
server, deployment, service and repository cards using the existing view/import flows.
- Assistant in chat apps — talk to your own Claude Code or Codex agent from Slack,
Discord, Telegram and Teams through the existing Assistant runtime and MCP grant.
Workspace allowance and personal opt-in start off. Conversations are isolated by
sender and chat; history, resume, new and stop reuse native conversations. Continue
chat-origin conversations in the dashboard with the same approved access. Choose
dedicated Assistant, deployment-command or combined bots.
Durable replies read the exact native turn, including after dashboard continuation,
and survive delivery retries without replaying turns. Access
changes stop further execution. Add settings and per-provider setup guidance;
preserve private command replies and assistant threads in the shared chat transport.
- Assistant automations — add Assistant settings and an opt-in flow editor for
failed deployments and confirmed service incidents. Investigate and notify,
request approval, or explicitly choose app recovery and repository permissions.
Support custom API endpoints and models, code fixes on new branches and draft PRs.
Each flow stays within existing Assistant consent; exact patches are reviewed
before approval and published through shared GitHub operations. Results appear in
the agent conversation, with optional existing notification channels.
Reuses MCP, deployment, jobs and notification paths, with private investigations,
fresh health verification, run history, cooldowns and daily limits. Duplicate
incidents and action retries cannot execute twice; changing access or pausing
invalidates pending work. Cloud agents remain on the chosen customer server.
- Chat app commands — connect Slack, Discord, Telegram or Microsoft Teams in Settings to
list projects, check deployments, open private logs, and confirm redeploys or restarts.
Each sender links their own account through the existing permission flow. Commands are
opt-in, use the normal deployment path without AI, and deduplicate provider retries.
Slack Socket Mode, Discord Gateway and Telegram polling work from Desktop or private
servers without a public URL. Connections report their status, reconnect and recover
durable cursors; Teams retains its public HTTPS webhook requirement. Bot connectivity
runs directly in OpenShip
Openship v0.9.6 — Recommended update2026-11-01
Recommended update for database recovery, reliable builds and migrations, GitHub
Actions scheduling, and managed infrastructure updates.
- Recover PGlite after a container crash — hold a Linux kernel file lock so
reused PIDs cannot strand the database or admit an owner in another container.
Preserve conservative checks for older locks and other operating systems (#1524).
- Keep Docker build failures readable — surface the cause before long generated
commands, preserve the full output in build logs, and retain Cloud recovery
guidance after reload. Exit 137 is reported as a killed process with possible
memory pressure, without claiming a confirmed out-of-memory event.
- Keep monorepo runtime images aligned with each service — use the service's
framework and selected builder for its runtime instead of inheriting an
unrelated parent image. Fill missing builders from the stack registry, preserve
explicit runtime selections for unchanged apps, and use the same resolution
when checking whether runtime images can be refreshed.
- Add a scoped Kubernetes manifest foundation — admit supported resources into
a project's namespace with ownership checks on objects, pod/job templates and
selectors. Validate the full change against Kubernetes before writing, reject
changed Job definitions, and preserve conflict checks when updating or pruning.
Exercise apply, update and cleanup against K3s in CI and the release gate. This
foundation does not yet expose a manifest upload UI or deployment route (#1039).
- Preserve live Docker logs — decode stdout and stderr independently across
split frames and UTF-8 characters, keep TTY logs intact, and report malformed or
truncated streams so the existing reconnect flow can recover (#1482).
- Support verified self-hosted OIDC sign-in — discover a configured identity provider and
verify signed ID tokens, issuer, audience, expiry and sign-in nonce before
creating sessions. Preserve invitation and two-factor checks, require matching
UserInfo subjects, and refuse insecure or redirected provider endpoints. Require
verified email, scope accounts to the issuer and exact subject, and keep instance
OIDC disabled on Openship Cloud and outside local-account auth mode (#1489).
- Keep BuildKit sessions alive — answer Docker’s session health checks so
builds can use optional secret mounts after long install/build steps. Close
sessions on completion, cancellation, and transport errors (#1488).
- Move digest-referenced images between servers — use the reference restored
by Docker load for migration's one-time deployment handover. Direct and relayed
transfers no longer try to create a Docker tag containing a digest (#1526).
- Move stateless single-app projects between servers — deploy a project-owned
app with no service rows through its single-app pipeline using the transferred image.
Reject unsafe empty service scopes before copying data or stopping the source;
reused containers stay outside the deployment scope. Single apps with mounted
data remain unsupported and are refused before data movement (#1525).
- Keep queued GitHub jobs moving — replace a registration that GitHub assigned
to another job, and only count spare registrations whose runners remain admitted
and capable for the waiting workflow. Excluded runners, stale approvals and
incompatible hosts no longer block dispatch (#1505, #1509, #1541).
- Keep Cloud diagnostics available during replica startup — allow bounded
schema initialization to wait for another replica, while preserving the short
write deadlines and local-log fallback used during normal operation.
- Recover health after a service container is replaced — refresh only the
stale service binding when the continuous watcher verifies a healthy successor
under the same active deployment. Preserve native and Compose service identity
through managed edge updates and rollback; leave unrelated services and
deployment history intact (#1496).
- Scan private repositories with server credentials — repository preparation,
monorepo folder selection and branch rescans use the shared GitHub credential
chain, including the selected self-hosted server's saved token. Without a
selection, only the active organization's local server is eligible. Borrowing
requires repository access and server write permission; SSH provisioning,
GitHub mutations and Cloud authentication remain unchanged (#1500).
- Match Laravel worker suggestions to production dependencies — suggest the
standard queue worker when Horizon is only in require-dev, matching the
default Composer --no-dev install. Explicit role choices remain available (#1171).
- Keep runtime roles available after removing attached services — a single
source app retains its existing deployment and role configuration flow after
the last attached service is removed or disabled, preserving its service and
routing identity (#1308).
- Prevent false stale-role warnings after deployments — background image
cleanup updates storage measurements without changing the project's configuration
revision. Real configuration edits still invalidate previously reviewed changes.
- OpenShip Earn — explain the Cloud affiliate program at /affiliates, with
an interactive commission split, monthly and annual reward timing, payout
guidance, and a dedicated social preview. Label the dashboard affiliate entry
Earn with a gift-box icon in the left sidebar.
- Start CockroachDB services correctly — pass the required single-node
command to the official image, generate an application password, and persist
TLS certificates alongside the existing data volume. New services keep TLS and
password authentication enabled; container replacement preserves both data and
certificates. Include recovery steps for saved services missing the command
(#1484).
- Recover storage from slow build-cache scans — when free disk space or inodes
already block deployment, allow up to two minutes to measure unused, owned build
caches before reclaiming them. Healthy hosts retain the short best-effort scan;
defer timed-out SSH measurements during automatic retention without blocking
unrelated builds. Explicit cleanup still reports measurement failures; active
builders and application volumes remain protected (#1527).
- Reclaim images from interrupted first deployments — include projects that
have never reached a running release in managed image collection. Resolve the
last attempt through the existing tenant checks and retain the same rollback,
retry, pin and in-use protections, so failed builds cannot fill the server with
orphaned images.
- Cloud affiliate program — create and revoke referral links with optional
customer discounts, follow verified payments, renewals and expiry, and request
reviewed cash payouts. Staff can review pending requests in a private operator
queue and reconcile transfers, including after an account is deleted.
Oblien owns the ledger and atomically reserves payout
funds. The default minimum is $50, with trusted per-user overrides. Eligible
monthly and annual Cloud compute starts at $10 per month equivalent; Manage,
PAYG and top-ups are excluded. Program guidance lives beside the referral lists,
with illustrated empty states, a two-step discount and plan picker, monthly/yearly
eligibility enforced at checkout, encrypted manual payout accounts with immutable
request destinations, payment-method guidance and a screenshot
walkthrough in the docs. The program remains off until the provider and
its explicit policy grant are configured.
- Review shared environment edits — preview which services inherit an edited
project variable, then save shared values and service overrides together. Stale
reviews are rejected inside the write transaction; project write access is
required, an
Openship v0.9.5 — Critical update2026-10-24
This hotfix restores self-hosted Compose startup after the 0.9.4 update.
- Restore dashboard readiness and edge startup — bind the dashboard's Next.js
server to 0.0.0.0 inside its container so the loopback healthcheck can reach it.
Apply the same bind setting in the CLI-generated, reference self-hosted and
from-source Compose environments. Published host ports retain their existing
loopback defaults (#1461).
- Test the complete customer upgrade — gate image publication on upgrades from
0.9.3 and the previous release using their published API, dashboard and edge
images and CLI templates. Verify populated PostgreSQL and Redis storage, custom
ports, preserved secrets, admin credentials and signed sessions, saved edge
routing, dashboard-to-API access, cold
restart and fresh installation. Probe both dashboard image architectures before
publication; an API-only migration check no longer stands in for a stack upgrade.
- Explain source rebuild prerequisites before a security refresh — global and
project advisory views use the same runtime-update preflight as the deployment
action. Replayed or revisionless source images show their prerequisite and an
Open source redeploy action instead of offering a refresh that will fail.
Redeploy still uses the existing project deployment controls; source provenance,
image pins and tenant authorization remain enforced (#1462).
- Include the packaged-worker image correction — source builds of managed
workers require Git checkout metadata. Bundled Dockerfiles in the released API
no longer trigger a development worker build.
Recovery from 0.9.4
Run openship update after 0.9.5 is published. The update recreates the API,
dashboard and edge through the normal pipeline and preserves existing database,
Redis and application storage. For a temporary recovery on 0.9.4, set
HOSTNAME: "0.0.0.0" in the dashboard service's Compose environment and run
docker compose up -d with that installation's existing Compose file and project
name. A later CLI run regenerates that file; update to 0.9.5 for the permanent fix.
---
Announcement metadata corrected for all installation modes; built artifacts remain byte-identical. Original build source: f1a021ec7c034761090ebfd10d7ea209236e0201; advisory source: c4e440e6eba4975d348c95d8432148f2951a58a9.
Openship v0.9.32026-10-17
This release improves Cloud monitoring and build-cache reliability, adds deployment
automation and isolated pull-request previews, and makes workers and schedulers
easier to configure, observe and recover. These notes cover all merged changes
since 0.9.2.
Deployment automation and previews
- Move command variables into Environment — review literal environment
assignments in install, build and start commands, then migrate them into
encrypted project or service settings. Conflicts and concurrent edits stop the
migration before partial changes are saved. Import and saved settings share the
same parser and guidance.
- Prepare framework output automatically — Next.js standalone monorepos and
Nuxt builds retain their required workspace dependencies, public/static assets
and selected Node or Bun runtime. Managed direct-server defaults start from the
configured app directory; explicit custom commands retain their working directory.
- Review older manual cache mounts — detect duplicate package/framework cache
mounts and offer configuration migration only after a successful build proves
managed cache support for those paths. Existing volume data is retained. Build
logs report observed cache reuse and build-time comparisons.
- Catch setup problems earlier — pre-install checks identify missing app roots
and environment examples; command-variable, standalone startup and duplicate-mount
guidance explains what needs attention without exposing variable values.
- Opt into GitHub pull-request previews — same-repository, non-draft pull
requests can deploy their exact commit into a separate preview environment with
preview-only variables, isolated volumes and per-service URLs. Production
variables are not copied. Forks and unsafe shared-storage configurations are
excluded.
- Recover preview lifecycle operations — durable coordination handles repeated
webhooks, controller restarts and retryable close/merge cleanup. Optional GitHub
comments update one existing comment, alongside the existing deployment Checks.
Whole-instance transfers preserve preview ownership; individual project imports
clear preview automation that cannot safely transfer.
- Use automation from the SDK — configure and list previews, inspect or migrate
manual cache mounts, and move command variables through the shared validated
project operations.
Workers, schedulers and rollback
- Configure roles without rebuilding the web app — Apps & Services → Configure
roles can add or change workers and singleton schedulers on active single-app
self-hosted Docker deployments. The normal deployment engine reuses the verified
image and frozen environment while preserving the web container and unchanged
replicas. The API, SDK and CLI expose the same operation. Cloud, bare, static,
cluster and multi-service targets are outside this editor's scope.
- See and inspect background processes — runtime roles appear in project
service views and topology, with role/replica log selection and retry states.
Health monitoring includes worker and scheduler failures instead of observing
only the foreground container.
- Keep independent role suggestions — framework scans expose matching presets
at the selected app root. Only presets competing for the same declared slot
exclude one another; explicit roles, including an empty list, retain precedence.
Suggestions do not automatically enable background processes.
- Recover interrupted role handovers — persist exact container identities and
ownership before replacement, predecessor shutdown and publication. Startup and
deployment reconciliation either finish a published handover or safely restore
its predecessor; uncertain cleanup remains pending before conflicting work.
- Protect active and rollback images — retained role replicas keep their
required image artifacts protected during configuration changes and release cleanup.
- Restore frozen Compose environment accurately — rollback preserves encrypted
deployment snapshots without confusing literal redaction-like values with missing
secrets. Incomplete legacy snapshots fail clearly rather than borrowing mutable
current service settings.
Cloud monitoring, caches and storage
- Avoid expensive monitoring scans — Cloud hosts using fuse-overlayfs skip
Docker's full storage inventory, which can exhaust daemon memory. Host totals
remain measured; unavailable detailed project storage stays unknown.
- Show guest RAM usage — use verified guest counters instead of hypervisor
process memory and overhead. Older guests receive a bounded, read-only memory
sample; stream teardown releases the executor.
- Keep partial metrics useful — missing disk or memory fields in a live frame
retain the latest measured value for that metric, with its measurement time.
Purchased capacity is never substituted for measured consumption.
- Keep Cloud cache cleanup scoped — collect only owned, idle project-worker
caches and stop before Docker Engine's global builder prune. Cache reuse, worker
GC, existing build concurrency and user-configured resource limits are unchanged.
Cloud builds require their isolated BuildKit executor instead of silently falling
back to the embedded builder. Existing legacy daemon state and autonomous Docker
GC remain separate host-maintenance concerns.
- Accept filesystems without fixed inode totals — unsupported or zero inode
totals mean unknown availability rather than confirmed exhaustion. Real free-space
and supported inode-exhaustion checks still protect deployment admission.
Domains and ingress
- Route verified custom domains on first deployment — single-app domains
without a saved destination use the verified serving port through the shared
route planner. Explicit endpoints and service-group destinations retain their
ownership instead of selecting a sibling service.
- Avoid ephemeral secondary host ports — secondary loopback publications use
the existing allocator and the target host's ephemeral-range checks.
- Handle varied Cloudflare Access applications — accounts containing launcher
or other domain-less applications no longer crash managed ingress setup.
Inventory and write receipts are validated while overlap and foreign-resource
ownership protection remain enforced.
- Clarify edge availability — documentation explains edge failure behavior and
recovery responsibilities for deployed applications.
Webmail
- Resolve exact Message-IDs for actions — thread reads, deletion, labels and
flags validate exact IMAP envelope identities instead of trusting substring
search matches. Literal percent sequences remain unchanged, stale UID hints are
rejected, and missing or refused operations no longer report success.
- Cache application assets correctly — fingerprinted assets receive immutable
caching while application HTML is revalidated.
- Serve precompressed assets — negotiate available Brotli or gzip files with
appropriate content types, encoding and cache headers.
Openship v0.9.22026-10-16
This patch adds worker and scheduler execution, personal appearance customization,
and managed Cloudflare Tunnel setup for self-hosted servers. Cloud spaces, reusable
build caches, more catalog apps and safer storage cleanup improve everyday
operations. These notes cover all merged changes since 0.9.1.
Workers and schedulers
- Run roles beside your web app — declare workers and schedulers in
openship.json or the project API. Single-app Docker deployments start separate
containers from the app image, with shared environment, volumes and connected
networks, their own commands and shutdown settings, and no published ports.
Roles follow pause, resume, restart, rollback and project deletion.
- Hand over singletons safely — scheduler renames, command changes, name swaps
and conversions into workers stop and retain outgoing singletons before starting
potentially conflicting replacements. Failed deployments restore them only after
those replacements are confirmed removed. Failed retirement of an old role is
surfaced in the deployment warning with its container identity.
- Require a verified startup — every replica needs exactly one stable result
for its container ID before optional exec health checks run. Missing inspections,
duplicate results and processes that already exited successfully fail startup.
Both project-defined and image-inherited PORT values are removed from roles.
- Make role configuration explicit — move and copy refuse active, unfinished
or preserved-cancelled role workloads even after saved roles are cleared.
Preset-only when and unless keys in declared roles produce warnings rather
than silently appearing to control execution. Automatic framework role selection
and cross-server role migration are not included.
- Improve framework shutdown defaults — Rails presets have measured stop
settings, and Laravel's scheduler preset uses SIGTERM with a 10-second grace
period while queue and Horizon workers retain 90 seconds. Customize these bounds
for long-running tasks; they do not guarantee task completion or exactly-once
scheduling. Laravel web-role cache warming is available as an opt-in setting.
Appearance and dashboard
- Customize your own appearance — Settings → General → Customize previews
color tokens and typography live, with explicit Save, Discard and Reset.
Import themes from JSON, a file or an HTTPS URL; export themes and libraries,
including supported WOFF2 fonts. Preferences belong to the signed-in user and
stay isolated across accounts and instances. API, SDK, CLI and MCP operations
use the same theme format.
- Keep operational tools together — project monitoring and logs share one
navigation entry with their own views. Backups moves under Infrastructure.
Project sidebars show assigned domains, migration retries retain destination
choices, and migrated service deployments use the correct icons.
- Reduce false outage alerts — the health watcher confirms repeated bounded
Docker probe failures before announcing a server outage. Late probe replies
cannot falsely announce recovery. Self-hosted administrators can clear resolved
monitoring history with confirmation while retaining open incidents.
- Improve navigation and terminal reliability — GitHub discovery no longer
blocks dashboard pages, selection controls use consistent states, and leaving a
server terminal during WebGL loading cancels setup and disposes the terminal.
Instance connection and move actions have clearer setup and recovery guidance.
Cloudflare Tunnel and domains
- Manage self-hosted ingress from Openship — Server → Security can connect or
create a remotely managed named Cloudflare Tunnel using saved credentials,
configure proxied DNS and optionally apply an existing reusable Access policy.
Install a pinned connector on a supported Linux server or use its existing
connector. Managed Openship Cloud routing retains its existing path.
- Enroll domains with recoverable setup — explicitly enable automatic tunnel
enrollment for new custom domains or connect existing domains individually.
Setup records Access, tunnel and DNS progress, supports retry after interrupted
requests, and removes only owned resources. External edits remain visible for
review instead of being overwritten. Exact hostnames and www companions are
supported; wildcard auto-enrollment is not.
- Choose primary and www behavior — the deployment wizard defaults a newly
included companion hostname to a 301 redirect to the entered primary. Choose
bare primary, www primary or Serve both on Cloud and self-hosted destinations.
Redirect rows show their target instead of duplicate runtime inputs.
- Keep domain operations consistent — service aliases on the same port are
preserved, domains added through the CLI receive routing, and Cloud routing
retries recover missing Pages through the owning Cloud connection.
- Honor trusted proxies on containerized edges — operator-declared proxy IPs
reach the edge without rebuilding its image. Invalid addresses and CIDR prefixes
are discarded. Failed configuration updates restore the previous shared trust
include, and an incomplete rollback cannot activate a partial configuration.
Cloud spaces, billing and connections
- See managed capacity as Cloud spaces — a shared picker, Overview and
Activity views show projects, purchased capacity and measured usage, with clear
retry states for unavailable readings. Existing allocations and subscriptions
keep their identity; connected self-hosted server tools remain available.
- Use the owning Cloud account consistently — connected Desktop and
self-hosted installations create Cloud projects through Cloud's API. Server,
project and deployment operations enforce their organization and provider
namespace. Cloud consent shows the actual account and organization and lets you
switch either before explicitly authorizing the connection.
- Continue purchases without repeating plan selection — pricing links carry
the chosen plan into the signed-in app's checkout flow. Pending unpaid payments
can be cancelled when supported by the provider so another plan can be selected;
retries retain the original payment identity. Server cancellation is easier to
find and repeated requests cannot create duplicate operations.
- Configure Actions on existing spaces — Cloud's Add runner flow opens the
capability form directly with the space picker. Local Actions lists remain
available when Cloud discovery fails, and official runner containers support
non-root SSH supervisors. Temporary runner profiles retain their separate
funding flow.
- Keep instance handoff with its source — control-plane provisioning on a
linked managed destination stays owned by the source controller until the move
transfers the instance, including resumed API-only and dashboard installations.
Build performance and resource control
- Keep unconfigured resources uncapped — omitted build and service CPU/RAM
limits no longer become sampled capacity caps or catalog sizing recommendations.
Containers share the selected server's capacity unless limits are explicitly
configured. Cloud plans and VM capacity still apply. Existing saved limits are
preserved; select Full capacity to remove an older unwanted limit.
- Allow concurrent Cloud submissions — different projects can submit builds
while a sibling build is active. Unspecified resource dimensions remain shared;
explicit limits, saved plan concurrency and exclusive maintenance protection
remain enforced.
- Reuse bounded project build caches — compatible builds retain project-owned
BuildKit state and supported package/compiler caches while temporary workers
are removed. Idle cache collection uses retention targets and storage-pressure
checks, preserving active workers, release ima