A Sentry alternative that comes back after the release.

What Sentry is built to answer

Sentry is built for the first minute: an alert the moment an error is new, the stack trace, the release it first appeared in, and a way to mark it resolved so it reopens if it comes back. For a team on call, that is the right tool, and Forge does not try to be it.

What the alert does not tell you is whether the error matters to the product — whether people stopped completing the thing the page is for — or, once the fix is out, whether the week after looks different from the week before.

What Forge reads from the same errors

Your app sends its errors, events and logs to Forge with a small SDK (browser, Node, serverless and Next.js) or plain HTTP. Once a day Forge counts them and states what moved, with the window, the baseline and the rule beside every number.

• Exact counts. Errors are grouped by a versioned fingerprint and counted from every row, never from a sample.
• An issue with its rule. An error opens an issue when its events over the last 7 days are at least 50 % above the 7 days before, from at least 20 events. Below that volume Forge says why it is not judging yet.
• The error beside the journey. When sign-up completion falls on /signup, the issue shows the errors from the same page in the same days, so the two facts are read together.
• Per thousand sessions. Errors are also stated per 1,000 sessions, so a week with more traffic is not read as a worse one.
• The release, measured. Your tracker sends the release with every row. Forge compares the days before that version reached production with the days after, under a plan written before it shipped, and says what it saw: improvement, no change or regression.
• A spec for your agent. Each issue opens with a work spec Forge writes from the counts; on a paid plan the model drafts one too, every number checked against the counts. It goes to Claude Code or Cursor; Forge writes nothing to your repository.

npm install @ambera/forge-tracking

import { createForgeTracker } from '@ambera/forge-tracking'

const forge = createForgeTracker({
  token: 'ftk_…',            // your product's tracking key, safe in page source
  environment: 'production',
  release: COMMIT_SHA,       // how Forge knows which version sent each row
})

forge.track('signup_completed')
forge.captureException(error)