The exact service
A fixed daily capture with human review.
The founding pilot turns Latchshot's guarded public-page renderer into a narrowly managed record. The owner agrees one UTC capture window with you, reviews the daily artifacts, retains the latest 30 days, and sends one concise weekly note about visible changes.
Daily capture
One 1440 × 900 PNG per confirmed page, once per day, at an owner-agreed UTC window.
Rolling archive
The latest 30 daily artifacts stay in the agreed private delivery location; older pilot artifacts roll off.
Weekly change note
A human-readable summary names visible changes or states that no meaningful visual change was found.
The pilot is best-effort. It has no uptime SLA, instant notification, pixel-diff threshold, compliance certification, or guaranteed capture time. A failed daily run is reviewed at the next owner check.
The deliverable
See the weekly note before requesting it.
The note separates visible observations from owner interpretation, names every expected artifact, and calls out missed captures. This compact example uses illustrative data; it is not customer work or a monitoring-result claim.
Public pricing page
Week ending
19 July 2026
- Capture coverage
- 7 of 7
- Pages reviewed
- 1
- Material changes
- 1
The hero message changed on July 17.
The sample heading changed from “Simple plans for growing teams” to “Plans that grow with your team.” Displayed prices, plan names, and the primary CTA appear unchanged.
Worth checking: update campaign or reporting copy if it still quotes the earlier heading.
Not claimed: why the change happened, whether it was intentional, or whether page behavior changed.
The fit test
Which pages fit the pilot?
Fits the pilot
- One to five exact public HTTP or HTTPS pages on port 80 or 443
- Release pages, public pricing, public records, portfolios, or client-approved sites
- A fixed viewport and one daily capture are sufficient
- You are allowed to request recurring captures of every page
Stops the pilot
- Login state, cookies, private pages, signed URLs, customer data, or query secrets
- Clicks, typing, scripts, selectors, scrolling, proxies, CAPTCHA, or bypass work
- Real-time alerts, legal surveillance, evidence certification, or an availability SLA
- Pages whose terms or your authority do not permit recurring capture
If one page crosses the boundary, it stays out of the schedule. The owner confirms every exact URL before payment or capture.
The sequence
How the pilot starts
- 1
Send one example public page
The intake stores one exact URL without credentials, query data, or a fragment, plus the page-count band and monitoring goal.
- 2
Owner confirms the complete scope
You and the owner agree the exact pages, daily UTC window, private delivery location, archive access, and what belongs in the weekly note.
- 3
Owner confirms payment and start
The owner handles payment separately. This page does not create a subscription, reserve capacity, charge a card, or begin monitoring.
- 4
Review the first week
The first written note is the acceptance check. If the fixed capture is not useful, the owner stops before a second month is agreed.
The fit request
Request a fit review with one example page
The owner can usually judge the boundary from one example URL, the number of pages, and the job you need the archive to do. This request is free and does not begin monitoring or payment.