Keyring turns product sign-ups into CRM contacts on your own Postgres and lets coding agents search, tag and merge them over MCP, with no seat fees.
Yes, Keyring (Unkey's MIT self-hosted CRM with an MCP server for agents) is open source under the MIT license.
Free (MIT), no per-seat pricing. You pay for hosting, Postgres and optional context.dev enrichment credits (daily cap; context.dev pricing not verified). (free).
Yes, Keyring (Unkey's MIT self-hosted CRM with an MCP server for agents) can be self-hosted (the source is available under the MIT license).
**Keyring** (unkeyed/keyring) is an **MIT-licensed** self-hosted CRM published by **Unkey**. It is built around product sign-ups: webhooks from Clerk, WorkOS AuthKit, Better Auth, Supabase Auth, Auth0 or Stytch, or a plain POST /v1/signups, become contact records. Optional enrichment through context.dev adds title, company, size and industry, and never overwrites a field a person has edited.
Agents get an **MCP server at /mcp** with OAuth browser sign-in, so there is no key to paste. From there an agent can search, update, tag and merge contacts, add notes, read the timeline and queue enrichment. A REST API uses scoped keys that can be read-only and can expire. It runs as one Go container plus your own Postgres (Docker Compose locally, Unkey or any container host in production), with passkey sign-in and secrets encrypted at rest (vendor claims).
Product-led teams often pay per seat for a CRM whose main job is holding sign-ups. Keyring keeps that list on your own database and gives agents a scoped, revocable door into it. Treat it as an experiment for now: it is two days old.