Questions, answered.

On the Sites page, click Install YOLO and download the plugin. In WordPress, upload it under Plugins → Add New Plugin and activate it. Then open YOLO → Cloud in WordPress and click Connect to YOLO Cloud. You come back here, pick a workspace, click Approve & connect, and the site appears in your list.

There are no keys to copy and paste. If the site already runs YOLO, skip straight to the connect step.

Sites on Cloudflare normally connect in one click. If Bot Fight Mode, an “Under Attack” challenge or a firewall turns our servers away, connect through the Agent instead: the site calls out to YOLO Cloud for work with a pairing code, so nothing has to be opened up to the internet.

The free YOLO plugin lets the AI you choose (ChatGPT, Claude or any agent that speaks MCP or a REST API) build and manage one site safely, with undo, auto-rollback, backups on the site’s own server and emergency recovery.

YOLO Cloud runs all your sites from one place and adds what needs a service: off-site backups, kits and sharing between sites, the community Library, uptime, security and error monitoring, auto-fix, before/after screenshots on updates, client reports, teams and the AI Bridge. Creating and importing kits and share links needs the site connected to Cloud.

YOLO Cloud is free to start, and every feature on this site, including off-site backups and the AI Bridge, is available to every account today. The YOLO plugin is free.

Your account and site data, and your off-site backups, are stored on servers we run in Germany (Hetzner, Falkenstein). Update screenshots and uploaded images are kept in Cloudflare R2.

AI features send what they need to the AI provider: see the next question. The privacy policy has the full list of the services we use.

Read the privacy policy →

Anthropic’s Claude models power the AI Bridge, Ask your fleet, error explanations, auto-fix proposals, the Library’s safety scan, and YOLO CMS’s safety checks and visual reviews. Your messages, any images you attach and the site details the AI reads are sent to Anthropic to produce a reply.

When an extension is published to the Library, its text is sent to OpenAI to build the search index, and the words you type into Library search are sent to OpenAI to match against it. Documentation look-ups go to Context7.

YOLO CMS is for websites without WordPress. Connect the AI app you already use, such as ChatGPT, tell it about your business, and it builds the website with you inside your YOLO Cloud account. Nothing goes public until you say yes.

See how YOLO CMS works →

Yes. Run WordPress, plugin, theme and translation updates on one site or many in a single job, and see the result for every site. Plugin and theme updates are health-checked by the plugin and rolled back automatically if they would take the site down; WordPress core updates are health-checked and reported.

Update jobs take a screenshot of the site’s home page before and after, then show how much changed. A run with no visual change says so; one that changed shows you both pictures side by side. The pictures are kept for 90 days.

Off-site backups go to our object storage in Germany, not the server the site runs on. Full backups are encrypted on your site with your account’s own key before they’re uploaded, so the stored file is unreadable without that key, which we keep encrypted and decrypt only to restore a backup for you.

You can also choose incremental backups, which upload only what changed and keep a long history cheaply. You set the schedule (daily or weekly, at a time you choose) and how many restore points to keep, up to 60. Incremental backups are not encrypted (stored as-is, partly compressed), in the same EU storage.

Pick a restore point and click Restore. The plugin takes a safety backup first. Restoring needs the connection to allow writing code and installing plugins. You can also copy a backup onto another connected site, such as staging to live, with addresses rewritten for the new domain.

Yes. When a new YOLO release is out, each directly connected site shows it and updates from here in one click, one site or all of them. The package is checked to be a valid plugin before the old copy is replaced. Agent-connected sites update from their own wp-admin. Very old versions of YOLO need one manual update before this works.

Downtime and response times, plugins and themes with known vulnerabilities (checked daily, with a one-click update when a fix exists), PageSpeed scores and Core Web Vitals, and new PHP fatal errors, which the AI explains in plain words. Opt in to emails for downtime, updates and fix proposals, plus a weekly digest.

No. Auto-fix is off until you switch it on for a site. When it finds a fatal error or a vulnerability, it proposes the safest fix it can, such as an update or a small patch, and an owner or admin has to approve it. Cloud then applies it through the plugin’s usual safety checks and confirms it worked.

The error watch, which is on for every account, only reports. It records each new fatal error, explains it and suggests a fix, such as updating the plugin that caused it. It never updates or switches off a plugin by itself.

You chat with it to manage a site. It reads the site, makes changes through the YOLO plugin, checks the result and tells you what it did. Because it works through YOLO, its content, design and settings changes are snapshotted and can be undone, updates are health-checked, and the connection’s permissions still apply.

Questions across every site you run at once, like “which sites still need a WordPress update?” or “which run PHP 7.4?”. It only reads, unless your workspace allows it to make changes.

Yes. Copy an extension or kit from one site to many, or import one from a share link and push it out to the sites you choose. Kits, share links and importing need the sites connected to YOLO Cloud.

Every published extension is scanned by AI for malicious or dangerous code and badged before anyone can install it. Installing it needs the connection to allow writing code, which you choose when you approve the connection (it starts ticked). If you grant neither writing code nor installing plugins, Cloud can’t turn them on; only someone signed in to wp-admin can.

A Library entry isn’t just one file. Anyone can improve an extension and submit their version back as a variant under the same entry, credited to them. When you add it to your sites, you pick which variant to install.

An extension you added from someone else’s entry goes back to the Library only as a Re-Mix of that entry, never as a new entry. No new entry can take another creator’s extension name, and an identical copy of their code, even with comments or spacing changed, is refused. So every entry and its credit stay with the person who made it.

No. Sites that use the extension are told a new version is available, and you choose when, or whether, to apply it.

Yes, when the extension declares them. Cloud shows the settings as a form; set them once, preview the change for each site and apply it everywhere. Secrets are encrypted and never shown back, and sites that drift from your settings are flagged.

Yes. Group sites under a client, then share a white-label report link with your branding and the client’s, for one site or all of that client’s sites. It covers uptime, security, performance and the updates you’ve applied, and prints to PDF.

Yes. Invite people as owner, admin, member or viewer. Viewers can see everything but change nothing. You can belong to several teams and your own personal workspace, and switch between them without signing out.

Yes, with magic login: from a site’s console, Cloud asks the site for a single-use login link that expires within minutes. Nobody shares admin passwords, and every use is written to the site’s audit log. It needs plugin installs allowed for the connection, and works for sites connected directly, not through the Agent. On YOLO 0.85.0 and later it also needs installs switched on in the site’s YOLO settings, so switching installs off there turns magic login off too.

Sign in with GitHub, Google, or email and password. Turn on app-based two-factor in your profile and you get one-time recovery codes; once it’s on, it’s required at every sign-in, including through GitHub and Google.

Every action runs through the YOLO plugin’s safety net: snapshots and undo for content, design and settings changes, auto-rollback when an update or activation would take the site down, and a tamper-evident audit log. When you approve a site’s connection you choose what Cloud may do. Everything is ticked to start with: untick writing code and installing plugins if you don’t want them. If you don’t grant them, Cloud can’t turn them on; only someone signed in to wp-admin can. If you do, treat that as full control of the site: installing plugins also lets Cloud open wp-admin as an administrator (magic login). We still recommend keeping independent backups, such as your host’s.

How we keep it safe →

Use break-glass recovery from the site’s console. It puts a fully downed site into safe mode, even when wp-admin and the normal API are gone, so you can then restore a good backup. It needs the site’s emergency recovery key, set up in wp-admin and saved in Cloud beforehand.

Site access keys are encrypted (AES-256-GCM, with a separate key for each record) before they reach our database, and are never shown back to you. Disconnect the site here to delete its stored key, or revoke the key in the plugin. Either way, access stops at once.