kilden_
$ kilden — the source

One source.
Every answer.

Product analytics, feature flags, and behavioral campaigns — on a single event pipeline you can trust.

~ two minutes to first event
$ npm install kilden

// app.js
kilden.init('wk_...')
kilden.track('checkout_completed', { amount: 29990 })
autocapture included — install the snippet, watch your events flow in live
live tail — events streaming
timestamp event distinct_id identity
09:41:07.312 $pageview anon_019f3c2e-8a41 anonymous
09:41:06.874 checkout_completed usr_4821 verified ✓
09:41:06.221 $autocapture usr_4821 verified ✓
09:41:05.660 search_performed anon_019f77aa-01c4 anonymous
09:41:04.981 cart_added usr_1194 verified ✓
09:41:04.412 $autocapture anon_019fb2d0-44e9 anonymous
09:41:03.777 signup_completed usr_7305 verified ✓
09:41:03.150 $pageview usr_7305 verified ✓
$ ls features/

Four products. One pipeline.

available now

Product analytics

Funnels, trends and retention over every event you capture — no sampling, no separate tracking plan. If it happened, you can query it.

funnel · checkout last 30 days
product_viewed 48,210 · 100%
cart_added 19,842 · 41%
checkout_started 9,120 · 19%
checkout_completed 6,743 · 14%
biggest drop-off: cart_added → checkout_started −54%
new-checkout-flow
serve to cohort
completed_onboarding used_search · last 7d
rollout 25%
evaluated in 3.2ms ● serving 25% of cohort
available now

Feature flags

Target releases by real behavioral cohorts — not just user properties. Evaluation under 5ms, instant kill-switch when things go wrong. Try the toggle.

<5ms evaluation instant kill-switch cohort targeting
coming soon

Behavioral campaigns

Emails triggered by what users do — cancelled the moment they convert. Campaign metrics re-enter the pipeline as plain events, so open→click→convert is just another funnel.

trigger cart_abandoned
wait 4 hours
send email: “still there?”
✕ exit checkout_completed → campaign cancelled
session · illustrative preview
2:40 / 07:52
coming soon

Session replay

Watch the sessions behind every funnel drop-off. Same events, same identity — jump from a chart straight to the recordings that explain it.

$ cat differentiator.md

Identity you can verify

Events from authenticated users are verified with a JWT signed by your backend. Nobody can spoof a user_id from the browser console — spoofing is impossible, not just unlikely.

One pipeline, zero drift: every feature reads from the same events. Your funnel, your flag targeting and your campaign triggers can never disagree.

// your backend signs, kilden verifies

const token = jwt.sign({ sub: user.id }, KILDEN_SECRET)

kilden.identify(user.id, { plan: 'pro' }, { token })
// → Authorization: Bearer <token>
// → distinct_id verified ✓  spoofed events rejected ✕
$ whoami → product manager

Stop filing tickets for data.

Your engineers install it once. From then on, every funnel, cohort and campaign is self-serve — no SQL, no tracking plan meetings, no waiting for the next sprint.

without kilden
PM
Hey, can we get data on where users drop off in checkout? 🙏 monday, 9:14
ENG
Need to add tracking first. I'll create a ticket — realistically the sprint after next. monday, 11:52
answer in ~3 weeks, if the ticket survives grooming
with kilden
1.open funnels → checkout
2.autocaptured events are already there — no tracking plan
3.drop-off found: cart → checkout −54%
4.launch recovery campaign on that cohort — yourself
answer in 3 minutes · zero engineering tickets
kilden-mcp coming soon
Or skip the UI entirely — ask your data in plain language from Claude or any MCP client: "why did checkout conversion drop last week?"
it's a 2-minute install — they'll thank you
By the way — you can install it yourself. Just ask your AI agent:
 Install kilden (npm package "kilden") in this project. Init it with my write key from app.kilden.io/settings, enable autocapture, and add a kilden.track() call to our main conversion event. Docs: docs.kilden.io/install
$ cat pricing.txt

The free tier is the product, not a demo.

Free

free forever, not a trial
1M events / month
1M flag requests
unlimited team members
cohorts & campaigns included
5K session replays coming soon
start free — no credit card

Pay as you go

prices coming soon
usage-based, on top of the free tier
no seats, no contracts
set your own billing caps
early users lock in launch pricing
get early access
$ ls use-cases/

What one pipeline unlocks

01

Recover abandoned carts

An email that cancels itself the moment the user converts. No “you left something behind” after they already bought.

02

Ship behind flags

Roll out to cohorts built from real behavior — “used search this week”, “completed onboarding” — not static user lists.

03

Onboarding that adapts

Sequences driven by what each user actually did — skip the steps they finished, nudge the ones they didn’t.

04

A/B test on the same numbers

Split traffic with a flag, measure both variants in the same funnel. No exporting events to a separate experiments tool.

05

Marketing on autopilot

Upgrade nudges, win-back emails, usage milestones — triggered by behavior, running without anyone pressing send.

06

Catch churn before it happens

Cohort of “active last month, quiet this week” → re-engagement campaign fires automatically. Growth loops, not dashboards.

$ man kilden

Questions, answered honestly

How is this different from PostHog or Mixpanel? +

Two things. First, verified identity: authenticated events carry a JWT signed by your backend, so nobody can spoof a user from the console. Second, one pipeline — analytics, flags and campaigns all read the same events, so your numbers never drift between tools.

Where does my data live? +

In Kilden’s cloud, in a dedicated ClickHouse + Postgres store per workspace. You can export everything at any time — your events are yours.

What are the team limits? +

None. Unlimited members on every plan, including Free. We charge for usage, not for people.

What does “coming soon” actually mean? +

It means it isn’t built yet. We label the roadmap honestly instead of selling features that don’t exist — campaigns and session replay are next, in that order.

Can I self-host? +

TBD. The architecture doesn’t rule it out, but we haven’t committed to supporting it yet. If it matters to you, tell us — it shapes the roadmap.