Callra docs

Know if your latest deploy broke growth.

Every deploy gets an impact report.

Callra is not another dashboard to check.

Callra is a post-deploy reviewer for small SaaS teams. The product is organized around one core object: the Deploy Impact Report.

10-minute first deploy check

1. Create site
2. Install script
3. Verify first pageview
4. Get first speed sample
5. Create or connect first release
6. Read the first deploy report in Releases

Start here

1. What is Callra?
2. Create your first site
3. Releases
4. Impact Analysis

Docs by workflow

First deploy check

• Create your first site
• Install the tracking script
• Using the dashboard

Read the report

• Releases
• Impact Analysis
• Reports and incidents

Continue the investigation

• Agent, CLI, and MCP workflows
• Agent Skills and MCP

Core product guides

• Framework adapters
• Manage sites and sharing
• Privacy and data

Reference

• Tracker API
• Environment variables
• Commands
• FAQ

What Callra gives you today

• Deploy impact reports with verdicts, evidence, affected slices, suspect commits, and next actions.
• Impact Analysis that expands the same deploy review into traffic, conversion, speed, revenue, and incidents.
• Reports and alerts for daily reports, Worry Inbox, anomaly incidents, and follow-up delivery history.
• Site-scoped agent access through CLI, MCP, and machine-facing APIs.
• One shared script.js install path for both Web Analytics and Speed Insights inputs.

Recommended first run

1. Create your account.
2. Create one site and allow the real production or preview hostnames.
3. Paste the shared snippet into a real page.
4. Verify the first pageview.
5. Wait for the first speed sample.
6. Open Releases and create one manual release or connect a deploy provider.
7. Read the first deploy impact report.
8. Open Impact Analysis when you need broader business context.
9. Turn on reports or alerts when the team wants proactive follow-up.