Autopilot
It does the work. You decide where it should ask first.
Monitoring, checks, updates and the changes you ask for run on their own, each with a restore point taken first and one line in the log. Undo is one click. For the things you want to see before they happen, a client's shop, anything that touches prices, you set a rule per site and WebCrew asks you first there.
Free for one site. No card. Every action is logged and can be undone.
What runs on its own
The routine is handled. You read a log, not a to-do list.
Watching and checking
Uptime around the clock, versions, core files, administrator accounts, known vulnerabilities, certificates. Always on, never a question for you.
Updates on your schedule
Plugins, themes and WordPress itself update when you set them to, with a restore point first. When the check afterwards fails, the update rolls back by itself and you get one line about it.
Changes you ask for
"Change the opening hours everywhere." The assistant does it, shows you what changed, and keeps a restore point. Undo is one click, for 30 days. Coming soon
Security findings
A changed core file is flagged with the exact difference. An unknown administrator is flagged the hour it appears. A plugin with a known hole gets its fix on the next run.
One log line per action
What ran, on which site, when, and what it changed. The log is the same for your own actions, the assistant's and the schedule's.
Undo, always
Every action takes a restore point of exactly what it touches. Undo puts back only that, in one click, for as long as the restore point is kept.
Where it asks first
You draw the line, per site
Some things you want to see before they happen. Set a rule and WebCrew asks you first there, and only there. Everything else keeps running.
- Prices and orders. On a shop, anything that changes a price or touches WooCommerce settings can ask first.
- A client's site, as a whole. For a client who wants to be asked, every change on their site waits for them or for you.
- Big updates. Major versions of WordPress or of the page builder can ask first, while small updates keep running on the schedule.
- Anything irreversible. Deleting content or users always asks. There is no restore point for something that is gone.
Questions
Questions about autopilot
What if an update breaks the site while I sleep?
Every update takes a restore point first and the site is checked right after. If the check fails, the update rolls back on its own and you read one line about it in the morning. Checking the checkout, login and contact form after every update is Coming soon.
Can I have it ask me for everything?
Yes. Set the rule for a site to ask first for all changes, and nothing happens there until you or the client say yes. Most people start there for one client and loosen it once they have read the log for a month.
Who can say yes?
Per site: you, your team, or a client user who can only say yes or no to changes on their own site. Client users are Coming soon.
What about changes from Claude or ChatGPT?
The same rules apply. Your tool asks WebCrew to make the change; WebCrew makes it, logs it and keeps the restore point, or asks first where your rule says so.
How long is a restore point kept?
Thirty days, so a change you only notice next week can still be undone. Deleting content or users has no restore point, which is why it always asks.
Let it run. Read the log in the morning.
Connect a site free and see what it does for you in the first week.