Clerk vs Descope.
Last verified 2026-10-05
When Clerk wins
- Clerk has auth: passwordless only flows; Descope does partially
When Descope wins
- Descope has enterprise federation breadth; Clerk does partially
- Descope has MCP support for AI agents; Clerk does partially
- Descope has ISO 27001; Clerk does not
- Descope has HIPAA; Clerk does partially
- Descope has auth: push mfa; Clerk does not
- Descope has adaptive MFA; Clerk does partially
Both win
- Both support WebAuthn passkeys natively
- Both support social login at scale
- Both have SOC 2 Type II
Pricing comparison
| MAU band | Clerk | Descope |
|---|---|---|
| 10,000 MAU | $25/mo | $99/mo |
| 100,000 MAU | $800/mo | $850/mo |
| 500,000 MAU | $2,800/mo | $3,000/mo |
| 1,000,000 MAU | $5,500/mo | $5,800/mo |
Developer experience & lock-in
Editorial 1–5 scores and migration effort, on the same axes for both. Lower migration effort is better (easier to adopt, less lock-in).
| Signal | Clerk | Descope |
|---|---|---|
| DX overallDeveloper experience | 5/5 | 5/5 |
| Docs qualityDocumentation | 5/5✓ | 4/5 |
| Passkey orchestrationPasskey / WebAuthn depth | 4/5✓ | 3/5 |
| Adoption effortMigrating in | Easy | Easy |
| Lock-in (exit effort)Migrating out | Moderate | Moderate |
Enterprise readiness
Computed across the enterprise pillars from the capability matrix. See the enterprise-ready pillars.
| Pillar | Clerk | Descope |
|---|---|---|
| Overall | Enterprise-ready · 81 | Enterprise-ready · 100 |
| Enterprise SSO | 85 | 100✓ |
| Directory sync (SCIM) | 100 | 100 |
| Organizations & tenancy | 100 | 100 |
| RBAC & custom roles | 60 | 100✓ |
| Audit logs & streaming | 80 | 100✓ |
| Compliance certifications | 60 | 100✓ |
| Security posture | 85 | 100✓ |
Side-by-side capability matrix
| Capability | Clerk | Descope |
|---|---|---|
| Password authentication | ✓ Yes | ✓ Yes |
| Social login | ✓ Yes | ✓ Yes |
| Magic links | ✓ Yes | ✓ Yes |
| SMS OTP | ✓ Yes | ✓ Yes |
| Email OTP | ✓ Yes | ✓ Yes |
| TOTP (authenticator app) | ✓ Yes | ✓ Yes |
| Push MFA | ✕ No | ✓ Yes |
| WebAuthn / passkeys | ✓ Yes | ✓ Yes |
| Biometric | ✓ Yes | ✓ Yes |
| Hardware security keys | ✓ Yes | ✓ Yes |
| SAML SSO | ✓ Yes | ✓ Yes |
| OIDC SSO | ✓ Yes | ✓ Yes |
| OAuth 2.0 SSO | ✓ Yes | ✓ Yes |
| Enterprise federation | ~ Partial | ✓ Yes |
| Passwordless-only flows | ✓ Yes | ~ Partial |
| Adaptive MFA | ~ Partial | ✓ Yes |
| Step-up auth | ✓ Yes | ✓ Yes |
| Capability | Clerk | Descope |
|---|---|---|
| RBAC | ✓ Yes | ✓ Yes |
| ABAC | ✕ No | ✓ Yes |
| ReBAC | ✕ No | ~ Partial |
| FGA engine | ✕ No | ~ Partial |
| API authorization | ✓ Yes | ✓ Yes |
| Fine-grained permissions | ~ Partial | ✓ Yes |
| Capability | Clerk | Descope |
|---|---|---|
| Self-service registration | ✓ Yes | ✓ Yes |
| Progressive profiling | ✓ Yes | ✓ Yes |
| Self-service account | ✓ Yes | ✓ Yes |
| Bulk user import | ✓ Yes | ✓ Yes |
| Admin user search | ✓ Yes | ✓ Yes |
| Custom user metadata | ✓ Yes | ✓ Yes |
| Organizations / tenants | ✓ Yes | ✓ Yes |
| Multi-tenancy | ✓ Yes | ✓ Yes |
| SCIM provisioning | ✓ Yes | ✓ Yes |
| Capability | Clerk | Descope |
|---|---|---|
| REST API | ✓ Yes | ✓ Yes |
| GraphQL API | ✕ No | ✕ No |
| SDKs | 9 listed | 14 listed |
| CLI | ✓ Yes | ✓ Yes |
| Terraform provider | ✕ No | ✓ Yes |
| Local emulator | ✕ No | ✕ No |
| Extension model | Webhooks + JWT templates | Flows (no-code visual editor) + Connectors |
| Capability | Clerk | Descope |
|---|---|---|
| Bot detection | ✓ Yes | ✓ Yes |
| Breached password detection | ✓ Yes | ✓ Yes |
| Brute-force protection | ✓ Yes | ✓ Yes |
| Anomaly detection | ~ Partial | ✓ Yes |
| Log streams | ~ Partial | ✓ Yes |
| Audit logs | ✓ Yes | ✓ Yes |
| GDPR data export | ✓ Yes | ✓ Yes |
| PII minimization | ~ Partial | ~ Partial |
| Post-quantum roadmap | ✕ No | ✕ No |
| Capability | Clerk | Descope |
|---|---|---|
| MCP support | ~ Partial | ✓ Yes |
| OAuth 2.1 | ✓ Yes | ✓ Yes |
| Dynamic client registration | ✕ No | ✓ Yes |
| Agent vs human token separation | ✕ No | ~ Partial |
| Web Bot Auth | ✕ No | ✕ No |
| Capability | Clerk | Descope |
|---|---|---|
| SOC 2 Type II | ✓ Yes | ✓ Yes |
| ISO 27001 | ✕ No | ✓ Yes |
| ISO 27018 | ✕ No | ✕ No |
| HIPAA | ~ Partial | ✓ Yes |
| PCI DSS | ✕ No | ✕ No |
| GDPR | ✓ Yes | ✓ Yes |
| CCPA | ✓ Yes | ✓ Yes |
| FedRAMP | ✕ No | ✕ No |
| EU data residency | ✓ Yes | ✓ Yes |
| Capability | Clerk | Descope |
|---|---|---|
| Consent management | ✕ No | ~ Partial |
| Preference center | ~ Partial | ~ Partial |
| Purpose-specific consent | ✕ No | ~ Partial |
| Integrates with CMPs | n/a | n/a |
| Capability | Clerk | Descope |
|---|---|---|
| Multi-region deployment | ~ Partial | ~ Partial |
| Data residency control | ~ Partial | ~ Partial |
| Proven at high scale (1M+ MAU) | ~ Partial | ~ Partial |
| Capability | Clerk | Descope |
|---|---|---|
| Password-hash import | ✓ Yes | ✓ Yes |
| Lazy / just-in-time migration | ~ Partial | ~ Partial |
| Account linking & dedup | ✓ Yes | ✓ Yes |
| Custom domains per brand | ~ Partial | ~ Partial |
| Per-brand theming of all flows | ~ Partial | ~ Partial |
| Per-brand consent partitioning | ✕ No | ✕ No |
| Deletion webhooks / cascade | ~ Partial | ~ Partial |
| Event streaming / webhooks | ~ Partial | ~ Partial |
| Documented rate limits | ~ Partial | ~ Partial |
FAQ
- How does Clerk compare to Descope on pricing?
- Clerk prices on tiered-mau; Descope prices on tiered-mau. See the pricing comparison table on this page for our editorial estimates at 10k / 100k / 500k / 1M MAU using the standard methodology assumptions.
- Should I switch from Clerk to Descope?
- Switching is a 60–90 day exercise in either direction once SDK rewrites and hooks/Actions migration are accounted for. If your team is hitting cost or feature ceilings on Clerk, evaluate Descope on the specific axes flagged in the "When Descope wins" list. If you're operating well within Clerk, the switching cost rarely pays back.
- Do Clerk and Descope both support passkeys?
- Both Clerk and Descope support WebAuthn passkeys natively per public documentation. Adoption rates depend on orchestration quality (device-aware prompting, conditional UI), not raw protocol support, see the passwordless guide for the orchestration question.
This comparison is auto-generated from the underlying capability matrix and pricing data on each vendor's profile. Editorial verdict lists below are seeded heuristically from the matrix diff; a maintainer review refines them before the page goes public.