6 oct2026v0.8.1CaracterísticasCorreccionesSeguridad50 actualizacionesCopiar enlace
Servidores en la nube administrados
Un servidor, múltiples proyectos
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).
Elija Docker o Ejecución directa
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).
Utilice la capacidad que compró
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.
Inspeccionar el uso por separado de la capacidad
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).
Administre el servidor cuando lo necesite
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.
Recuperar operaciones sin perder proyectos vecinos
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.
Cuentas de nube en escritorio y autohospedadas OpenShip
Tus recursos existentes en la nube aparecen cuando te conectas
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).
Compre y use servidores administrados desde el mismo panel
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.
Los cambios de cuenta borran el estado de la cuenta anterior
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.
Facturación y planes.
Los servidores mensuales incluyen su período de pago completo.
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.
Planes revisados y recursos personalizados.
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.
La facturación sigue el servidor seleccionado
Switch servers without losing the page, inspect each subscription independently, or use Obtener servidor para una nueva compra. Los clientes nuevos ven planes en lugar de pantallas de uso vacías. Las comparaciones de actualizaciones más pequeñas mantienen tarjetas compactas y un resumen del plan actual por separado; Los métodos de pago y las facturas comparten el portal Stripe del servidor.
Revisar los cambios del plan antes de aplicarlos.
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.
El pago tiene una ruta de recuperación visible
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).
Reanudar o cancelar pagos pendientes
Pagos pendientes enumera la oferta guardada de cada servidor y abre su pago original. La cancelación confirmada por el proveedor le permite elegir otro plan o eliminar un servidor no utilizado y no pagado. Las instalaciones conectadas y en la nube comparten el flujo de recuperación, y al cambiar de cuenta se descartan los detalles de pago y las respuestas de la cuenta anterior (#1067).
Vista previa de niveles PAYG prepagos
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).
Seguridad de la cuenta y GitHub
Claves de acceso y autenticador 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).
La protección de la cuenta se mantiene constante durante las fallas
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 el acceso al repositorio es independiente del inicio de sesión
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).
Los tokens personales funcionan en todo el flujo del repositorio
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.
Soporte e incorporación
Una bandeja de entrada de soporte en la nube privada
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).
Las páginas de soporte y contacto aceptan solicitudes duraderas
Submissions are saved before email delivery, with a receipt and notification to
[email protected]. Los reintentos de entrega sobreviven a los reinicios de la API y las respuestas de soporte aparecen en la bandeja de entrada y se envían por correo electrónico al cliente. Los envíos reintentados reutilizan su recibo original en lugar de crear otro ticket (#970).Pantallas de cuenta y de primera ejecución más claras
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.
Aplicaciones y migración
Las aplicaciones tienen su propio lugar
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.
Un asistente de implementación más consistente
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.
La instalación de la aplicación explica las opciones de enrutamiento y recursos
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).
Importe Docker aplicaciones a servidores en la nube administrados
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.
Revisar importaciones como tarjetas o topología
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.
Builds, deployments and recovery
Detener cancela el constructor seleccionado
Cancellation reaches the worker's actual Docker or Bare runtime, including remote Git and archive preparation. The UI shows Parando… hasta que finalice la limpieza, luego permite la redistribución. La cancelación de una compilación conserva los contenedores implementados que heredaron las etiquetas de compilación; la propiedad ambigua del servicio aún bloquea la activación (#1059).
La salida de la compilación permanece legible
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).
Los servicios de redacción sin cambios siguen ejecutándose
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).
Las copias de seguridad previas a la implementación finalizan antes de la activación
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).
Las compilaciones remotas y las versiones estáticas utilizan las rutas correctas
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
.dockerignorelas negaciones se respetan (#1010, #1041).Los controles de estado y el apagado respetan el tiempo de ejecución
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).
Detección de Farm.js
Identify Farm.js applications and supply the framework's build and output defaults (#1037).
Dominios, networking y monitorización
Los dominios gratuitos siguen el servidor administrado seleccionado
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).
Conecta Cloudflare desde la configuración del dominio
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 comodín y recuperación de Edge más confiables
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).
Las actualizaciones de origen permanecen visibles hasta que se completa la implementación
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).
Correcciones de conexión y configuración.
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).
Correcciones de SDK, CLI y plataforma
Más administración a través de Ship SDK y 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.
Ediciones de entorno y orientación de comandos más seguras
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.
Flujos de trabajo de MCP Cloud más claros
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).
Correcciones de correo web y panel de control
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).
Inicio de API y validación de acciones masivas
Capacity previews pass the startup permission scan, and malformed bulk container requests are rejected instead of being interpreted as an empty request (#1033, #994).
Análisis opcional de productos en la nube
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.
Notas de actualización y transferencia de datos
Exportaciones completas y portátiles
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.
Las importaciones conservan el alcance y los datos seleccionados
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; Los campos de archivo no admitidos se rechazan antes de cambiar los datos.Actualice la nube antes que los clientes conectados
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.
Mantenga estable la configuración de seguridad de la cuenta
Self-hosted passkeys require HTTPS and a stable dashboard hostname through
OPENSHIP_PUBLIC_URL(localhost es compatible para el desarrollo). Conservar y realizar copias de seguridadBETTER_AUTH_SECRET, que protege los secretos del autenticador y los códigos de recuperación.