November 8, 2026
Automatic app updates for Docker images
Images now have the option Update apps automatically after every build. When it is on, every successful build of the image (a push to GitHub, an upload or a manual rebuild) restarts on the new version the apps of that image that are running. Stopped apps stay stopped, and an app that fails to update does not stop the others: the failure shows up in the activity log. See Custom Docker images.- Default: an image created from GitHub starts with the option on; all others start with it off. Change it on the image page.
- Deploys tab: an app that runs from an image now shows which image the deploy comes from and whether automatic updates are on. The GitHub link belongs to the image, not to the app.
- Same rules as any deploy: zero-downtime deploys and automatic rollback apply when your plan includes them.
Clearer warning about WORKDIR /app
At runtime /app is the app’s persistent disk, mounted over the image, so what the image puts there is hidden. The check now warns about WORKDIR /app only in the final stage of the Dockerfile (a build stage of a multi-stage build no longer triggers it), and the warnings of every build, including those started by a push to GitHub, are kept on the image. The panel shows a banner on the image page and a warning on the Deploys tab of the apps that use the image, and asks you to confirm before creating an app from it. To fix it, use another directory (such as WORKDIR /srv) and build again. See Custom Docker images.warnings(list of{ code, line }) is returned byGET /v1/images/:image_idand by the image list.
API and MCP
auto_update_apps(boolean) is returned byGET /v1/images/:image_idand accepted byPATCH /v1/images/:image_id.- The MCP
update_imagetool acceptsauto_update_apps.
Language of the site and of emails
- Site: on your first visit, the site opens in Portuguese when you access it from Brazil or another Portuguese-speaking country, and in Spanish from a Spanish-speaking country, even when the browser is set to another language. Elsewhere, the browser language still decides. A language you pick in the language selector always wins and is remembered.
- Account and emails: a new account now keeps the language of the page where it was created, so the sign-in email and every later email arrive in that language. Existing accounts that never chose a language are updated on the next sign-in. You can always change it in your account settings.
Snapshots of any size can be downloaded
Downloading a snapshot no longer has a size limit.GET /v1/users/:id/snapshots/:snapshot_id/download now returns the ZIP for any existing snapshot, in a single response.Very large projects show a clear message
Downloading a project that has more than 300 MB of files directly as a ZIP now returnsDOWNLOAD_TOO_LARGE (HTTP 413) and the panel asks you to download a snapshot instead, which has no size limit. See Download Application.Snapshot before deleting is now optional
Deleting an application or a database no longer creates a snapshot automatically. The delete dialog in the panel now has the option Create snapshot before deleting, off by default (shown on plans with manual backups). When it is on, the panel creates the snapshot and deletes only if it succeeds; when it is off, the resource is deleted right away.- API:
DELETE /v1/apps/:idandDELETE /v1/databases/:iddelete right away. To keep a backup, create a snapshot first. - Unchanged: deleting a whole stack or a custom Docker image (which deletes its apps) still takes a safety snapshot first. When the platform removes projects on its own (an expired plan or an account without a plan), the backup is still required: if it fails, the project is stopped and kept, not deleted. See Back up and restore with snapshots.
Snapshot size limit
A snapshot can have at most 4 GB (the size of the snapshot file, already compressed). Above that, creating it is refused withSNAPSHOT_TOO_LARGE (HTTP 413) instead of a generic error. The limit applies to manual, daily and safety snapshots. Downloading has no such limit: any existing snapshot can be downloaded. See Back up and restore with snapshots.New daily limits for manual backups
Manual backups now have two daily limits: up to 5 per project (application or database) and, across all your projects, 2 per GB of plan RAM per account, at least 5 and at most 64: 5 on Starter 1 and 2, 8, 12 and 16 on Pro 4, 6 and 8, 24, 32 and 48 on Business 12, 16 and 24, and 64 on every Enterprise size. The day is counted in Brasília time, the 5-minute interval between manual backups of the same project still applies, and the automatic daily backup does not count. See Plans and limits.Adjusted traffic protection limits
We adjusted the limits of Vertra Shield and of the request rate limit per visitor IP so that legitimate traffic is interrupted less often.- Vertra Shield: applications that make many outgoing requests, such as bots and integrations that call external APIs, are paused less often. A first occurrence no longer pauses the application right away. Higher plans keep proportionally higher limits.
- Request rate limit per visitor IP: the limit for applications on
*.vertraweb.appand on custom domains was adjusted. If your application legitimately receives high-volume traffic from a single IP, such as a server-to-server integration, contact support. See Platform protections.