Zero Downtime Deployment
Build Magento releases separately, switch prepared files and inspect deployment history and rollback actions.
Check it fits your store
Questions about compatibility? Contact us.
Details
Magento zero downtime deployment becomes practical with Zero Downtime Deployment, a digital extension for Magento 2 that builds each release separately and then switches the prepared files into place.
Magento zero downtime deployment workflow
The module prepares releases with Composer, dependency injection compilation and static deployment. Once the release is prepared, it switches the prepared files. Build work stays separate from the live switch, so your team can review each step before the release goes live.
Release visibility and control
- Admin history of deployments
- Deployment logs
- Webhook automation
- Rollback tools that support the release workflow
What to plan before you deploy
Database upgrades still need compatible change and rollback planning. Run preflight database changes and deployment rollback steps on the destination installation before you switch files.
Requirements
- Magento 2.4.9 package line
- PHP and runtime requirements, listed in the included guide
- CLI filesystem ownership and release directory permissions
- Git and Composer when used
- A writable application tree for the in-place release switch
Adobe Commerce on cloud infrastructure
Adobe Commerce on cloud infrastructure must use its supported build and deploy hooks and platform workflow. This package does not replace that pipeline.
What you get
Choose the edition that matches your installation: Community, Enterprise or Magento Cloud. The digital download includes Zero Downtime Deployment Version 1.5.2 and the included guide. This product is listed in the Magento 2 Extensions category under SKU TI-EXT-ZERO-DOWNTIME.
Change Log
Version 1.8.0 – October 29, 2026
New
- Command techimprovement:zdd:cleanup (zdd:cleanup) and the button Clean Up Build Files on the deployments page: delete the previous builds of releases up to the latest successful deployment and the build instance now, for example what earlier versions left behind. --all includes every release. Does nothing while a deployment runs.
Improved
- Build copies are kept only while a deployment can still break the store. The build a deployment replaces (generated/, pub/static/frontend, pub/static/adminhtml, var/view_preprocessed) stays in the release for the switch, the health check and auto-revert. Once the health check has passed (or was skipped), it is deleted, and the backups of the code files the deployment replaced or deleted are packed, with the previous app/etc/config.php, into the release's rollback.zip. Older releases that still hold a previous build are stripped the same way. Malware scanners report scripts in var/, and copies of payment JavaScript in previous builds matched card skimmer signatures; no loose copies of scripts stay behind now. New setting Previous Build After a Deployment: "Remove once the deployment is verified" (default) or "Keep for instant rollback" (the previous behavior). A deployment that failed after its switch while auto-revert is off keeps its previous build until a newer deployment is verified.
- The build instance is deleted when a deployment ends, so the full copy of the store's code is not left in var/. The next deployment copies the store again. New setting Keep Build Instance Between Deployments (default No) keeps it for faster, incremental copies.
- Rollback rebuilds when the previous build was removed. The store is copied into the instance, the deployments are undone there newest first from their rollback.zip (replaced and deleted files restored, added files removed, the previous config.php back), and the code is built, staged and switched in like a deployment, with health check and auto-revert and without database steps. In git mode the live HEAD moves back to the commit before the oldest rolled back deployment. A rebuild that fails before its switch leaves the store and the releases as they were. Releases that hold their previous build are still switched back in milliseconds.
Requirements
- The PHP zip extension (ext-zip, also required by Magento).
Earlier versions (4)
Version 1.7.0 – October 29, 2026
New
- JavaScript bundling with Magepack. With Bundle JavaScript with Magepack on (new group JavaScript Bundling (Magepack) in the settings), full and static content deployments run magepack bundle in the build instance after static content and the "after build" hooks, for every storefront theme a store view uses (themes based on Hyvä are skipped) or the selected themes. Every bundle and its RequireJS configuration must exist and pass node --check before the switch; the bundles go live with pub/static/frontend in the same rename. When bundling fails, the partly written bundles are removed and the release goes live without them, or the deployment stops (When Bundling Fails). Preflight checks node and magepack first.
- Bundle configuration (magepack.config.js): generated from the live storefront with magepack generate (when there is none yet, before every deployment, or only on request), uploaded, or read from a file in the code. The CMS, category and product page are found on the storefront (home page, first main menu category, a product of it that can be added to the cart without choosing options) unless entered. Stored configurations are read as data and written back as plain JSON, never run; module paths that leave the theme folder are refused. The previous configuration is kept and can be restored.
- Store setting follows the live bundles. Every cache refresh after a switch, revert or rollback sets "Enable JavaScript Bundling with Magepack" (dev/js/enable_magepack_js_bundling) per store view: on where the theme and locale have bundles, off elsewhere, with one default value when all store views agree. A value locked in app/etc/env.php or config.php is reported. Turn Magepack On and Off in the Store, default Yes.
- Storefront check after the switch. The CMS, category and product page open in the headless browser; a bundle file that does not load, a JavaScript error or a requested RequireJS module that never gets defined is a problem. Problems are compared with the same pages without bundles: only those the bundles cause turn Magepack off for the release (its bundles are removed and the store setting follows). Errors the pages have anyway are remembered, so later deployments skip the comparison. Without a browser, the bundle files the home page references are requested over HTTP.
- Admin page System > Tools > JavaScript Bundling (Magepack) (ACL "JavaScript Bundling (Magepack)"): setup check with the fix for each line (Node.js, npm/yarn, magepack, puppeteer and its browser, Magento module and settings, themes, configuration, storefront pages, live bundles per store view), Generate Configuration Now, upload, download and restore of the configuration, Set Store Setting From Live Bundles, task log.
- Command techimprovement:zdd:magepack (--check, --generate, --import, --export, --restore-previous, --sync-store).
- Server setup guide MAGEPACK.md: Node.js with NodeSource or nvm, npm and yarn installs of magepack 2.11.2, puppeteer (which npm skips silently when its Chromium download fails), system Chrome/Chromium or puppeteer's Chromium with its libraries, the Magento module, every setting, and troubleshooting.
Improved
- Commands that receive a password as an argument show it as *** in the deployment log and error messages.
- The deployment that installs 1.7.0 still runs the steps of the version it replaces; bundles are built from the next deployment on.
Version 1.6.0 – October 26, 2026
New
- First commit of a new site. Connect & Set Up on a store that is not a git checkout yet pushes the store's code to the branch: as the first commit of an empty repository or a new branch, or on top of a branch that has no store (only a README, for example). A store that is a git checkout already pushes its commit. A branch with a store is never overwritten. Never committed: app/etc/env.php and its copies, auth.json, .env, .ssh/, var/, generated/, pub/media/, pub/static/ (their .htaccess files are committed), node_modules/, database dumps, the excluded paths, and vendor/ when composer.lock exists, whatever the store's .gitignore says; a store without .gitignore gets one. Files over 95 MB stop the push with their names.
- Deployments stop when the branch is not ready, like the Adobe Commerce Cloud build (bin/magento module:config:status): before building, app/etc/config.php of the branch must list exactly the modules of the code; after building, the build must not have changed or removed a repository file. The deployment fails before anything goes live and its log lists each file with the reason (module list, a file composer install copies from magento/magento2-base, a committed vendor/ that does not match composer.lock, a build hook) and the command to run on your computer. A config.php with the same modules in another order and JSON files with the same data do not count. Setting When the Branch Is Not Ready (Stores > Configuration > Zero Downtime Deployment > Git; default: stop) and -f deploy anyway.
Improved
- Test Connection reports a branch that does not exist yet as a warning: Connect & Set Up creates it.
- The Git Connection page and the guides describe the first commit; the token needs write access to the repository's contents for it (read-only is enough afterwards).
Version 1.5.3 – October 24, 2026
New
- Customer user guide USER-GUIDE.md (installation with Composer, configuration, usage, troubleshooting).
Improved
- The shadow database example in the admin comment and README is shop_zdd.
- Unit tests build query and JSON result doubles instead of constructing Magento framework classes without arguments, so the suite runs against the real framework.
Version 1.5.2 – October 22, 2026
Fixed
- "Notification could not be sent: Class "Hyva\Theme\ViewModel\SvgIcons" not found" after a deployment that removed Hyvä. The deployment process still runs the code it started with, so rendering the email after the switch needed classes of modules that were gone. Notifications are now sent by bin/magento techimprovement:zdd:notify , a new process with the code that is live; in-process sending is the fallback.
- app/etc/config.php was reported as "changed by the deployment, different in the branch" when setup:upgrade had only sorted the module list. When the modules and their values are the same as in the branch, the log now says that nothing has to be done.
Reviews
Be the first to review Zero Downtime Deployment
Reviews are written by customers with an account. Sign in to tell others how it works on your store.

