Every site in one organization
Each WordPress site is its own connection in the same organization, and changes are allowed site by site. Ask about one site or all of them.
For people with several sites
See what is waiting on each site and ask ChatGPT or Claude to sort it out. You approve one plan, and Mitos runs it by itself, one site at a time, checking each site after every change.
Free to start · One approval for the whole plan · Stops at the first problem
What updates are waiting on my sites? Run them all, one site at a time.
wordpress_list_fleet_updates6 sites · 14 plugin updates · 1 WordPress updatewordpress_start_fleet_updateone plan of 15 updates, one site at a timewordpress_fleet_update_status6 of 6 sites · the home page loaded after every changeDone: 15 updates on 6 sites, each checked after every change. Updates cannot be undone, which is why a run stops at the first problem.
What you would do site by site, in one chat and one plan.
Each WordPress site is its own connection in the same organization, and changes are allowed site by site. Ask about one site or all of them.
Plugins, themes and WordPress, with the current and new version on each site. Pick all or only some sites and updates, and approve the plan once with a 6-digit code as an extra check that it's really you.
Clear caches, empty spam older than the days you choose, and check WordPress's files against WordPress.org's checksums, on every site. The file check starts at once, since it only reads.
Whatever the AI asks for on any site waits in the same list in Mitos. Open each one, see exactly what would change, and approve or reject it, in the chat where your AI assistant supports it, otherwise in Mitos.
Choose per site whether risky changes only warn about the last backup's age or are refused without a recent one. The backup comes from the plugin you already use, such as UpdraftPlus.
Every week Mitos checks each connected site and shows what is new and what was resolved since the last check. Owners and admins get an email when something starts failing.
Updates cannot be undone, so a run is careful from start to finish.
No. You approve one plan, once, with a 6-digit code as an extra check that it's really you. The approval covers only the sites, updates and versions you saw, so nothing different can start.
The run stops there and the remaining sites are left alone. Owners and admins get an email saying where and why. Mitos cannot undo an update, so you restore from your backup in wp-admin.
Yes. Pick sites, kinds (plugins, themes or WordPress) or exact updates. If you pick nothing, the plan includes everything waiting.
No. Once you approve, Mitos runs the plan by itself. Ask your AI assistant how it is going, or see it on the Mitos updates page.
It compares WordPress's files with WordPress.org's checksums and names any that changed or are missing, which can mean tampering or a broken update. It only reads, so it needs no approval.
Better not. For clients, create one organization per client so their data stays apart. One organization suits several sites of the same business.
Connect your first site, add the rest to the same organization and ask what is waiting. No card needed.