← 変更履歴

v0.8.1

Openship Cloud now runs projects on managed servers with their own monthly plans. Share a server across applications, add another when you need it, and manage your Cloud resources alongside local projects from desktop or self-hosted Openship. This release also adds passkeys, authenticator 2FA and a private support inbox, expands CLI automation, and improves billing, migration and deployment recovery.

1 リリース
10月6日2026v0.8.1特長修正セキュリティ50 件の更新情報

マネージドクラウドサーバー

  • 1 つのサーバー、複数のプロジェクト

    Each managed server has its own subscription and shared CPU, RAM and disk. Builds, applications, Compose stacks and catalog services use the existing Docker and Bare deployment engines. Creating a project no longer allocates a separate VM or reserves another disk (#1036).

  • Docker または直接実行を選択します

    Use Docker for containers and Compose, or run compatible source applications as supervised host processes with Direct. The shared destination picker can select an existing server or start a purchase for another. New eligible source apps default to Direct below 2 GiB RAM; saved projects and explicit runtime choices are preserved (#1064).

  • 購入した容量を使用する

    A service can use the server's full available CPU and RAM, or use a custom container limit. Fractional CPU settings, including Micro, reach Docker correctly. Source builds use available server headroom and optional build caps; image-only installs do not start a source builder. Applications, builds and the operating system still share the host.

  • 容量とは別に使用量を検査する

    Server monitoring distinguishes the purchased disk size from measured usage. Project containers and volumes have a disk breakdown, with shared images, build cache and system data shown separately. Missing readings stay unknown, and undeployed drafts no longer inflate running-service counts (#1011).

  • 必要なときにサーバーを管理する

    Reuse server diagnostics, terminals, listening-port checks and resource views. Networking controls outbound internet access; the Activity tab holds provisioning and resize logs. Scheduled command jobs can target shared or separately subscribed managed servers.

  • 隣接するプロジェクトを失わずに運用を回復

    Provisioning, resize and interrupted deployment work retain progress for retry. Resizing restores previously running services while leaving intentionally stopped ones stopped. Project deletion removes its own resources and preserves the shared server; server deletion checks remaining projects and subscription state.

デスクトップおよび自己ホスト型のクラウド アカウント OpenShip

  • 接続すると既存のクラウド リソースが表示されます

    Cloud projects, apps and managed servers join the local inventory. A server already linked to the installation appears once. Cloud-owned settings, deployment history and operations stay in Cloud rather than becoming local project copies (#1074).

  • 同じダッシュボードから管理対象サーバーを購入して使用する

    Cloud subscriptions and provisioning remain in Cloud. Local projects can select an authorized managed server through the same destination picker as SSH servers, using an execution link for deployment, logs, terminals, jobs and backups.

  • アカウントを切り替えると、以前のアカウントの状態がクリアされます

    Inventories, project details, deployment history and billing responses follow the selected Cloud account and organization. Connections are revalidated for live operations; locally scoped automation credentials do not inherit the owner's Cloud account.

請求とプラン

  • 月額サーバーには有料期間全体が含まれます

    New monthly plans cover purchased CPU, RAM and storage without a second compute-credit allowance or a monthly build-time cap. New offers have no project or running-service count limit; workloads share the server's physical capacity. Optional managed proxy transfer and storage retained after coverage ends remain separate charges.

  • 改訂された計画とカスタム リソース

    Hobby is $5/month for 1 vCPU, 4 GiB RAM and 25 GiB disk; Starter is $20 for 2 vCPU, 8 GiB and 32 GiB; Pro is $39 for 4 vCPU, 16 GiB and 128 GiB; Scale is $99 for 8 vCPU, 32 GiB and 256 GiB. Custom lets you choose CPU, RAM and disk and review a quote before checkout.

  • 請求は選択したサーバーに従います

    Switch servers without losing the page, inspect each subscription independently, or use サーバーの取得 新しい購入のために。初めての顧客には、空の使用状況画面ではなくプランが表示されます。小規模なアップグレード比較により、カードがコンパクトになり、最新計画の概要が個別に表示されます。支払い方法と請求書はサーバーの Stripe ポータルを共有します。

  • 計画の変更を適用する前に確認する

    Show the provider's prorated amount, effective date and affected projects. Capacity upgrades apply after confirmed payment; resource reductions and billing-mode changes wait until renewal. Pending changes remain visible, and a resize requires restart consent. Disks can grow but cannot shrink in place.

  • チェックアウトには回復パスが表示されます

    Payment confirmation, paid coverage and server readiness are separate steps. Setup failures expose progress and retry without asking for another purchase; the welcome dialog appears when setup completes. Unavailable offers show a dedicated dialog with retry and a support request for availability updates (#1062).

  • 未完了の支払いを再開またはキャンセルする

    保留中の支払い 各サーバーの保存されたオファーをリストし、元のチェックアウトを開きます。プロバイダーが確認したキャンセルにより、別のプランを選択したり、未使用の未払いのサーバーを削除したりできます。クラウドと接続されたインストールは回復フローを共有し、アカウントを切り替えると、以前のアカウントの支払い詳細と応答が破棄されます (#1067)。

  • プリペイド PAYG レベルのプレビュー

    Compare three shared resource-pool tiers, configure server resources and select a credit package in one calculator. The estimate separates active vCPU-hours, reserved RAM and storage, with hourly costs and balance-duration scenarios. Enterprise contact is available in both purchase views. PAYG purchases remain disabled in this release (#1057).

アカウントのセキュリティと GitHub

  • パスキーと認証システムの 2FA

    Settings → Security supports passkey registration and removal, authenticator QR setup, and single-use recovery codes. Enabled 2FA also applies after social and passkey sign-in. These controls are available on Cloud and self-hosted installations with local accounts (#984).

  • 障害発生時でもアカウント保護は一貫性を維持

    Credential changes commit together, concurrent requests cannot reuse a challenge or recovery code, and password resets do not disable 2FA. OAuth, invitation and MCP handoffs resume after verification. Security setup state clears when the account changes.

  • GitHub リポジトリへのアクセスはサインインとは無関係です

    One GitHub identity can authorize repositories for multiple Openship accounts without transferring login ownership. Reconnect existing installations from the shared connection flow, including direct installation links, and see completion or failure for each attempt (#992).

  • 個人トークンはリポジトリ フロー全体で機能します

    Git settings remain reachable through the alternative connection option. A verified token can supply repository and owner listings and private-source access when no GitHub App connection is available. Account avatars and Git URL entry are clearer.

サポートとオンボーディング

  • プライベートクラウドサポート受信箱

    Submit deployment, billing, account or general tickets, search your history, reply and resolve or reopen a conversation. The same personal ticket history is available from Cloud-connected desktop and self-hosted installations. Team membership does not expose another user's tickets (#1073).

  • サポートおよびお問い合わせページは永続的なリクエストを受け付けます

    Submissions are saved before email delivery, with a receipt and notification to [email protected]。配信の再試行は API の再起動後も継続され、サポートの返信が受信箱に表示され、顧客に電子メールで送信されます。再試行された送信では、別のチケットを作成するのではなく、元のレシートが再利用されます (#970)。

  • より明確な初回実行画面とアカウント画面

    Refreshed Cloud plan prompts, purchase welcome dialogs, email-verification and password-reset completion screens. The home page omits empty system-status cards for new Cloud accounts, and already subscribed users do not keep seeing the first-purchase promotion.

アプリと移行

  • アプリには独自の場所がある

    A dedicated Apps sidebar entry and list keep catalog applications separate from source projects. Compact home rows, restored empty states and clickable app illustrations make discovery less cluttered.

  • より一貫性のある展開ウィザード

    Share destination and server controls across Cloud and self-hosted modes, with Full/Custom power choices, filled inputs, compact Build/Start settings, readable deployment-step icons and clearer draft project details. App install forms support grouped and two-column layouts.

  • アプリのインストールではルーティングとリソースの選択について説明します

    Public dashboards start with domain routing and ask for confirmation before continuing without a recommended domain. Self-hosted app CPU/RAM recommendations are advisory; failed Cloud installs can be retried or cleaned up without treating an absent runtime as a teardown failure (#1009, #1016).

  • Docker 個のアプリケーションをマネージド クラウド サーバーにインポートします

    Reuse the existing migration engine for images, environment, volumes, bind data and routes. Cloud can connect an external SSH server as a migration-only source. Target preparation, saved progress, verification and explicit cutover support recovery; source data is preserved and source-container retirement requires consent.

  • カードまたはトポロジとしてインポートを確認する

    Compact expandable service cards are the default, with a topology view, expand-all controls, repository linking and clearer Custom, Free and Internal-only routing choices.

ビルド、デプロイメント、およびリカバリ

  • Stop は選択したビルダーをキャンセルします

    Cancellation reaches the worker's actual Docker or Bare runtime, including remote Git and archive preparation. The UI shows 停止中… クリーンアップが完了するまで、再デプロイメントが許可されます。ビルドをキャンセルすると、ビルド ラベルを継承したデプロイされたコンテナーが保持されます。あいまいなサービス所有権は依然としてアクティベーションをブロックします (#1059)。

  • ビルド出力は読み取り可能な状態を維持します

    Cloud Docker streams preserve raw bytes, partial lines, UTF-8 characters and terminal progress updates. Uploads finish correctly when stdin closes. Disk and inode exhaustion are explained separately from memory failures, and temporary BuildKit cache is reclaimed after builds (#1058, #1064).

  • 変更されていない Compose サービスは引き続き実行されます

    Folder uploads and snapshot syncs no longer mark unchanged image services dirty. Import metadata preserves concurrent configuration edits; inherited project resource changes still apply while respecting per-service overrides (#989).

  • 導入前のバックアップはアクティベーション前に完了します

    Deployments wait for all configured pre-deploy backups and their cleanup, including when reusing a build. Failed backups offer retry, an explicit skip or stop. PostgreSQL dumps must succeed, and suspiciously small dumps are rejected against recent comparable backups before becoming restore points (#1060).

  • リモート ビルドと静的リリースは正しいパスを使用します

    Subfolder refreshes preserve root manifests and rescan at the project root. Static output resolves relative to that root, and retained artifacts are checked on their deployment destination for rollback. Directory-only .dockerignore 否定は尊重されます (#1010、#1041)。

  • ヘルスチェックとシャットダウンはランタイムを考慮します

    Configured single-app readiness probes run through the deployment server; unreachable SSH leaves a check unverified. Docker replacement honors stop signals and grace periods, probe watchdogs are reaped, and Bare services retain the correct user privileges and artifact ownership (#1043).

  • Farm.js の検出

    Identify Farm.js applications and supply the framework's build and output defaults (#1037).

ドメイン、ネットワーキング、監視

  • 無料のドメインは選択した管理対象サーバーに従います

    Availability and quota checks retain the destination through project creation, Compose synchronization and deployment. Route changes are validated before related settings are saved; editing an existing route at the limit does not count it as a new route (#1064).

  • ドメイン設定から Cloudflare に接続します

    Add and verify a DNS credential without leaving the DNS panel, review proposed records, then apply them. Cloudflare TXT quoting and Cloud certificate-status handling are corrected, while certificate checks verify the domain's project binding (#977).

  • より信頼性の高いワイルドカード HTTPS とエッジ回復

    DNS challenge hooks pass Certbot validation, Compose installations detect Edge correctly, and challenge route cleanup checks ownership. Whole-project rules handle a null path prefix correctly. Projects no longer have the unrelated 20-public-endpoint schema cap (#1054, #1003, #1017, #1045).

  • ソースの更新は、展開が完了するまで表示されたままになります

    The project deployment tab indicates available updates; unchanged image services are not refreshed unnecessarily. Updates on the local Openship instance use the appropriate advisory flow, and resource reporting accepts current Docker runtime limits (#1006, #1047).

  • 接続とセットアップの修正

    Recover Cloud Docker connections after credential rotation, report missing proxy/bridge failures clearly, correct registry TLS/WebSocket dependency compatibility, and handle Docker networks without subnets during cluster setup (#970, #1068, #961).

SDK、CLI、プラットフォームの修正

  • Ship SDK と CLI によるさらなる管理

    Add commands for project resources, environments, storage and connections; credentials and DNS; monitoring, notifications and webhooks; workspace access and audit history. They use the shared platform operations and permission checks.

  • より安全なコマンド ターゲティングと環境編集

    Each CLI invocation keeps its selected endpoint, credential and organization. Directory links reject mismatched contexts. Partial service environment edits preserve other values and secret classification; full replacement is explicit. Deployment waits have deadlines and expose pending decisions, and request logs can be followed through the SDK's authorized Cloud stream.

  • より明確な MCP クラウド ワークフロー

    Discover authorized managed destinations and deploy desktop folders through a connected server. Explicit promotion to Cloud can resume from its saved receipt after an interrupted response or cleanup, without importing the project again (#1056).

  • Webメールとダッシュボードの修正

    Spam, Not spam and Archive move messages into the correct IMAP folders. Notification settings and icons recover from hydration races, Teams accepts current Microsoft webhook hosts, member-access settings avoid repeated refetches, and background project deletion preserves navigation (#981, #1004, #1008, #1035, #1024, #1066).

  • API の起動と一括アクションの検証

    Capacity previews pass the startup permission scan, and malformed bulk container requests are rejected instead of being interpreted as an empty request (#1033, #994).

  • オプションのクラウド製品分析

    The hosted Cloud API can send configured PostHog events for signup, deployment and verified checkout/payment outcomes. Delivery is queued separately from those operations. Telemetry runs only on the hosted Cloud API; local operations, logs, secrets and session recordings are excluded.

データ移行とアップグレードに関する注意事項

  • 完全でポータブルなエクスポート

    Instance and project archives include plaintext environment values, server keys and credentials by default, without an export password. Treat the archive as sensitive or explicitly omit secrets. Imports still accept older encrypted archives and encrypt credentials with the destination's key.

  • インポートではスコープと選択されたデータが保持されます

    Instance imports default to full replacement after confirmation. Project overwrite removes destination-only records in selected categories and applies cleared credentials atomically. Project analytics retain normalized hostnames, including www;サポートされていないアーカイブ フィールドは、データを変更する前に拒否されます。

  • クライアントを接続する前にクラウドをアップグレードする

    New inventory and support features require the matching Cloud API. Desktop-initiated cancellation fixes require an updated desktop controller. Existing per-project Cloud deployments need an explicit migration to managed servers; updating alone does not consolidate VMs or replace saved subscription terms.

  • アカウントのセキュリティ構成を安定した状態に保つ

    Self-hosted passkeys require HTTPS and a stable dashboard hostname through OPENSHIP_PUBLIC_URL (localhost は開発用にサポートされています)。保持してバックアップする BETTER_AUTH_SECRET、オーセンティケータの秘密と回復コードを保護します。