Features / Bring-your-own WordPress staging

Link the staging site you already host.

Keep production and staging related in the workspace. Use that relationship for supported safe-update and high-risk change workflows without moving your hosting.

In practice

How you use it

01

Connect both installations

Add your production site and a separate staging installation. A copy that points at the same installation is not a safe execution target.

02

Link the pair

Associate staging with its production site in the same workspace. A linked pair counts as one billable site; a standalone staging site does not get that exemption.

03

Choose the policy

Set the site's execution policy and use workflows that honor the linked target. Review what actually ran on staging before making a production decision.

Inside the workspace

Keep the work in view.

An actual screen from the IrmaWP demo workspace. The workspace includes sample history; available actions depend on your plan, role and site connection.

Bring-your-own WordPress staging

Keep production and staging related in the workspace. Use that relationship for supported safe-update and high-risk change workflows without moving your hosting.

IrmaWP bring-your-own wordpress staging workspace context
Demo workspace · Dark mode
Before you connect

What to know

Does IrmaWP provision or clone staging?
For sites hosted elsewhere, bring your own staging installation and link it to production in IrmaWP. For managed hosting, contact our team to confirm the staging and restore workflow for your site before testing a change.
Does a staging link make every change safe?
No. Staging must be isolated and representative. Database state, integrations and unsupported workflows still need human judgment.

Start with your own sites.

Connect a small portfolio, check the tools you need, and choose the plan that fits your team's work.