7 ago2026v0.6.1CaracterísticasCorreccionesBreaking52 actualizacionesCopiar enlace
Redes de servicio a servicio
Ahora cualquier proyecto se puede conectar a otro a través de la red interna.
Every project (a plain single-app, a raw Compose stack, a monorepo, or an imported one) now shows a Connection card with its internal address (
http://<alias>:<port>) y se puede elegir como fuente "Usar en un proyecto". Anteriormente, solo se podía acceder internamente a las aplicaciones de catálogo con un bloque de conexión declarado o pilas de redacción multiservicio; un proyecto de aplicación única no tenía ninguna dirección interna. La accesibilidad al mismo límite es automática y el cruce de un límite permanece explícito: un alias solo se vuelve accesible una vez que se vincula a un consumidor a la red. Solo autohospedado y omitido para sitios estáticos (sin puerto de escucha) y aplicaciones alojadas en la nube (que en su lugar se vinculan a través de Público).Dar a un servicio un nombre de host interno personalizado
A service can carry a custom east-west DNS alias that resolves alongside its default name, set from the service's Settings tab and available to single-app, Compose, and monorepo services alike. Openship normalizes it to a valid hostname and rejects one that collides with another service on the same project network, and the internal-address card shows the alias its containers actually answer to. Self-hosted only.
Un editor de configuración de servicio más claro
The service Settings tab groups fields into labelled sections and swaps free-text boxes for structured editors: ports and volumes are entered as chips (with per-item limits enforced as you type) and depends-on is a picker of the project's other services. The image and build-from-source fields are shown together — fill either, and a build context wins over a stale image — instead of an image/build mode toggle.
Estado e incidentes de los contenedores
OpenShip vigila tus contenedores las 24 horas del día, no solo durante la implementación
Until now a container was health-checked exactly once, during the ~15s window right after a deploy, and then never looked at again unless a human was staring at the project page. A new health watch polls every server's Docker daemon once a minute (and reacts within about 10 seconds when Docker itself reports a container dying or restarting), so an app that falls over or drops into a crash loop at 3am raises an alert through your existing notification channels instead of waiting for a user to complain. Self-hosted only.
Los contenedores rotos te avisan una vez, no cada minuto
A container stuck in a restart loop is broken on every poll, so a naive watcher would fire 60 alerts an hour about one fault. Instead each fault becomes a single incident: one message when it opens, one more only if it gets strictly worse (unhealthy → crash looping → down), and one all-clear that tells you how long it was down. A fault must be observed twice before it notifies, and an in-flight deploy, an operator's own
docker stop, o un proyecto deshabilitado nunca activa una falsa alarma.Un servidor inaccesible es una alerta, no una por aplicación
When a box's Docker daemon stops answering, Openship opens a single server-level incident that names how many projects it can no longer monitor, and freezes those projects' health rather than falsely marking them recovered. The record is durable, so a box that has been down for days does not re-page every time the control plane restarts.
Una pestaña de Salud en cada proyecto, con 30 días de historial de incidentes
Each project gets a Health tab listing its currently open incidents plus a rolling 30-day history of resolved ones with downtime durations. It also states whether monitoring is actually switched on (an operator toggle in the Jobs module) and surfaces the server's own outage when a box is unreachable, so an empty tab is never misread as "all good." Self-hosted only.
Análisis y uso de recursos
Vea de dónde vienen sus visitantes
The Monitoring tab draws a per-country choropleth of visitors alongside a ranked list, and animates real-time request ripples fed by the same stream the Logs tab tails, so you can watch where requests are landing right now. It works the same way self-hosted and on Cloud, and it can tell "no visitors yet" apart from "geo lookups aren't set up on this box," which used to render identically as an empty map. On a multi-domain project the whole view scopes to a chosen domain.
Los recuentos de visitantes ahora son números reales, no recuentos de solicitudes
The dashboard's visitor figure was a request count relabelled "unique IPs," so five page views from one browser counted as five people. It's now a genuine count of distinct visitors, deduplicated at the edge with a per-day salted hash that never stores an address or a per-visitor row — the number is honest while still collecting no behavioural data on your end users.
Rutas principales y códigos de respuesta que tienen datos reales detrás
The Top Paths table was hardcoded empty and error rate couldn't be answered from anything saved. Both are real now: the daily rollup records normalized request paths (query strings stripped, ids collapsed, so tokens never become keys) and the full status-code mix, and a new card expands each 2xx/3xx/4xx/5xx class to the exact codes beneath it. On self-hosted, per-path aggregation is opt-in per project (a toggle, default off, including on existing projects) because it adds measurable work to every request the edge handles; on Cloud paths are aggregated automatically. Every other analytics dimension is unchanged.
Se conserva el historial de uso, para que pueda ver qué provocó un fallo
CPU, memory and network usage used to exist only as a live stream that vanished when you closed the tab, so "was memory climbing before it got OOM-killed at 3am" had no answer. Usage is now sampled on a schedule into 5-minute buckets and charted over time, per service. A Compose project reports its whole stack with a per-service breakdown and an All/service scope picker instead of just the one container the primary service owned; a static site (nothing to measure) now says so plainly instead of showing four zeroed metrics. Self-hosted Docker deployments; bare non-Docker deployments report zero network, since per-process accounting isn't available there.
Busy domains keep their analytics
A domain pushing more than about 2 GB in a single minute (roughly 286 Mbps — routine for video or large downloads) used to overflow a 32-bit byte counter and kill the analytics scrape for that entire domain, so the busiest sites were precisely the ones with no analytics. The bandwidth counters are now 64-bit and collection keeps up. Self-hosted edge.
Los análisis ya no desaparecen silenciosamente cuando nadie está mirando
Traffic analytics live in the edge's memory under a TTL and were only flushed to the database when someone opened a project's Analytics tab, so a project nobody viewed for a day lost its per-minute data. A background scrape job now persists every server's analytics on a schedule whether or not anyone is watching, collecting a whole server in one pass instead of a separate memory scan per domain.
La información sobre herramientas de gráficos se puede leer en todos los temas.
Tooltips were effectively transparent in the dark themes (plot lines showed straight through the text) and on light cards the hover marker rendered as a stray white block below the tooltip. Both are fixed with a shared tooltip style reused across the monitoring and billing charts.
Proxy perimetral y inverso
Ajuste el proxy inverso por proyecto
A project's Routing settings now expose a full set of proxy tunables instead of a handful: raise or entirely remove the upload size limit, set connect/read/send/keepalive timeouts, control response buffering and gzip level, turn on HTTP/2, tighten request-header limits, and verify TLS to the upstream — each value validated before it reaches the generated nginx config and labelled with its own directive name. On self-hosted it also reads back what the edge is actually serving next to what you saved, flags any drift in colour, and offers a one-click adopt, so a hand-edited vhost or a value the sanitizer dropped can't quietly disagree with your settings. Self-hosted only.
Los análisis por país y las reglas nacionales funcionan en el borde de los contenedores
The containerized edge shipped without the MaxMind geo library or its country database, so every lookup returned nothing: no per-country analytics were recorded, and country-based route rules failed closed (a single-country ban silently blocked all traffic). The library and a GeoLite2 database — parsed and validated before shipping — are now baked into the edge image, so geo works from a box's first install with no runtime download.
Corregir la identidad del visitante detrás de Cloudflare o un balanceador de carga
Behind a proxy the edge treated the proxy as the client, which broke four things at once: visitor country resolved to the PoP, distinct-visitor counts collapsed, per-IP rate limits put the whole planet in one bucket, and IP bans banned a PoP instead of a visitor. The edge now recovers the real client address from
CF-Connecting-IP, confiando solo en los rangos publicados de Cloudflare como par de conexión.Las reglas por ruta llegan al borde incluso cuando no está en el loopback de la API
Pushing a project's route rules to a local edge now goes through the same resolved edge-management path as the rest of Openship instead of assuming the edge lives on the API host's own loopback. On setups where it doesn't — such as the containerized edge — rate-limit, ban, and country rules now actually take effect.
La píldora "Edge ready" coincide con el estado real del servidor
Edge readiness is now read from whether Openship's edge container is actually running, the same fact the Infrastructure tab and System Health use. Before, a leftover bare-host OpenResty install could make the pill claim "ready" while the server tab reported the edge as down.
Dominios personalizados y gratuitos
Gratis
.opsh.ioLos dominios solo se dirigen a un servidor cuyo control usted ha demostrado.Openship Cloud's shared edge now forwards a free subdomain to your server only after that server answers a challenge proving it owns the target, a proof that lasts 90 days and that Cloud re-checks about a week before it lapses. Openship prepares the box to answer the moment you set up its edge, so a free domain added later works without a redeploy, and a background sweep re-asserts, reads back over the server's own public address, and re-verifies anything expired — so a box left undeployed for months no longer silently loses its free URLs. A slug can't be pointed at someone else's box, and a server that can't yet answer is told why. Requires Openship Cloud.
Los dominios gratuitos y personalizados ahora funcionan en sitios estáticos
Adding a free
.opsh.iodominio a un proyecto estático utilizado para registrar nada en el borde, por lo que la URL pasó al comodín sin origen detrás; La edición del dominio de un proyecto estático no escribió ningún vhost hasta la próxima implementación. Ambos ahora emiten una ruta real en el instante en que guarda, entregando los archivos creados del proyecto, el mismo comportamiento que ya tenían las aplicaciones proxy.Un certificado que se emitió pero luego tuvo un problema ya no se pierde
If an ACME order completed but a later step failed (the vhost rewrite, the reload, or the read-back), the domain stayed stuck in "provisioning" with no expiry recorded, which made it invisible to the renewal sweep — a valid certificate then sat on the edge and expired ~90 days later. Openship now re-reads the edge after a failed issuance and records a certificate that's actually present, so renewal stays scheduled.
Los dominios personalizados no válidos se rechazan en la puerta
Setting a custom domain to something that isn't a public hostname (
localhost, una IP simple, una etiqueta única o un valor con una ruta/puerto/esquema) utilizado para devolver el éxito, generar una fila de dominio pendiente inactivo e incluso escribir unserver_name localhost;vhost en el borde compartido. Las rutas de escritura ahora validan los nombres de host personalizados y rechazan los incorrectos, al tiempo que permiten que un proyecto que ya tiene un valor incorrecto lo edite y lo elimine.Editar un dominio gratuito ya no muestra un falso "Acción requerida"
A single edit could sync the same free subdomain to Cloud twice, and the two racing challenges reset each other's token, so the route worked but the project reported "Action Required" anyway. Callers that run their own managed-edge sync now suppress the duplicate, so each edit issues one challenge and the status reflects reality.
Los redireccionamientos y los límites de carga entran en vigor al guardar
Raising a route's upload limit or adjusting its timeouts now applies as soon as you save instead of waiting for the next redeploy, and a domain redirect is applied live to static-site domains too, not only to proxied apps.
Correo electrónico
El correo se ejecuta como un motor autónomo en lugar de hacerse cargo de su servidor
Setting up mail no longer installs iRedMail's daemons directly onto the host or reboots the box. Postfix, Dovecot, spam and virus filtering, and DKIM now run inside a single
openship-mailcontenedor con su base de datos vmail en un sidecar Postgres, conectado en red al host, por lo que el correo aún ve las IP de los clientes reales y el borde permanece fuera de la ruta de datos del correo. La configuración se reduce a ocho pasos cuyos únicos requisitos previos son Docker y openship edge, y cada parte del estado del correo (cola, maildirs, claves DKIM, configuración) reside en montajes de enlace del host, por lo que la actualización es una extracción y recreación que conserva sus datos. Solo autohospedado.Mail usa el mismo borde y TLS que todo lo demás
Mail setup no longer stands up its own host OpenResty and certbot on the side. The certificate for
mail.<domain>se emite a través del borde abierto compartido, la misma ruta que toma el TLS de todos los demás dominios, y ahora se registra para renovación como cualquier otro dominio: un certificado de correo en un borde contenedorizado (sin temporizador de certbot de host) solía caducar ~90 días después de la instalación, de forma silenciosa; una renovación fallida ahora genera una notificación.Los servidores de correo configurados antes de la contenedorización siguen funcionando
The move to containers is topology-aware, so a server whose mail was installed the old way (system daemons, database on the host) still reports accurate component health and stays fully manageable: SQL queries, outbound SES/SMTP relay config, and daemon restarts all target the right engine. When the engine genuinely is stopped or was never installed, admin actions now return a clear message telling you to restart it or re-run setup instead of a bare 500 leaking a Docker "No such container" error.
Infraestructura remota
Vea cada borde administrado y contenedor de correo en un solo lugar
A new Infrastructure view lists each server's edge and mail container with the image version it's running against the version this release pins (for example edge 0.4.0 → 0.5.0), and flags which are behind, stopped, or missing. An attention rollup surfaces the ones that genuinely need hands — an edge that's down, or absent on a box that hosts projects — separately from the ones that merely have an update available. Self-hosted only.
Actualizar, reparar o instalar un contenedor sin tocar un caparazón
Update swaps a behind container onto the pinned image (rollback-guarded), Fix restarts a stopped one in place, and a server with no edge gets a one-click Install that runs the first- install path with 80/443 takeover consent. Each apply streams its pull/recreate/ verify progress and survives a dropped connection, and a fleet-wide Update all / Restart stopped does the same across every server at once. Self-hosted only.
Actualice automáticamente su infraestructura remota al actualizar
A new instance-wide toggle lets the control plane update every remote edge and mail container automatically when you upgrade Openship (its
APP_VERSIONavanza), por lo que la infraestructura de su flota rastrea la versión que está ejecutando sin barrido manual. Está del lado del servidor, por lo que también funciona en el escritorio, a diferencia de la actualización automática de la aplicación de escritorio, y está desactivado de forma predeterminada. Solo autohospedado.La detección de deriva se mantiene actualizada por sí sola
With auto-scan on (the default), opening the Infrastructure tab or the home page quietly runs one detect-only scan when the cached state is stale, throttled to about every 30 minutes per browser, so the attention dot reflects reality without pressing Scan. It only refreshes what's shown — it never applies an update, which stays the separate auto-update toggle. Self-hosted only.
Las cajas heredadas ya no se marcan como rotas
A server converted to the containerized edge kept listing its leftover host OpenResty as a component with an Update button for a config nothing loads; those superseded host modules are now dropped from the view. And a legacy host-native mail engine (systemd Postfix/Dovecot) that was quietly delivering mail used to show up as "Stopped, container missing" — it's now labelled as not containerized rather than inventing a version. Self-hosted only.
Docker migración
Los sitios migrados mantienen el límite de carga y los tiempos de espera bajo los cuales se ejecutaron
When you move or take over a Docker stack, the reverse-proxy tunables the source vhost declared (upload size limit, upstream read timeouts) are now carried onto the migrated project before the new edge vhost is rendered. Previously the site silently reverted to nginx's 1 MB / 60 s defaults at cutover, so the first large upload after a move failed with a 413 and nothing tied it back to the migration. Adoption is additive: a limit you set by hand always outranks a value inferred from the old box. Self-hosted only.
La adopción de una pila ya no vuelve a publicar los puertos internos
A compose service that published a container port on a random host port (a single-part
ports:entrada, p.e. el 5432 de una base de datos (la fuente nunca estuvo realmente expuesta) ahora no se expone durante la adopción en lugar de volver a publicarse en el destino, por lo que una migración no expone innecesariamente los servicios internos ni choca con lo que ya tiene un puerto de host. El puerto todavía se muestra en el asistente para que pueda enrutarlo y el tráfico de servicio a servicio sigue resolviendo por nombre a través de la red compartida. Solo autohospedado.El asistente le indica qué variables de entorno no se transfirieron
When adopting a foreign stack, environment variables that exactly match the image's baked-in defaults are dropped rather than imported as explicit config (the image still supplies them at runtime). The wizard now lists exactly which keys were skipped and why — common with Coolify/Nixpacks images that bake config as ENV layers — so you know what to re-enter if you later change the image.
No más nombres de host fantasmas en el asistente de importación
The wizard used to invent a hostname from the project name whenever a step had no route chosen, labelling port fields, previewing monorepo sub-app hosts, and even wiring the "Visit Site" button to a host that would never exist. It now shows only hosts your config actually names, and hides "Visit Site" entirely when the deployment has no public domain.
Registro de auditoría
Vea exactamente lo que cambió su asistente de IA
Every audit entry now records where the action came in from (the dashboard, an MCP client, the CLI, the API, a webhook, or the system itself), and you can filter the log down to a single source. Isolating MCP-driven activity finally answers "what did the AI assistant do," which was impossible before because an MCP write and a CLI write produced identical rows. Entries written before this release show as an honest "unknown" rather than being mislabelled.
Desactive la auditoría y controle cuánto tiempo se conserva
Each organization can switch audit recording on or off and pick a retention window (7, 30, 90, 180 or 365 days). Turning recording off stops new entries but never touches the ones already written, and the act of disabling is itself logged first, so the trail always explains why it went quiet. The switch is per-organization, so on a shared cloud instance one tenant can't disable everyone's audit log.
Una verdadera barra de filtro sobre el registro.
You can narrow by category, actor, date range and free-text search, with a live count on every category tab. Search resolves project, server and domain names, so typing a name like "api-gateway" turns up entries that only ever stored an opaque id, and rows now display the human name of the affected resource, resolved server-side in one batched lookup per page.
La paginación del registro ya no salta ni repite filas
Entries that share a timestamp are now ordered by a stable tiebreaker, so scrolling through pages no longer reshuffles them; two entries created in the same instant could previously appear twice or vanish between pages.
Notificaciones
Enviar alertas a Telegram
Telegram joins email, Slack, Discord, and Teams as a notification channel: point a BotFather bot at a chat, group, or forum topic and Openship delivers your deploy, health, and job alerts there. The bot token is stored encrypted, and the channel list shows which bot does the sending.
La configuración de notificaciones autohospedada elimina los botones que nunca pueden activarse
On a self-hosted box the billing notification categories are fed by the SaaS billing system, so they were switches that could never send anything. They no longer appear, and the remaining categories are organized into tabbed groups in Settings.
Instalar y empaquetar
OpenShip ahora se instala y actualiza en Node, nunca en un Bun global
El
curl | shy los instaladores de PowerShell descargan una carga útil CLI autónoma y verificada por sha256 que se ejecuta en Node: usan su sistema Node 22+ si tiene uno y, de lo contrario, venden un Node 22 oficial de nodejs.org en~/.openship, y te migran silenciosamente desde cualquier instalación anterior de Bun global sin tocar tu propio Bun.openship updatetoma el mismo camino: volver a descargar la carga útil verificada, actualizar el tiempo de ejecución primero, para que una actualización que eleve el piso del nodo se recupere a sí misma en lugar de romperse. Esto retira la clase de bloqueo Bun-vs-ssh2 que podría eliminar operaciones SSH remotas.El servidor de correo se envía como imagen oficial.
Openship's official multi-arch (amd64 + arm64) image set, built and published to GHCR and Docker Hub each release, now includes
openship-mailjunto con la API, el panel y las imágenes de borde, por lo que ya no es necesario crear un motor de correo autohospedado desde el origen.openship upahora funciona bajo Docker sin raíz en lugar de fallar crípticamenteBringing up the compose stack on a rootless daemon used to abort the install with Docker's opaque "error while creating mount source path … permission denied," because a rootless daemon can't create the edge's bind-mount directories under root-owned paths. The CLI now creates those directories itself and, when it can't, prints the exact one-time
sudo mkdir/chowncomandos para ejecutar (#372).
Implementaciones y redacción
Una implementación en funcionamiento nunca se registra como fallida
Build output that carried a raw NUL byte or a broken Unicode character (as a failed
docker exechace cuando derrama su flujo multiplexado, encabezados de marco y todo) hizo que la escritura del registro fallara y OpenShip leyó mal esa escritura rechazada porque la implementación en sí falló: una implementación en vivo y en ejecución fue marcada como fallida y sus contenedores derribados, mientras que la vista de implementación permaneció bloqueada en "Implementación". Los registros de compilación almacenados ahora se desinfectan y tienen un tamaño limitado, la escritura del resultado elimina cualquier registro o blob de error Postgres que se rechace en lugar de perder el estado, y el evento terminal que cierra la transmisión en vivo siempre se activa.Su URL de acceso y sus puertos de dominio personalizados sobreviven a una nueva implementación
A project's deploy target is now stored durably on the project itself (a new
server_idcolumna) en lugar de vivir solo en los metadatos volátiles de la última implementación. Antes, una instantánea nueva o parcial podía perder ese enlace, hacer una regresión silenciosa del proyecto a una implementación local, eliminar los puertos de sus dominios personalizados (un 502) y restablecer la URL de acceso alocalhost:3000; Los proyectos existentes alojados en el servidor se reponen para que esto no pueda afectarlos en la próxima redistribución. Un dominio personalizado verificado también se conserva en lugar de eliminarse o borrarse incluso cuando el conjunto de puntos finales de una implementación lo omite. Solo autohospedado.Una instalación de dominio gratuito ahora tiene un objetivo de implementación
A box set up with a free
.opsh.ioEl dominio podría finalizar la incorporación sin servidores en la lista y sin nada en qué implementar, porque el registro de la fila local "Este servidor" colgaba de un paso de arranque que esa ruta nunca se ejecuta. El cuadro ahora materializa su propia fila de destino de implementación cuando los servidores aparecen por primera vez, cuando se conecta a OpenShip Cloud y al restablecer el administrador. Adjuntando un gratis.opsh.ioEl dominio a un proyecto más tarde ya no necesita una nueva implementación primero, ya que cada implementación ahora prepara la casilla para responder a la verificación de propiedad. Solo autohospedado.Los dominios de servicio respetan su límite de carga y configuración de proxy
A compose service's own domain ignored the project's reverse-proxy tuning, so the main app would accept a 50 MB upload while the same project's service domain rejected it at nginx's 1 MB default with a 413. Those settings now apply to every domain a project writes — per-service, static, single-domain composites, path fan-out, and single-app native deploys. Self-hosted only.
Las URL del servicio de aplicaciones de catálogo se resuelven por puerto y nunca están en blanco
Apps that route one container port to a domain and leave another port-only (Convex, for one) used to get an empty or self-referential origin injected (
CONVEX_SITE_ORIGIN="", o un127.0.0.1que dentro de un contenedor apunta al propio contenedor). Cada puerto ahora se resuelve de forma independiente, un servicio de solo puerto vuelve al alcance real de la caja.http://host:port, y un{{publicUrl:…}}El token que aún no se puede resolver se deja sin configurar, por lo que se aplica el valor predeterminado de la imagen, con una advertencia fuerte en el registro de implementación en lugar de un espacio en blanco silencioso.La advertencia de enrutamiento le indica cuándo el borde es el problema
When a deploy succeeds but its domains aren't being served, the post-deploy warning now checks why: if the edge container itself is down it tells you to bring the edge back up, instead of sending you off to your DNS provider to debug routes that are actually fine. Self-hosted only.
Nota de actualización: esta versión supera las versiones de imagen de correo y de borde fijado. En el modo autohospedado, abra la nueva vista Infraestructura para actualizar el borde de cada servidor y el contenedor de correo en la imagen fijada, o active la actualización automática en toda la instancia para que el plano de control lo haga en cada actualización.