Browser & device
The exact browser, OS and viewport the bug happened on.
Click, capture, resolve.
Open bug and change requests as they happen, directly from your website, with full device, network, browser and repro context included.
// Captured automatically
Reproducible by default. Full engineering context.
The moment an issue is flagged, Rebase captures everything an engineer needs to reproduce it — no extra steps for the person reporting.
Console logs
Every error and warning from the session, as it happened.
Network activity
Failed and slow requests, with status codes and timing.
Screenshot
A full-page screenshot from the moment it was flagged.
Reproduction steps
The exact clicks and inputs that led to the bug.
Element & code context
The flagged element, its selector and component name.
// GitHub / Linear / Jira / Asana
Lands in your tracker. No second inbox.
Every report files into GitHub, Linear, Jira or Asana as a structured issue, mapped to the right project — with no new workflow to learn.
GitHub issues
Reports open as issues in your repo, ready to pick up.
Linear issues
Filed into the right Linear team and intake column.
Status stays in sync
Close it in your tracker and it closes in Rebase.
// Triage
Points to the fix. Down to the line.
Every report comes triaged — a summary, a severity, and the likely source down to the file and line. Duplicates merge into one clean, structured issue.
Suspected source location
Matched to your connected repo to name the likely file.
Duplicate detection
Repeat reports are matched and linked, not piled up.
Summary & severity
Every report arrives summarised and prioritised.
// Privacy
Masked on the page. Only what you need.
Inputs are masked in the browser, scrubbed again server-side, and every customer's data stays isolated to its own tenant.
Mask by default
Password, card and phone fields are never captured.
Redact any element
Hide anything with a single data attribute.
Server-side scrubbing
Tokens and PII are stripped before anything is stored.
// Pricing
One price per website. Unlimited users.
One flat price with everything Rebase does in the box. Invite your whole team and your clients — the price never changes. No seats, no tiers, no surprise overage.
Pro plan includes:
- Owners, teammates, commenters and viewers are all covered by the flat price. Invite your whole team and your clients; the bill stays the same.Unlimited users — every role, included
- Each report is summarised, given a severity and a likely source. 200 credits reset monthly; if they run out, triage fails open and tickets still reach your tracker.200 AI triage credits per project, monthly
- Search every report by meaning, not just keywords, with no query limits.Semantic search — uncapped
- Reports draft issues in your tracker with the triage and screenshot embedded, and status syncs both ways.GitHub, Linear, Jira & Asana sync
- An MCP server gives Claude Code, Cursor or any MCP client tools over your tickets — with scoped, revocable tokens.MCP server for coding agents
- Rebase surfaces errors it detects on your site before anyone reports them, so you hear about breakage first.Proactive error detection
- Captured screenshots are kept for 90 days, then automatically deleted.90-day screenshot retention
Frequently asked questions
Paste one script tag — no API key, your domain identifies your project — then claim your site from your own site: verify the domain with a meta tag, pick a handle, start the 7-day trial (card required). There's deliberately no dashboard to learn.
The flagged element, the last 50 user actions, 50 console entries and 50 network requests, a device snapshot and a screenshot — merged into one causal timeline: Clicked 'Save' → POST /orders returned 500 → TypeError follows.
Every report gets a summary, repro steps and a severity right after capture, and is classified as a bug, change request or question. Summary sentences link to the evidence. Projects include 200 AI credits a month — and if they run out, triage fails open: the ticket still reaches your tracker.
New tickets draft issues in GitHub, Linear, Jira or Asana with the AI triage and screenshot embedded, and status syncs both ways. Duplicates are detected and linked, with a cross-reference on the canonical issue.
Yes. An MCP server (@rebasedotdev/mcp) gives Claude Code, Cursor or any MCP client five tools over your tickets — with scoped, revocable tokens. Agent replies land in the same thread your team watches.
Everything typed is masked by default before it leaves the page, and passwords, cards and one-time codes are hard-blocked. No session video, no DOM replay, no keystroke log. Screenshots are deleted after 90 days, and every tenant's data is fully isolated.
$69/month per website, or $690/year — about two months free. Unlimited users, whatever their role. That covers 200 AI triage credits, all four tracker integrations, MCP access for coding agents, proactive error detection and 90-day screenshot retention.
Yes — a 7-day free trial, card required, once per user. If a subscription ever lapses, everything goes read-only rather than being deleted, and reactivating restores it instantly.
Start shipping feedback faster.
Start your 7-day free trial.