Skip to content
Prysm:ID Docs
Prysm:ID

Prysm:ID Docs

Identity, refracted. B2B multi-tenant auth with no lock-in and a native MCP server. Built in LATAM.
Start in 5 minutes Connect your agent with Claude See pricing

Three ways to read these docs

Section titled “Three ways to read these docs”

Prysm:ID serves three readers with distinct needs. Pick your path:

You're integrating Prysm:ID into your SaaS You're a developer. You want each of your customers to have their own login. Start with the Integrate guide.
You're building with an AI agent You're connecting Claude/GPT to Prysm:ID via MCP. Your agent creates workspaces, registers apps, configures IdPs.
You're an admin of a workspace You already have a workspace. You want to invite users, connect Google, brand the login.

What is Prysm:ID

Section titled “What is Prysm:ID”

A B2B multi-tenant auth platform on top of an open-source foundation. Each of your customers lives in their own dedicated instance — physical isolation, not logical. When your enterprise customer audits you, the answer is clean.

What you get:

  • Real portability. If you want to leave, you export your directory in standard format and migrate to your own infrastructure. The foundation is open source.
  • Predictable pricing. $29/month up to 100k MAU, $0.02/MAU beyond. SSO/SCIM included in Enterprise with no per-connection fees.
  • Native physical multi-tenancy. Each of your customers gets their own instance. Not “logical orgs” in a shared database.
  • Official MCP. Your AI agent can create workspaces, register apps, configure IdPs through natural language.

Read the full architecture model →

Why AI-first matters

Section titled “Why AI-first matters”

Your agent can build you auth. Or it can integrate Prysm:ID in 30 seconds and save you from maintaining it.

Any agent with your credentials can implement social login in an afternoon. What it doesn’t tell you is that it’s writing — inside your app — a mini Prysm:ID: OAuth callbacks, sessions, refresh tokens, account linking, recovery, audit logs, multi-tenant when you need it. That code is now yours: you maintain it when Google rotates a scope, when your first enterprise customer asks for SAML, when passkeys land, when audit asks for SOC2.

With Prysm:ID, that code doesn’t exist in your repo — it’s an API call. The same agent that was going to build it integrates it in 30 seconds via MCP. Same speed on day 1, zero technical debt on day 400.

Start with Claude →

Most-read

Section titled “Most-read”
Quickstart Zero to first login in 5 minutes.
Architecture model Why physical multi-tenancy, not logical.
Validate JWTs in your backend Verify tokens issued by Prysm:ID.
Custom branding Logo, colors, custom domain for the login.
Webhooks React to signups, logins, plan changes.
MCP server tools Catalog of operations available to agents.

The promise

Section titled “The promise”

Your identity layer, unlocked. Forever.

What comes in as complexity goes out as an ordered spectrum. And the foundation stays portable forever: if you want to leave, you export everything in standard format and your DNS points wherever you choose.