Identity resolution your way — self-host the binary, plug into Supabase, or use our hosted cloud. Configurable merge strategies, schema-free attributes. We never store a byte of your customer data.
curl -fsSL https://get-idx.nortek-solutions.com | shMerge anonymous visitors with known users across channels, devices, and sessions — without renting your data to a third party.
Priority-based identity resolution. Email beats cookie, phone beats device_id. Configurable per account.
Define merge logic in plain config. 9 strategies for attribute resolution: latest, earliest, union, max, coalesce, and more.
One Rust binary. Connects to Supabase, Neon, or any self-hosted Postgres. SQLite for local dev. No JVM, no Docker required.
Forget and unforget users. Soft-delete preserves identity history for audit. GDPR-aware merge cascades — forget propagates through every merge chain automatically.
Attach any JSON property to a user — plan tier, signup source, custom traits. No schema migrations to add a new field. Merge rules respect data type per attribute.
Built-in Model Context Protocol server. Wire idx into Claude, Cursor, or any MCP-compatible agent. Resolve users, query the merge graph, and debug identity — all from your AI workflow.
Same engine, same API, same console. Different sovereignty / convenience trade-off. Pick the one that fits your team.
Click any card to jump to install. Same engine in all three. Migrate between modes anytime — your schema is yours, your config is portable.
Same outcome. Very different trade-offs.
| SaaS CDP (Segment / mParticle) | DIY (dbt + SQL) | idx | |
|---|---|---|---|
| Pricing | $15k+ / yr + per-MTU | Free + months of eng time | ✓Free OSS · Cloud from $19/mo |
| Where data lives | Vendor cloud | Your warehouse | ✓Your VPC, Supabase, or our cloud — your choice |
| Customizable merge | Limited (their DSL) | Yes (you write SQL) | ✓Yes (config-driven) |
| Time to first merge | Weeks (sales cycle) | Months (build it) | ✓Minutes (drop binary) |
| GDPR delete cascade | Manual ticket | You build it | ✓Built in |
| Vendor lock-in | High | None | ✓None (AGPL v3) |
Pick your install path. All three converge on the same API + console.
Run the binary on your infrastructure. Connects to any Postgres (Supabase, Neon, RDS, your own). AGPL v3 open source.
curl -fsSL https://get-idx.nortek-solutions.com | shmacOS / Linux · auto-detects arch · installs to /usr/local/bin/idx
idx migrate --postgres $DATABASE_URLIdempotent. Re-runs safely on every deploy. Use --sqlite ./idx.db for local dev.
idx serve --postgres $DATABASE_URL→ Listening on 0.0.0.0:4000
curl -X POST $IDX_HOST/api/v1/users -d '{"user":{"email":"..."}}'Or open the built-in web console at $IDX_HOST/console
The web admin UI is bundled into the binary — no separate deploy. Search users, dry-run merges, edit identifier priorities, and audit identity changes from one place.
Active / Forgotten / Merged counts. Paginated table with email, phone, cookie, device_id columns and merge lineage.
Free OSS forever. Cloud starts at $19/mo. Pay as you grow.
Self-host, fork, modify — same license as Plausible & GitLab CE
Pay as you grow · we host the compute
Card auth only · No charge today · Cancel anytime
Multi-tenant · customer-cloud deployment
Tell me about your SaaS and how you handle identity today. I'll reach out personally before Pro ships.
OSS binary targets Q3 2026. Reserved early-access seats get the binary 2 weeks before public release, plus locked-in Pro pricing for life.
No. The 'Reserve at $19/mo' button uses Stripe authorization-only — your card is held but not charged. We capture the charge only when Cloud ships and you confirm by email. You can cancel anytime before that.
Same core capability — unify identifiers across login methods into a single user profile. The differences: (1) AGPL v3 open-source core you can audit, fork, and self-host, (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.
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.
Depends on which deployment mode you pick. Self-host: never — the binary runs inside your VPC, all data is on your servers. Supabase plugin: transiently, in memory during a single merge call — we read from your Supabase, merge in our process, write back to your Supabase, then discard from memory. We hold no persistent copy. Hosted: yes, you opt in to letting us store your merged user records in our managed Postgres (encrypted, region-pinned). Pick the trade-off you want.
Self-host: idx going down means your binary stopped — you operate it, you handle it. Supabase plugin: your reads keep working (they go direct to your Supabase, not through us). Writes queue at the Edge Function level or fail loudly with a retry-safe error. No 'we lost your CDP' scenario — your existing data is untouched. Hosted: standard SLA, status page at status.idx.nortek-solutions.com (post-launch).
Yes. Same engine, same API, same schema in all three modes. Move from hosted to Supabase plugin: export your merged user table, push it to your Supabase, switch the API endpoint. Move from Supabase to self-host: change the DATABASE_URL the binary points at. Your config (identifier priorities, merge rules) is a portable JSON file you carry over. No vendor lock-in across modes.
Core merge engine is functional and the admin console is working — the screenshots in the section above are from a live instance. We're polishing the OSS package (multi-platform binary, install script, documentation, AGPL v3 license headers) for public release in Q3 2026. Reserve a spot above to get the binary first when it ships.
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. Reserve a spot above and I'll reach out personally.