Theirside docs

How to run the collector, add the SDK to your app, and make alerts fit how your providers behave.

• Getting started

  Run the collector, add the SDK to your app, see your first provider and get alerts in Slack, in about ten minutes.

• Node servers

  Add Theirside to an Express, Fastify or NestJS app, in ESM or CommonJS, with the right service and environment names.

• Serverless

  AWS Lambda with wrap() behind API Gateway, ALB or a function URL; when events are sent; webhooks on Lambda; Cloudflare Workers, Deno and Bun.

• Webhooks

  How the webhooks providers send you are monitored, which senders are recognised, how unknown ones are discovered and confirmed, and how to debug a missing one.

• Expected outcomes

  Tell Theirside when a provider's error status is a normal answer (a consent check answering 400), in code with markExpected or expecting, or from the dashboard.

• Self-hosting

  Run the collector with Docker Compose, on ECS Fargate or Kubernetes; settings, upgrades, backups, a load balancer in front, and a public status page.

• Configuration

  Every init() option of the SDK and every environment variable of the collector, with defaults.

• Privacy

  What the SDK records about each call and webhook, what it never captures, and how paths are kept free of personal data.

• Troubleshooting

  A provider doesn't show up, a webhook isn't discovered, alerts are too noisy, or the collector is unreachable: what to check first.

• Set up with an AI coding agent

  Two prompts to paste into Claude Code, Cursor or Copilot, one that adds the Theirside SDK to your app and one that adds the collector to your infrastructure, each changing nothing else.

For AI agents: /llms.txt lists every page, /llms-full.txt has them all in one file, and each page is also plain Markdown at its URL plus .md.