launch week Respira for WordPress is live on DevHunt until Monday. Live on DevHunt this week. See the launch

About Respira

Respira lets AI work on live WordPress sites, safely.

It connects Claude, ChatGPT, Cursor and other AI clients to WordPress through 312 tools across 17 page builders. Every change gets a restore point, published pages change on a copy you approve, and your content travels straight between your AI and your site.

Respira is independent. There are no investors: it is paid for by the people who use it.

A thin aluminium console with a small screen and an emerald key

Why Respira exists

It started with one job. The investor pages of a Divi site needed new pages and more than 40 PDFs uploaded and linked, on a deadline, with no room for a mistake. By hand that was days. An AI could do it in minutes, but one wrong move on a live site costs far more than the time it saves.

What was missing was the safe part: a way for an AI to work in the site’s own page builder, on a copy first, with a restore point before every change and a person approving anything that goes live. Respira is that part.

The name is Romanian for breathe: room to move fast without holding your breath.

Your data

What passes through Respira, and what protects it.

Respira works on live client sites, so this is the question it hears most. Here is the plain answer.

Two aluminium devices joined directly by a green cable, with a small padlocked box off to the side on a thin grey wire, outside the cable's path
Your AI talks to your WordPress site directly. respira.press sits to the side: it holds your account and receives usage records, not your pages.

Goes straight between your AI and your site

  • Your pages, posts and page builder layouts
  • The prompts you type and everything the AI writes back

On a direct connection, Respira’s servers never see your content.

What respira.press keeps

Account
Your email address, plan and licence.
Sites
Each site address, its Respira version and the page builders it uses.
Usage
Which tool ran, on which site, how long it took and whether it worked. Never the content, the instructions or the results. Set RESPIRA_USAGE_OPT_OUT=1 to switch it off.
Payments
Handled by Polar. Card details never reach respira.press.

Only when you choose them

These three send content through respira.press, because they cannot work without it:

  • Respira AER, the hosted workspace in your dashboard, processes the content each run needs and keeps your threads until you delete them.
  • Respira Exhale, the HTML to WordPress converter, reads the HTML file you give it on its way to your site.
  • The rendered design check loads a page that is already published, to take screenshots.

What protects your site

  • A restore point before every content change, and one-step rollback.
  • The AI edits a copy first. You approve before it goes live.
  • Deletes, plugin installs and bulk changes wait for your approval.
  • Scoped keys, encrypted at rest: a key only does what you grant it.
  • Settings that could lock you out are refused to every agent.
  • Every action is written to a sealed log on your own site.
The full safety model

What protects respira.press

  • Data stored in the EU (Ireland), encrypted in transit and at rest.
  • Row-level security on every table: each account can read only its own rows.
  • Daily backups, kept for 7 days.
  • Errors traced in Sentry’s EU region, with personal data scrubbed.
  • A breach would be reported to every affected account within 72 hours.
Infrastructure and sub-processors

How Respira is built

Every change
runs automated checks before it can ship: a test suite for the MCP server, static analysis and a regression suite for the WordPress plugin on more than one PHP version.
Every release
is refused by the build if any development tool would end up inside the plugin you install.
Every report
is taken seriously. When a researcher reported a weakness in September 2026, it led to four audits: sign-in, database, API and plugin. The fixes are live.

Found a security problem? Email word@respira.press with Security in the subject. The privacy policy covers the rest.

Who builds Respira

Mihai Dragomirescu, founder of Respira

Mihai Dragomirescu

Founder

I have spent 22 years building products across EdTech, marketing tech and community platforms. I am not a coder by training: I build Respira with AI coding agents, which is exactly why every change passes the checks above before it ships.

I answer every support message myself.

A note of appreciation

Every purchase, every bug report and every honest review shapes what Respira becomes.

  • If you bought a licence: thank you. You are making this sustainable.
  • If you reported a bug: thank you. You made it better for everyone.
  • If you shared your experience: thank you. It helps the next person decide.

Mihai