The problem
To answer a single question — "why aren't people activating?" — a product team ends up paying for four tools. One shows the funnel, another records sessions, another ships the experiment, and a fourth sends the message. Each defines "user" its own way, each brings its own SDK and its own invoice. When the numbers don't match between two dashboards nobody knows which one is wrong, and the whole meeting goes into reconciling data instead of deciding.
What we did
We built Kilden as our own product: six products — product analytics, session replay, feature flags, campaigns, messenger and tours — on a single source of data. Capture flows through one pipeline into Kafka, ClickHouse and Postgres, and lands in real time for every feature: the funnel, the recording of that exact session, the flag targeting that behaviour, and the email that cancels itself the moment the person converts.
Identity is the other pillar. It's verified with a JWT signed by your backend, so every feature sees the same people and the same events with no reconciliation afterwards. For instrumentation there are official SDKs for JavaScript with autocapture, PHP, Node, Python, Ruby, Go and Expo, plus a WordPress plugin and an MCP server to query the data from Claude. Pricing follows usage and never seats: adding the whole team costs nothing extra.
The outcome
Kilden runs in production on infrastructure hosted in Chile, and we use it across our own projects: Elecktro Producciones, Láminas Mundial and Bingoo all ship today with Kilden capture, session replay and messaging — Láminas Mundial with JWT-verified identity on top.
It's the hardest proof of what we offer: not an integration with someone else's tool, but a complete data platform built from scratch — ingestion, analytical storage, dashboard and SDKs — with the same engineering standard we apply to our clients' custom software.
