# BugTape vs Faultline

Faultline is Sentry-SDK compatible error tracking you can self-host (MPL-2.0) or run hosted at faultline.live, with a GitHub App that turns CI failures into issues. BugTape is a hosted service with browser replay, a user bug button and an MCP agent inbox.

No account: `npx -y bugtape --help` prints the commands and does not sign you in. MCP needs one sign-in.

Page owner: Jaco Veldsman, hi@bugtape.ai. Last checked 2026-10-16.

## What Faultline publishes

Checked on Faultline's own site on 2026-10-16:

- MPL-2.0 licence: one Go binary plus a Dolt server. It also runs hosted at faultline.live.
- Accepts the Sentry envelope v7 ingest format, so Sentry SDKs can point at Faultline.
- A GitHub App turns `workflow_run` and `check_run` failures into issues, one GitHub issue per error.
- A regression reopens a resolved issue.
- Signed outbound webhooks.
- MCP server for Claude Code, Cursor and Windsurf: list issues, fetch stack traces, `mark_resolved`.
- Session replay and a user bug button are not stated on their site.

## What BugTape does

BugTape does not record every visit. It keeps a short buffer and sends it with a supported error or a user report. Repeats of the same failure become one issue. An authorized agent reads that issue over MCP after one sign-in. DOM replay is rebuilt from events; it is not a screen video. Server SDKs (Node.js, Python) add route, service and release so a fix anchors to what shipped.

## Facts

| | Faultline (their site, 2026-10-16) | BugTape (our docs) |
|---|---|---|
| Licence / self-host | MPL-2.0: one Go binary plus a Dolt server; also hosted at faultline.live | Hosted only |
| Sentry SDK compatible | Yes (envelope v7) | No; BugTape SDKs or HTTP ingest |
| CI failures as issues | Yes, GitHub App on workflow_run/check_run | No |
| Session replay | Not stated | Browser replay around each failure |
| User bug button | Not stated | Yes |
| MCP | List issues, fetch stack traces, mark_resolved (Claude Code, Cursor, Windsurf) | Ranked inbox, repro pack, ack + PR URL, listen |
| Regressions | Reopen a resolved issue | Reopen as a regression anchored to the release |
| Price | See https://faultline.live | Free; $10 prepaid = 2,000 credits; Pro $29/mo |

## When each fits

Use Faultline when you want to keep Sentry SDKs, self-host an open-source tracker, or turn CI failures into issues automatically. Use BugTape when you want browser replay, a user bug button and a hosted MCP agent inbox with PR acknowledgement, with no binary or Dolt server to run.

## FAQ

### Is Faultline better than BugTape?

It depends on the job: Faultline wins if you want to keep Sentry SDKs, self-host an open-source (MPL-2.0) tracker, or turn CI failures into issues automatically.

### Does Faultline have an MCP server?

Yes, for Claude Code, Cursor and Windsurf, according to its public site.

### Does BugTape self-host?

No. It's hosted, and data is stored in Sydney.

### Can I try BugTape free?

Yes, on the Free plan with no credit card.

## See also

[Compare](/compare/) · [BugTape vs Sentry](/compare/sentry/) · [Best error tracking MCP servers](/blog/best-error-tracking-mcp-servers/) · [BugTape vs ObserverKit](/compare/observerkit/) · [BugTape vs SnagFrog](/compare/snagfrog/)

## Try the commands

```bash
npx -y bugtape --help
```

Your team reviews the PR. Agents do not silent-ship.