Web support operating system
Udy is a working surface for the people responsible for dozens of client websites. It investigates a ticket against the live site, shows you what it actually found, and watches those sites for trouble in between.
Paste the ticket as it arrived. Udy finds the domain, runs read-only probes across DNS, HTTP, headers, certificates, WordPress and plugins, reads the page source, and opens the site in a real browser when it needs to. Where a fault only appears when someone does something — a form, a coupon, a checkout — it reproduces the action and captures what happens.
You get ranked causes, each labelled verified, likely, hypothesis or unknown, with a fix and a citation you can open.
Udy checks the sites on your roster on a schedule — reachability, the real page rather than an error or parked page, certificate and domain expiry. A failure has to confirm before it reaches you, and a request that simply didn't complete is checked again from a clean connection before anyone is disturbed.
When something is genuinely broken it opens an incident, runs the same diagnosis automatically, and messages you on Telegram with the likely cause already attached.
Udy gathers with ordinary, deterministic tools before any model is involved, and each result becomes a numbered piece of evidence. A finding can only be marked verified if it cites evidence that genuinely exists in that ledger — checked in code, not requested in a prompt.
When the cause isn't readable from outside the site, Udy is built to say unknown rather than name a plausible culprit. Probes are read-only, and it stops before anything irreversible.