ingestlayer

About ingestlayer

ingestlayer is a programmable event pipeline that sits between everything at a company that emits events and everything that consumes them, so that signals arrive classified, redacted and routed rather than raw. Every signal walks the same three stages. Ingest accepts it durably, typed and idempotent, from an SDK, an inbound webhook, an agent or GitHub. Transform runs an ordered stack of typed actions you compose per event family — fourteen are available today, spanning enrichment that adds fields (entity, person, company), mutation that rewrites them (classify, summarise, translate, AI transform, HTTP request, upsert entity, PII redaction), and control actions that may drop the event entirely (dedupe, throttle, filter). Route then branches on the typed result and fans out to Slack, Telegram, a Postgres warehouse or an outbound webhook, with retries, dead-lettering and replay. The composition is the point: a page view can skip the stack and go straight to routing while a signup gets the full treatment, without either path needing its own bespoke service. In-flight PII redaction before an event reaches a destination is the piece that is hardest to bolt on afterwards. Billing is per arrival and metered once per event — not once per destination, per pipeline or per transform step — and events dropped at the gate are not charged, which makes the cost of adding a destination or a step zero rather than multiplicative.

Key Features

ingestlayer Pros & Cons

Tags