Trust & data
Your clients’ sites, handled with care.
What Verploy needs from your WordPress sites, what it stores, and how you stay in control.
The connector
One small plugin. No passwords.
Verploy connects to each site through a lightweight connector plugin. It doesn’t need SSH or special hosting features.
- You install the Verploy Connector plugin on each site and pair it with a one-time code from your dashboard.
- Verploy never asks for WordPress passwords, FTP or SSH access.
- Every request between Verploy and your site is signed.
- The connector reports technical health data and only carries out signed requests from Verploy.
Your data
Only the technical data needed to maintain your sites.
Verploy stores what it needs to update, check and report. Nothing more.
What Verploy stores
- Plugin, theme and WordPress core versions
- Health data: PHP version, SSL certificate, domain expiry, memory, disk space and uptime
- Update runs, check results and timelines
- Screenshots from checks, in private storage
- Your account and team details
What Verploy doesn’t need
- WordPress passwords, FTP or SSH credentials
- Visitor data or site content for the AI diagnosis: it only sees error messages, failed checks and version information
- Email from the test copy: it never sends any
The test copy
Tested where your site actually runs.
Updates are tested on a private copy before they reach the live site. This is how that copy behaves.
On your own server
The test copy is built on the same server as the live site, with the same PHP version and limits. Not on ours.
Invisible
Visitors and search engines never see the test copy.
Silent
The test copy never sends email, so your clients’ customers get nothing by accident.
Temporary
The copy exists for the update run. Your server needs enough free disk space for it.
You stay in control
Nothing risky happens without a policy you chose.
You decide how much Verploy does on its own. You can change it at any time.
- By default, Verploy asks before it resolves a vulnerability.
- Automatic fixes only when you enable them, and only for high and critical vulnerabilities with a safe fix.
- Invite colleagues as owner, admin or member.
- Every update run has a timeline with before, after and difference screenshots.
Leaving is easy
You can always stop.
No contracts that trap you, no hidden dependencies.
Disconnect a site at any time. Deactivate or remove the Verploy Connector plugin and Verploy can no longer reach that site.
See for yourself whether Verploy is up. Current status and incident history: status.verploy.com.
For the legal details, see our privacy policy.
How we build and release
AI helps us build. People decide what goes live.
We use AI to develop faster. We do not let it decide what reaches your clients’ sites.
A developer reviews every change. Is it safe? Is it correct? Does it make Verploy better? Nothing is merged on an AI’s say-so.
Our own client sites go first. Verploy is built by an agency that runs it on the WordPress sites it maintains for its own clients. Every change runs there before it is offered to you.
One release a month. New features are collected in a monthly release and announced only after they have proven themselves. Fixes ship in between, with the same review. See the release notes.
When something still slips through, it is on status.verploy.com and in the release notes, not hidden.
Spend less time checking WordPress.
Let Verploy do the maintenance work.
3 months free, up to 40 sites. No credit card.