The intelligence layer for your event pipeline.

Track events from anywhere, send them through elaborate data processing pipelines, and route each one to the destinations you need.

One process sits between everything that produces signals at your company and everything that consumes them. It accepts the signal, runs an ordered stack of typed transformations on it, and fans the result out. Fourteen actions today, in three categories. Pick the ones each event family needs.

fig. 1 — the spine. Three stages per signal. The middle is a stack you compose.

Every signal walks the same three stages. The middle one is a stack of typed actions you compose per event family. Page views skip the stack and go straight to route. Signups get the whole kitchen.

01

ingest

Accept the signal as it arrives. Durable, typed, idempotent.

02

transform

An ordered stack of typed actions. Pick from fourteen today: enrichment that adds fields, mutation that rewrites them, control that may drop the event.

03

route

Branch on the typed result. Fan out. Retry. Dead-letter. Replay.

Order matters. Dedupe before classify saves model calls. Redact before route enforces PII at the wire.

Anywhere signals come from. SDK, webhook, AI agent, and GitHub are live today. Python SDK and Stripe land next.

• sdk.eventTypeScript SDK[ready]
• webhook.inHTTP webhook[ready]
• agentAI agent[ready]
• githubGitHub events[ready]
• emailInbound email[ready]
• sdk.pyPython SDK[soon]
• stripeStripe events[soon]

Anywhere they need to land. One signal, many destinations, shaped differently for each consumer.

• slackSlack[ready]
• telegramTelegram[ready]
• webhook.outHTTP webhook[ready]
• email.outEmail[ready]
• warehouse.pgPostgres[ready]
• discordDiscord[ready]
• notion.dbNotion[ready]
• warehouse.bqBigQuery[soon]
• linear.issueLinear issue[soon]
• s3S3 / object[soon]

Events arrive from the TypeScript SDK matching team.member.invited. The pipeline enriches with the user entity matched on $event.inviter_id, enriches with person data from $event.invitee_email, enriches with the account entity matched on $entity.user.account_id, classifies along pattern (4 labels) and priority (4 labels), and redacts PII (with per-destination overrides). Routed to Slack in #cs, email to cs-leads@ingestlayer.io, and Postgres (table events.team_invite).

$ pnpm add @ingestlayer/sdk
$ echo "INGESTLAYER_KEY=il_…" >> .env

# in your app code:
import { init, track } from "@ingestlayer/sdk";

init({ apiKey: process.env.INGESTLAYER_KEY! });
track({ type: "user.signup", payload: { email: user.email } });