No borrowed logos, no vague claims — five things the product does that a stitched-together stack can't.
Analytics, replay, flags, campaigns and chat usually mean five vendors, five trackers and numbers that never match. In Kilden every feature reads the same events and the same people — the funnel, the campaign and the replay always agree.
Your backend signs who the user is — a standard JWT, nothing exotic. Nobody can impersonate a customer to read their chat or fire their campaigns. Most tools take identity on faith; Kilden verifies it.
One install with autocapture: pageviews, clicks and forms captured from minute one — no tracking plan meeting required. Server SDKs when you need facts from the backend.
Kilden replaces an analytics tool, a replay tool, a flag service, an email platform and a chat widget. You pay for what you use — events, replays, messages — never for seats. Your whole team gets in.
Every feature included, generous limits, no credit card. You upgrade when your traffic grows — not to unlock the product.
This site is customer zero. Everything on this page is running on the product it sells — watch it work.
That's Kilden Messenger. Ask us anything — we see your visit in context, not a blank slate.
Any banner or survey on this site is a Kilden in-app unit, targeted by behavior — no deploy behind it.
Our onboarding nudges are a Kilden campaign. They cancel themselves the moment you activate.
It's already an event in our own dashboard, through the exact pipeline you'd get.
Where Kilden wins — and where it doesn't, yet.
| Kilden | Stitched stack | All-in-one suites | |
|---|---|---|---|
| Trackers to install | 1 |
5 |
1 |
| Numbers match across features | always |
never quite |
~ mostly |
| Verified identity (backend-signed) | |||
| Campaigns + live chat built in | via integrations |
partial |
|
| Pay per seat | never |
usually |
sometimes |
| Self-hosting | not yet |
some |
|
| CDP destinations (export elsewhere) | on the roadmap |
partial |
The last two rows are ours to lose — on purpose. Self-hosting is under evaluation; export destinations are on the roadmap.
Engineering, not marketing. Send this section to whoever asks the hard questions.
Fast enough to sit in your render path.
At-least-once pipeline with deduplication at every edge. Your numbers stay honest.
Exactly-once delivery per journey node. Nobody gets the same message twice.
Recovery isn't a checkbox: we rehearse full restores, on a schedule.
A live dashboard with real-looking data — funnels, replays, campaigns and flags. No signup, no email, no sales call.
We take data protection seriously. Our privacy policy spells out exactly what we collect and why, we keep a documented retention policy, and we ship operator tooling to delete or export a person's data on request (access, erasure and portability). Suppression lists and consent-driven capture let you honor opt-outs end to end.
Yes. Send historical events through the SDKs or the ingestion API, and run Kilden in parallel during the switch — the free tier makes that cost nothing.
You get a heads-up well before any limit, and upgrading is usage-based pricing — no plan negotiation, no seat math.
The SDKs cover ingestion across seven languages, and an MCP server (@kilden-io/mcp) lets Claude or any MCP client query your data in plain language. A full public read API is on the roadmap.
Don't trust — verify. The demo is open, the docs explain the architecture, and the free tier is the full product. Judge it working.