Demo report

A deploy report your team can read in under 2 minutes.

This sample shows the core product Callra sells: one Deploy Impact Report with a verdict, evidence, affected slices, suspect commits, and the next action to investigate.

Start checking deploysRead docs

Deploy Impact Report

deploy #184 - pricing-layout-refresh
Generated 30 minutes after the latest production deploy. Callra is comparing the live release group against the previous stable release and the immediate before/after window.
WatchingMedium confidence2 grouped deploys

Signup conversion

-18%

after deploy #184

Pricing LCP

+42%

mobile Safari

Checkout revenue

-11%

directional only

Affected slice

/pricing

highest visible impact

Verdict
The short answer the team needs right after shipping.

Watching: signup conversion dropped after this deploy, mainly on mobile Safari. Traffic is stable, speed is worse, and revenue is still directional.

Why this is not a rollback call yet: enough evidence exists to focus the investigation, but not enough to claim strong causality.
Evidence
The smallest set of proof a team needs before opening deeper tools.

Affected slices

Page /pricingRoute /pricingmobile Safarisignup flow visitors
Verdict: Watching: signup conversion dropped after this deploy, mainly on mobile Safari. Traffic is stable, speed is worse, and revenue is still directional.
Evidence: Pricing LCP worsened, the same route leads the affected slices, and the strongest commit trail points back to the pricing refresh and checkout loader changes.
Next action: Callra pushes the same investigation into dashboard, email, CLI, and MCP so the team can reopen one shared report instead of reconstructing context by hand.
Suspect commits
These are the first commits a founder or engineer should compare.

def4567890ab

Pricing layout refresh

Touches the affected pricing flow and introduced a larger mobile media bundle.

9a8b7c6d5e4f

Checkout script loading change

Moved the checkout script behind a new lazy-loading path that may delay activation on slow devices.

Next action
This is what makes the report actionable instead of just descriptive.
Inspect the pricing layout on mobile Safari first.
Compare the checkout script loading change against the previous stable release.
Keep watching the same release group for 2 hours before deciding between rollback and hotfix.
About this demo
This synthetic sample shows the structure of a Deploy Impact Report: verdict, evidence, suspect commits, and next action in one screen.
What it demonstrates: a post-deploy review with one conclusion, not a generic dashboard tour.
How to read it: start with the verdict, scan the evidence, then move straight to the next action.
How to continue: recreate the same workflow in Releases, Impact, Reports, CLI, or MCP after you connect your own site.

Try the same workflow with your own site

Every deploy gets an impact report.
Connect a site, install the script, create or receive a release, and compare your own deploys against the same report structure shown above.
Start checking deploysBack to homepage