security
What is checked, and where we stand
No tool can promise a site never gets hacked. This one makes sure you know early and have a way to act.
Dutch company. EU customers' site data stays in the EU.
Compared with the WordPress release.
Plugin versions matched against a public feed, daily (Standard).
Checked from outside, with alerts.
who can act
Monitoring runs alone. Changes need a key.
Every action is in the site's log.
One plugin, or one SSH key for the site's own user, never root. Revocable at any time.
MCP clients connect with OAuth. Destructive actions need a confirmation token.
Single sign-on, two-factor and roles per organisation.
Health results, findings and versions per site. Never sold, never used to train a model. Privacy policy
Over SSH we help clean it, with a restore point before each step. We never promise it stays clean.
certification
We are working towards ISO 27001
We are building the management system and will have it audited. Until a certificate is issued we do not call ourselves certified. Tender or questionnaire? Write to security@webcrew.ai.
Scope and risks.
Access, changes, incidents, suppliers.
Tested by someone who did not build it.
By an accredited body.
WebCrew watches from outside; it does not host or shield the site. Found something? security@webcrew.ai. A person reads it the same day.