Stop renting your customer graph.
Drop-in identity resolution that runs on your infra. Open-source core, $99/mo Pro. Reserve early access today.
The buy-or-build trap
Why most SaaS teams give up on identity resolution.
- 01Buy a SaaS CDP (Segment Personas, mParticle) and pay $15k+/year to ship every event your users generate to a third party.
- 02Or hand-stitch identity in dbt and SQL — endless edge cases, race conditions on simultaneous merges, and no one to ping when production data goes sideways.
- 03Either way, you don't own your merge logic. The rules driving your customer graph live in someone else's binary, or in a Slack thread from 2024.
Buy vs build vs idx
Same outcome, very different trade-offs.
| SaaS CDP (Segment / mParticle) | DIY (dbt + SQL) | idx | |
|---|---|---|---|
| Pricing | $15k+ / yr + per-MTU | Free + months of eng time | ✓$99 / mo flat per app |
| Where data lives | Twilio cloud | Your warehouse | ✓Your VPC, your servers |
| Customizable merge rules | Limited (their DSL) | Yes (you write SQL) | ✓Yes (config-driven) |
| Time to first merge | Weeks (sales cycle) | Months (build it) | ✓Hours (drop binary) |
| GDPR delete cascade | Manual ticket | You build it | ✓Built in |
| Vendor lock-in | High | None | ✓None (Apache 2.0 core) |
Comparison reflects publicly stated pricing & capabilities at time of writing. We'll get the details wrong sometimes — tell us at the founder's email below.
How idx works
Three steps. Self-contained binary. Your infrastructure.
- STEP 01
Drop in the binary
One self-contained binary. Deploy alongside your existing stack — Postgres or any SQL warehouse for storage. No data leaves your VPC.
- STEP 02
Define your merge rules
Express identity merge logic in plain config. Email + device ID? Phone + Stripe customer ID? Workspace + invited-by? Your call. Deterministic only — no probabilistic guessing, GDPR-friendly by default.
- STEP 03
Query unified profiles
REST API or SQL view over a single source of truth. Get the full event stream for any user, regardless of how they signed up — and replay history when merge rules change.
Open core, fair pricing
Built like Sidekiq: free OSS forever, paid Pro when production demands it.
Pro adds: web admin UI, audit log, merge undo/replay, GDPR delete cascade, crash-safe merge. Stripe authorization only — no charge today, only when Pro ships and you confirm.
✓ Card authorization only · ✓ No charge today · ✓ Cancel anytime
Reserve your spot
Tell me about your SaaS and how you handle identity today. I'll reach out personally before Pro ships.
FAQ
When does it launch?+
OSS binary targets Q3 2026. Reserved early-access seats get the binary 2 weeks before public release, plus locked-in Pro pricing for life.
Will I be charged today?+
No. The 'Reserve at $99/mo' button uses Stripe authorization-only — your card is held but not charged. We capture the charge only when Pro ships and you confirm by email. You can cancel anytime before that.
How is this different from Segment Personas / mParticle / RudderStack?+
Same core capability — unify identities across login methods, merge event streams. The differences: (1) open-source core you can audit, (2) runs in your own infra so customer data never leaves, (3) merge rules are programmable, not opinionated, (4) transparent flat pricing, no per-MTU bills that explode at scale.
Why deterministic only? No probabilistic merging?+
Probabilistic identity merging (guessing two anonymous users are the same based on device fingerprints) is a privacy minefield, hard to audit, and increasingly illegal under GDPR/DPDP. We do rule-based deterministic merge — the part Segment does well — and stop there. Your compliance team will thank you.
What's already built? Can I see code?+
Core merge engine is functional in private. The team is polishing it for public release based on early-access signups. If you're a fit and would actually pay, reserve a spot and we'll talk — including a peek at the code if it's mutual.
Who's building this?+
A solo developer who built customer-data infrastructure at a previous SaaS, watched users repeatedly ask for ID resolution, and saw the gap between Segment's enterprise pricing and what Series A/B teams actually need. Building in the open at https://github.com/yangou (repo goes public at launch).