Curious, and careful

Try AI on your WordPress site without risking it.

You have read what AI can do and you have also read what it can break. Respira is the version where the live page is never the first thing it touches.

Copy first
the live page is not the experiment
90 days of rollback
so a mistake is a minute, not a weekend
7 days free, no card
try it on a staging site if you prefer
A soft clay door ajar with green light behind it and a key in the lock
What it looks like

Start with something you would not mind getting wrong

You type

Update the copyright year in the footer to 2026.

  1. 1Reads the footer and shows you what it found before changing anything
  2. 2Writes the change to a copy
  3. 3Gives you the preview and waits
What you get

Two minutes, and you have seen the whole loop: what it read, what it wrote, where it waited for you. Then you try something bigger.

Most people do three or four of these before they trust it with a real page. That is the intended order.

What stops people trying
  • "What if it edits the wrong page?"
  • "What if it deletes something and I do not notice for a week?"
  • "I do not know which AI tool to even start with"
  • "I cannot explain to a client why the site broke"
What changes the answer
  • Edits land on a duplicate, so the live page is never the draft
  • A snapshot before every write, restorable for 90 days
  • You approve in WordPress, where you can see what changed
  • Works with the AI you already use, so there is nothing new to learn
What you get

Everything on this page ships today.

Read before write

Ask it what is on a page first. Reading changes nothing and costs nothing to be wrong about.

The approval queue

Changes sit in WordPress until you say yes. Leaving them is a valid answer.

Site memory

Tell it once that the booking page is off limits, and the plugin refuses writes there, to any agent.

Snapshots

Every write records the state before it. Restore a page without needing a backup plugin.

Your own AI

Claude, ChatGPT, Gemini, Cursor. No new subscription, no new chat window to learn.

Start on staging

Point it at a staging site for the first week if that is what makes you comfortable.

After helping me change slugs and adding a new hero to multiple pages in one prompt in a couple of minutes, I have to say that editing my client's WordPress sites will never be the same.
Verified user
What keeps it safe

Every guard, written out rather than promised.

The honest answer to "what is the worst that can happen" is a page you delete. Here is the whole chain that makes that the worst case, including the parts that are not on by default.

  • Duplicate-before-edit as the default, not an option you find later
  • A snapshot before every write, 90 days of rollback
  • Rules the plugin enforces itself, whichever agent is asking
Read the safety model
A change held in Respira before it reaches the live page
Held
The checks Respira runs before a change goes live
Checked
Respira AER

The gentlest way in: a chat that is already connected.

If wiring up an MCP client is the part that puts you off, skip it. AER is a chat inside your Respira dashboard with your sites already attached and the same approval workflow underneath.

  • Nothing to install beyond the plugin
  • A plan you read before anything runs
  • The same duplicate-first writes and the same rollback
See Respira AER
The Respira AER interface showing two selected sites and a plan awaiting approval
Built out in full

Each of these has a page of its own.

What it costs

Maker is €9 a month, or €71 a year, for one site. The trial is 7 days and takes no card, so the first week costs nothing to abandon.

Straight answers

The questions people actually ask

What is the worst that can happen?

A duplicate page you do not like, which you delete. The live page is only touched after you approve, and even then the write is snapshotted and restorable for 90 days.

Do I have to install anything strange?

A WordPress plugin, and a connection to the AI you already use. Nothing about your hosting or your theme changes.

Can I stop it touching certain pages?

Yes. Site memory holds rules the plugin enforces itself, so a protected page refuses writes no matter which agent is asking.

What does it cost to find out?

Seven days, no card. If you do nothing at the end of it, nothing happens.

Not quite you?