Proof of work, published with its limits on the page

The demonstration case file

We built a test website on infrastructure we own, ran it through the same process a customer job follows, and kept every artifact: the full backup (taken and verified, with its checksum recorded), the outside scan records before and after, the working notes, and the proof pack document that ties them together. The point of the exercise was to prove the process end to end: backup discipline, evidence capture, and the exact format of the record a customer receives.

What the demo honestly shows, and what it does not

It shows the process works: the backup is real and restorable, the scans are genuine records of a real site, and the verification format is the one your job will use. It does not show a completed patch on a customer site, because no customer job has run yet, and the demo environment itself could not execute the final runtime step, so its conclusion is recorded as more information required, in the same words a customer record would use. That restraint is the product: conclusions here are stated exactly as strongly as the evidence supports, in writing, every time.

As paid jobs complete, their case files replace this demonstration, published only with the customer's written permission and in their exact approved words. If you are weighing whether to trust a new service with your website, weigh this page: a service that publishes the limits of its own proof is telling you how it will treat yours.

The record every job produces