TempsTemps

Error tracking

Know about errors before your users report them.

Sentry-compatible error tracking, built in. Point your existing SDK at Temps and get stack traces, source maps, error grouping, regression detection, and real-time alerts — self-hosted, with no per-event pricing.

Try it yourselfRead the error tracking docs

Every official Sentry SDK works, unmodified

React
Node.js
Python
Go
Ruby
PHP
Java
.NET

Sentry-compatible error groups with events and timelines — the same view your existing SDK already talks to.

  • Your existing Sentry SDK just works

    Temps injects SENTRY_DSN and SENTRY_RELEASE into every deploy automatically — keep the Sentry SDK you already have installed, no new library, no rewritten error-capture code.

  • Stack traces with source maps

    Errors resolve to readable stack traces, not minified line numbers — source maps are handled the same way Sentry expects them.

  • Error grouping and regression detection

    Related events collapse into a single issue, and a fixed error that comes back gets flagged as a regression instead of buried in a new group.

  • Real-time alerts to Slack or Discord

    Your team hears about a new error the moment it happens, not the next time someone checks a dashboard.

  • Unlimited events, no per-event pricing

    Self-hosted means there's no event quota to hit and no bill that grows with a bad deploy — the exact week you'd need it most.

  • Autofix: from error group to open PR

    Click Fix on any error group and an AI agent reads your actual codebase, finds the root cause, and opens a pull request — gated on connecting a git provider, so it never runs against a repo you haven't authorized.

No dashboard step, no copy-pasted DSN

Temps sets the DSN and release for you.

Every deploy gets its own SENTRY_DSN — generated per project and environment — plus SENTRY_RELEASE, tagged automatically from the commit SHA or image digest you just deployed. Your Sentry SDK just reads the environment; there's no key to generate, copy, or store in your repo.

import * as Sentry from "@sentry/react";

// Temps injects a public, framework-specific DSN var at deploy time —
// VITE_SENTRY_DSN for Vite-based apps (React, Vue, Remix, SolidStart),
// NEXT_PUBLIC_SENTRY_DSN for Next.js.
Sentry.init({
  dsn: import.meta.env.VITE_SENTRY_DSN,
});

Change one DSN. Keep your SDK.

Point your existing Sentry SDK at your own Temps instance — errors start flowing in immediately.

Try it yourself — quickstart guide