We can tell you which repairs actually hold. Every fix FixiWeb performs is recorded — what broke, what caused it, what we tried, what worked, and whether the defect came back. That record is the Repair Graph.
"This site has 17 problems."
"This site runs a stack we have seen fail before, in a way we have already repaired on other sites — and we can show you the repair held."
Every certified capability below has been driven end to end against a real site in FixiWeb Labs. Each proof is anchored to a commit and a content hash, so the claim can be audited rather than taken on trust.
Each bar below is one link in the proof chain: detects · certified repair path · named channel · independent read-back · public truth verified · rollback proven · stack supported.
A detector tells you a site is already broken. This tells you an upgrade will break it, and in what order to do it safely. These entries are publicly documented breaking changes with citations — our own fleet observations are reserved for customers and partners.
Data governance is not an appendix to this product — it is the product. Insurers, banks, hosts and enterprises can use this data precisely because the boundary below is enforced in code, not promised in a policy document.
Two mechanisms carry that boundary. k-anonymity: no figure is published unless at least five distinct sites stand behind it, and when we suppress something we say so rather than quietly rounding it away. De-identification: repair outcomes, the records behind the published rates, are keyed by a keyed hash of the domain rather than the domain itself, and nothing we publish names a site. Per-site risk profiles do store the domain; they are served only under the access rules for that site and are never published.
A scan takes under a minute and tells you which of your issues we can already prove we repair.
Scan your site