Claron
    Documentation
    BACKEND EVIDENCEReviewed

    Backend Evidence

    Backend evidence connects a browser request to the server activity captured for that exact request. Enable it for the project before starting a new review, then unlock it on an authorized device.

    Before you start

    Project-owner setup and a recovery password. Keep the downloaded recovery files.

    What you get

    The captured server context for a report's request, unlocked on an authorized device.

    Inspect a request's backend evidence

    INTERACTIVE EXAMPLE

    Select the request and unlock the sample diagnostic view.

    StorefrontInspect a request's backend evidence
    Sandbox

    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.

    Try the controls · sample data · changes stay in this example

    Choose the setup for your server

    ApplicationSetup
    Supported SSR application built and hosted by ClaronEnable project backend evidence and rebuild the SSR app. The build registers that application's SSR server for capture.
    Separate API or backend serverKeep it on your own infrastructure. Use the optional backend SDK and its collector. Claron does not host separate backend servers.
    Static-only siteThere is no application server to capture. Connect a separate API you own if that is the server evidence you need.

    Enable the project and save recovery access

    1. As the project owner, open the project → Settings → Backend.

    2. Choose a recovery password of at least 16 characters, confirm it, and prepare the recovery files.

    3. Download both files: the diagnostic backup and the administrator backup

      Save them with the recovery password in a secure location. The administrator backup controls project setup; share only the diagnostic access intended for an authorized teammate.

    4. Confirm that both files and the password are saved, then finish setup

      Enable Remember access on this trusted device only on your own trusted computer.

    5. Make a new supported hosted SSR build, or enroll the separate backend

      Confirm that the Backend settings show evidence enabled and the expected service registered.

    Capture and inspect one request

    1. Start a new review session after setup

      Perform the action that sends the request to the registered server, then create an annotation.

    2. Open the annotation's Network evidence and select the request that failed or behaved unexpectedly.

    3. Open its backend evidence

      If the device is locked, import the appropriate diagnostic recovery file and enter its original password. Your project role and diagnostic permission must also allow access.

    4. Read the captured request context, errors, and operations

      Use the correlation reference to confirm that the evidence belongs to this request and service, rather than assuming a nearby server event is the cause.

    Missing, locked, or incomplete evidence

    What you seeWhat to check
    LockedUnlock the authorized device with the project's recovery file and original password. A project role alone does not replace recovery access.
    No correlated requestConfirm the service and environment are registered, the new server build is running, and capture was enabled before the request.
    IncompleteInspect the recorded completeness state. A timeout, unsupported operation, or interrupted capture may leave partial context; it is not proof that nothing happened on the server.
    Old report has no evidenceStart a new review and reproduce the request. Requests that were never captured cannot be recovered by enabling the feature later.

    Recovery and access changes

    On a new owner device, use Restore in Backend settings with the administrator backup and the original recovery password. Losing the files or password can prevent recovery; Claron cannot reconstruct a missing recovery password.

    Manage diagnostic access separately from project invitations. Removing SDK startup configuration stops that service's future capture; it does not by itself revoke an existing teammate or trusted-device grant.

    MCP returns backend correlation references and availability only. It does not return backend plaintext, ciphertext, or recovery keys.