Follow the request. Into your server.
Claron matches each request in the session to what your server did with that exact request.
Open a report's network evidence, pick the request that failed and see the server side of it: the functions it called, the branches it took, the error it threw. Your own collector encrypts it; it is decrypted only on your device.
From the network tab to the server
Backend evidence connects a browser request to the server activity captured for that exact request. Start a review, reproduce the action, report it, then open the request's backend evidence from the report.
Where it works
Choose the setup that matches where your server runs.
- Server-rendered apps Claron builds and hosts: tested Node configurations of Next.js, Nuxt, SvelteKit, Remix / React Router, Astro and Angular.
- An API or backend you host yourself: connect it with the experimental backend SDK and its collector. It stays on your infrastructure.
- Backend SDK setup is documented for Node, Python, Java, .NET, Go, PHP, Ruby, Rust and Elixir.
Encrypted with your own recovery keys
The project owner sets a recovery password and keeps the downloaded recovery files. Evidence is unlocked on authorized devices, and diagnostic access is managed separately from project invitations.
Honest about gaps
Evidence exists only for requests captured after setup. A report can show it as locked, missing or incomplete, and an incomplete capture is not proof that nothing happened on the server.
Try it in the product's own interface
Inspect a request's backend evidence
INTERACTIVE EXAMPLESelect the request and unlock the sample diagnostic view.
Network evidence
Checkout total differs from the expected amount
- Environment
- Staging
- Release
- checkout-v2
- Service
- checkout-api
Select the captured request to inspect its exact server context.
Backend evidence
Availability and access are separate checks.
Evidence locked on this device
A permitted role still needs diagnostic recovery or trusted-device access.
Questions about backend debugging
Straight answers, including the limits.
Set it up
More of Claron
- Visual bug reportingReport a bug by clicking the page. Claron attaches a screenshot, console logs, network requests, element and source context to the report.
- Session replayReplay the visit behind a Claron bug report with clicks, console and network in sync. Inspect the captured DOM, export the recording, share it safely.
- Live website reviewsReview a website together: invite clients as guests, guide everyone to the same page and collect visual bug reports with their evidence attached.
- Review rounds and sign-offCollect sign-off on a specific build: invite reviewers to selected pages, record each approval or change request, then verify fixes on the fixed version.
- AI fixes, CLI and MCPClaron reads a bug report's evidence, explains the cause and proposes a diff. Apply it with the CLI, open a pull request, or hand it to your agent via MCP.
Weighing up other tools?
See how Claron compares with Marker.io, BugHerd and Sentry across the whole workflow.