01
Copy
The update isn't installed on your live system but on a copy of your shop or website. There, the Crew works only with anonymised data.
Works with any system
Risk-free updatesCopy, automated tests, your approval and a backup before every deployment.
For Shopware, Shopify, WooCommerce, Magento, WordPress and TYPO3 · Last updated: October 2026
In brief
Risk-free updates means: every system, plugin or extension update is first installed on a copy of your shop or website (a staging environment) and tested automatically there. It only goes live once you approve it. Before every deployment, the AI Crew backs up the current state, so the previous version can be restored at any time. The principle applies to Shopware, Shopify, WooCommerce, Magento, WordPress and TYPO3.
✓ Copy
✓ Tests
✓ Approval
✓ Backup
The problem
Why updates are risky for shops and websites
Install updates directly on the live system and you risk downtime. Put them off and you risk security vulnerabilities.
- [WARN]After an update, the checkout or the contact form suddenly stops working.
- [CONF]A plugin or extension isn't compatible with the new version.
- [RISK]Updates get postponed, and known security vulnerabilities remain open.
> Solution: test on the copy first, then approve, then go live with a backup.
Process
Risk-free updates in four steps
Copy, automated tests, your approval and a backup before every deployment: every update passes through these four safety stages.
02
Automated tests
The Crew automatically checks that everything still works after the update, from individual pages to forms and checkout.
03
Your approval
You see the result on the copy and decide. No update goes live without your approval.
04
Backup before every deployment
Before the approved update goes live, the Crew backs up the current state. That way the previous version can be restored at any time.
Comparison
Update directly on the live site or risk-free update?
| Question | Update directly on live | Risk-free update |
|---|---|---|
| Where is the update installed? | Directly on the live system | On a copy |
| Who spots errors first? | Your customers | The automated tests |
| Who decides when it goes live? | Nobody, it's already live | You, by approving it |
| What happens if there's a problem? | Troubleshooting while the site is running | Backup of the previous state |
| When does it go live? | Immediately, often at inconvenient times | Scheduled, by default on Tuesdays and Thursdays |
Release schedule
When do updates go live?
Mon
Tue
Wed
Thu
Fri
Sat
Sun
By default, approved updates are deployed automatically on Tuesdays and Thursdays, with a backup before every deployment. Happy to discuss daily releases when you get started.
Works with any system
Risk-free updates for every system
The principle stays the same; only the components differ from system to system.
- ShopwareShopware core, plugin and theme updatesAI Crew for Shopware →
- ShopifyTheme and app customisations on a theme copy. Shopify updates the system itself.AI Crew for Shopify →
- WooCommerceWordPress, WooCommerce and plugin updatesAI Crew for WooCommerce →
- Magento & Adobe CommerceUpdates, security patches and extension updatesAI Crew for Magento →
- WordPressCore, plugin and theme updatesAI Crew for WordPress →
- TYPO3Core, extension and security updatesAI Crew for TYPO3 →
FAQ
FAQs on risk-free updates
What does “risk-free updates” mean?
Every update is first installed on a copy of your shop or website and tested automatically. It only goes live after your approval, and the current state is backed up before every deployment.
What is the copy used for testing?
A separate test environment, often called staging, that mirrors your live system. There, the AI Crew works only with anonymised data. Your live system stays untouched while the work is done.
Which updates are installed this way?
System, plugin and extension updates, as well as security updates. Exactly which components are involved depends on your system, for example plugins in Shopware and WordPress or extensions in TYPO3 and Magento.
What happens if an automated test fails?
Then the update doesn't go live. The Crew fixes the problem on the copy, and you only receive a working version for approval.
When do approved updates go live?
By default on Tuesdays and Thursdays. Happy to discuss daily releases when you get started.
What happens if an error does appear after go-live?
Before every deployment, the Crew backs up your current state. That means the previous version can be restored (rollback) while the error is fixed on the copy.
Do I have to check every update myself?
You decide on the approval. How closely you review the result on the copy is up to you. The automated tests run in every case.
Which systems does this apply to?
Shopware, Shopify, WooCommerce, Magento and Adobe Commerce, WordPress and TYPO3. With Shopify, Shopify updates the system itself, so here the principle applies to your theme and your customisations.
Never fear the next update again
In the demo, we show you on your own system how an update is tested on the copy, approved and taken live with a backup.
Book a demo
