Skip to main content

How Wigoh Connect works

Your WordPress site ──(snapshot)──▶ Wigoh preview ──(you edit)──▶ Release proposed
        ▲                                                             │
        └──(approve in WP admin, apply, health check, 7-day rollback)─┘

Identity​

On activation the plugin creates a key pair unique to your site. The private key stays on your server, encrypted with your site's own secret keys. Wigoh stores only the public key. Every request the plugin makes to Wigoh is signed with the site key.

Snapshot and import​

The plugin exports your database and files into a snapshot and uploads it to Wigoh's private storage. Wigoh imports it into a preview. The preview is a full copy; your live site is never edited directly.

Editing​

The imported site opens in the same editor as any other Wigoh project. Everything in The editor applies. The Deploy button is replaced by Publish to my site, because a connected site goes back to your own WordPress rather than to Wigoh hosting.

Releases​

A release packages the edited copy, is signed by Wigoh, and is proposed to your site. The plugin polls Wigoh, receives the proposal, computes the drift report, and waits for a WordPress administrator to approve. Only then does it download, verify, stage and swap. A health check follows; failure rolls back automatically.

Two-sided approval​

You start a release in Wigoh. An administrator approves it in WordPress. Both are needed.