Fintech landing page
A marketing site with a booking flow and a strict Content-Security-Policy. Try the "break it" button to see a CSP violation get captured.
These are real apps running the real OnCatch widget. File a report on any of them, then watch it land in the live triage feed with the console + network context auto-captured. It is a sandbox: your reports here never reach a real customer, and everything auto-clears after 24 hours.
A marketing site with a booking flow and a strict Content-Security-Policy. Try the "break it" button to see a CSP violation get captured.
A live WebGL scene (react-three-fiber). OnCatch screenshots the actual 3D frame — not the black rectangle most widgets capture. "Break it" to fire WebGL faults the widget catches.
A Next.js app — virtualized 10k-row table, Stripe-style checkout iframe, streaming AI panel. OnCatch captures it cleanly under cross-origin iframes, large DOM, and mid-stream DOM churn. "Break it" to plant a defect.
A Vite + React app with a service worker + IndexedDB + a canvas chart. OnCatch captures the canvas at fidelity and survives the service-worker layer that breaks naive widgets. "Break it" to go offline, serve stale cache, or hit a quota error.
The same view a QA team sees: reports streaming in with console-error and network-error counts, refreshing live.
SaaS dashboards, e-commerce checkouts, and mobile web flows are on the way — each one a real host app for the real widget.