The Identity Graph:
From Chaos to Company ID
We don't sell to "developers." We sell to organizations. This is the engine that turns a stray GitHub star into a qualified account lead.
The "Anonymous" Problem
98% of developer activity happens anonymously. They read docs without logging in. They browse packages via CLI tools.
If we simply "count hits," we are flying blind. We need to resolve identity to know if that traffic is a student in a dorm or a VP at Netflix.
The 3-Layer Resolution Engine
1. The Lake (Ingestion)
We pipe every event (GitHub webhook, segment track, npm install) into a raw Postgres lake. We keep everything, even the noise.
2. The Resolver (Graph)
This is the secret sauce. A supervised OTP process runs nightly to "stitch" identities. If User A commits to Repo B which belongs to Org C, we link User A to Org C with 90% confidence.
3. The Signal (Activation)
Once an Account crosses a "Readiness Threshold" (e.g. Score > 80), we push a notification to Slack/Salesforce. This is no longer data; it's money.
Build Simulator: Identity Graph
See how we build the graph from the command line.
Ingest Raw Signals
We pull raw events from GitHub, Package Managers, and Documentation logs. At this stage, they are just noise.
