Installation

Install the package that matches your stack. You can mix and match — for example, @autter/runtime-browser on the frontend with @autter/runtime-node on an Express backend.

npm install @autter/runtime-browser   # frontend (React, Vue, any SPA, static sites)
npm install @autter/runtime-node@^1.3.1
npm install @autter/runtime-next@^1.3.1

Frontend
Backend
Next.js

Errors and usage, automatic from init:

import { initAutterBrowser, captureException, trackEvent } from "@autter/runtime-browser";

initAutterBrowser({
  endpoint: "/api/autter-runtime",   // your relay route (recommended), or
  // endpoint: "https://otlp.autter.dev/v1/browser", clientKey: "autter_rtc_…",
  service: "web-app",
  release: import.meta.env.VITE_GIT_SHA,
});

captureException(err, { operation: "start-checkout" });
trackEvent("clicked_upgrade");

React render errors don’t reach window.onerror — wrap your app with the error boundary (exported from @autter/runtime-next, works in any React app):

<AutterErrorBoundary fallback={<ErrorPage />}>
  <App />
</AutterErrorBoundary>

Static site with no backend? Deploy the serverless relay and keep endpoint: "/api/autter-runtime" — see Stack integrations. Direct ingest with a client key is a lossy fallback only.

One preloaded file, requests traced automatically:

// instrument.cjs — run with: node --require ./instrument.cjs server.js
const { initAutterServer } = require("@autter/runtime-node");
initAutterServer({
  apiKey: process.env.AUTTER_RUNTIME_KEY,   // secret server key
  service: "payments-api",
  environment: "production",
  release: process.env.GIT_SHA,
  retainTracesAboveMs: 2000,
});

ESM-only app? Use --import plus OpenTelemetry’s loader hook — see the @autter/runtime-node package README.

npm install @autter/runtime-next@^1.3.1

Three files give you server tracing, browser tracking, the relay, and the error boundary — instrumentation.ts, app/api/autter-runtime/route.ts, and a client component. See the @autter/runtime-next package README for the exact snippets.

Enable endpoint regression telemetry

Reuse existing SDK initialization and pass the options only once. Set release to the deployed commit SHA and use the actual deployment environment. The backend example opts into bounded slow-request retention; the SDK default is off. For Next.js, pass retainTracesAboveMs: 2000 to the existing registerAutter call. The platform rollout does not change installed SDK settings. Self-hosted ingesters require 1.3.1 or later. See Endpoint regressions for request histogram requirements, trace comparison, team feedback, and draft fix review.

Get a key

Every ingest key is scoped to one orgId + repositoryId. If you’re self-hosting the ingester, generate a key yourself — see Environment variables. If you’re using Autter’s hosted ingester at otlp.autter.dev, create a key from your Autter organization.

No npm in this codebase?

Any language with an OpenTelemetry SDK can send server telemetry with configuration only — no @autter/* package required. See Using Autter Runtime without npm.

Stack integrations

Per-stack setup snippets — React, Node, Next.js, Go, Rust, and any OTel SDK.

Self-hosting

Run the ingester yourself, or point at Autter’s hosted endpoint.

Get started

Guides

Reference

Enable endpoint regression telemetry

Get a key

No npm in this codebase?

Stack integrations

Self-hosting

​Enable endpoint regression telemetry

​Get a key

​No npm in this codebase?

Stack integrations

Self-hosting

Enable endpoint regression telemetry

Get a key

No npm in this codebase?