Request-level context when production breaks — without a full APM suite.
The problem
When something fails in production, teams need the request that failed, the error that grouped with it, and the release it landed in — not a wall of unrelated dashboards.
One footprint per request. Similar errors become issues. Releases stay visible.
How it works
From signup to your first footprint — without the ceremony.
Sign up, create an organization and project, copy your DSN.
Install the Insider SDK for your language, initialize with your DSN, deploy.
Requests beam to Insider; errors group into actionable issues.
Product
The pieces that matter when production breaks: the request, the issue, the release, and a path to notify the team.
Footprints
See the path, status, timing, related logs, and the exception when something fails — tied to a single HTTP cycle.
Shape
1 → 1
request to footprint
Issues
Group repeating failures into issues you can open, resolve, or ignore — including when a fixed error comes back.
Workflow
Open · Resolve
Ignore when it is noise
Releases
Compare two releases to separate brand-new failures from ones that came back and issues still open.
Compare
New · Returned · Still open
Pro and Pro+
Alerts
Notify the team when issues are new or returned — in the product first, then out to the channels you connect.
Triggers
New · Returned
wired from project settings
Teams
Invite teammates into the organization and project so debugging is not a private screenshot thread.
Access
Org · Project
roles, not shared passwords
Reliability
The SDK beams in the background and is designed so a bad day for Insider does not become a bad day for your app.
Guarantee
Never crash
the host application
SDK
Language-agnostic contract — same DSN, same beam path. Prefer INSIDER_DSN in your environment.
pip install "insider-python[django]"
import insider
from insider.integrations.django import DjangoIntegration
from insider.integrations.logging import LoggingIntegration
insider.init(
dsn="https://<token>@theinsiderinc.com/<project>",
environment="production",
release="1.2.3",
integrations=[DjangoIntegration(), LoggingIntegration()],
)
Coming soon
The Go SDK is in progress. Same DSN and beam contract as Python and Node — install instructions will land here when it ships.
Coming soon
The Java SDK is in progress. Same DSN and beam contract as Python and Node — install instructions will land here when it ships.
npm install insider-node
import * as insider from "insider-node";
import {
ExpressIntegration,
expressRequestHandler,
expressErrorHandler,
} from "insider-node/express";
insider.init({
dsn: "https://<token>@theinsiderinc.com/<project>",
environment: "production",
release: "1.2.3",
integrations: [new ExpressIntegration()],
});
app.use(expressRequestHandler());
app.use(expressErrorHandler());
Coming soon
The Rust SDK is in progress. Same DSN and beam contract as Python and Node — install instructions will land here when it ships.
Integrations
When something breaks, the signal should land in the tools you already use — not only inside another dashboard.
Issue alerts to a channel via incoming webhook. Available on Pro and Pro+.
Notify members when issues appear or regress. Extra recipients on paid plans.
Suspect commits on release compare with a connected repo and PAT. Pro and Pro+.
POST alert payloads to your own HTTPS endpoint. Available on Pro and Pro+.
Route issue alerts into Teams channels alongside the rest of your incident chat.
Push critical returned issues to on-call groups when email and Slack are not enough.
Open or link tickets from Insider issues so tracking stays in your existing backlog.