Hanko vs SlashID.
Last verified 2026-05-07
When Hanko wins
- Hanko has auth: passwords; SlashID does not
- Hanko has auth: step up auth; SlashID does partially
- Hanko has local emulator for development; SlashID does not
- Hanko has breached-password detection; SlashID does not
When SlashID wins
- SlashID has SOC 2 Type II; Hanko does partially
- SlashID has auth: sms otp; Hanko does not
- SlashID has SAML SSO; Hanko does partially
- SlashID has authz: rbac; Hanko does partially
- SlashID has B2B Organizations / multi-tenant model; Hanko does partially
- SlashID has user mgmt: multi tenancy; Hanko does partially
Both win
- Both support WebAuthn passkeys natively
- Both support social login at scale
Pricing comparison
| MAU band | Hanko | SlashID |
|---|---|---|
| 10,000 MAU | $99/mo | $49/mo |
| 100,000 MAU | $700/mo | $350/mo |
| 500,000 MAU | $2,400/mo | $1,400/mo |
| 1,000,000 MAU | $4,500/mo | $2,700/mo |
Side-by-side capability matrix
| Capability | Hanko | SlashID |
|---|---|---|
| Password authentication | ✓ Yes | ✕ No |
| Social login | ✓ Yes | ✓ Yes |
| Magic links | ✓ Yes | ✓ Yes |
| SMS OTP | ✕ No | ✓ Yes |
| Email OTP | ✓ Yes | ✓ Yes |
| TOTP (authenticator app) | ✓ Yes | ✓ Yes |
| Push MFA | ✕ No | ✕ No |
| WebAuthn / passkeys | ✓ Yes | ✓ Yes |
| Biometric | ✓ Yes | ✓ Yes |
| Hardware security keys | ✓ Yes | ✓ Yes |
| SAML SSO | ~ Partial | ✓ Yes |
| OIDC SSO | ✓ Yes | ✓ Yes |
| OAuth 2.0 SSO | ✓ Yes | ✓ Yes |
| Enterprise federation | ~ Partial | ~ Partial |
| Passwordless-only flows | ✓ Yes | ✓ Yes |
| Adaptive MFA | ✕ No | ✕ No |
| Step-up auth | ✓ Yes | ~ Partial |
| Capability | Hanko | SlashID |
|---|---|---|
| RBAC | ~ Partial | ✓ Yes |
| ABAC | ✕ No | ✕ No |
| ReBAC | ✕ No | ✕ No |
| FGA engine | ✕ No | ✕ No |
| API authorization | ✓ Yes | ✓ Yes |
| Fine-grained permissions | ✕ No | ~ Partial |
| Capability | Hanko | SlashID |
|---|---|---|
| Self-service registration | ✓ Yes | ✓ Yes |
| Progressive profiling | ~ Partial | ✕ No |
| Self-service account | ✓ Yes | ✓ Yes |
| Bulk user import | ✓ Yes | ✓ Yes |
| Admin user search | ✓ Yes | ✓ Yes |
| Custom user metadata | ✓ Yes | ✓ Yes |
| Organizations / tenants | ~ Partial | ✓ Yes |
| Multi-tenancy | ~ Partial | ✓ Yes |
| Capability | Hanko | SlashID |
|---|---|---|
| REST API | ✓ Yes | ✓ Yes |
| GraphQL API | ✕ No | ✕ No |
| SDKs | 7 listed | 6 listed |
| CLI | ✓ Yes | ✓ Yes |
| Terraform provider | ✕ No | ✕ No |
| Local emulator | ✓ Yes | ✕ No |
| Extension model | Webhooks + custom UI elements (web components) | Webhooks + custom auth flows |
| Capability | Hanko | SlashID |
|---|---|---|
| Bot detection | ✕ No | ✕ No |
| Breached password detection | ✓ Yes | ✕ No |
| Brute-force protection | ✓ Yes | ✓ Yes |
| Anomaly detection | ✕ No | ✕ No |
| Log streams | ~ Partial | ~ Partial |
| Audit logs | ✓ Yes | ✓ Yes |
| GDPR data export | ✓ Yes | ✓ Yes |
| PII minimization | ✓ Yes | ✓ Yes |
| Post-quantum roadmap | ✕ No | ✕ No |
| Capability | Hanko | SlashID |
|---|---|---|
| MCP support | ✕ No | ✕ No |
| OAuth 2.1 | ✓ Yes | ✓ Yes |
| Dynamic client registration | ✕ No | ✕ No |
| Agent vs human token separation | ✕ No | ✕ No |
| Web Bot Auth | ✕ No | ✕ No |
| Capability | Hanko | SlashID |
|---|---|---|
| SOC 2 Type II | ~ Partial | ✓ Yes |
| ISO 27001 | ✕ No | ✕ No |
| ISO 27018 | ✕ No | ✕ No |
| HIPAA | ✕ No | ✕ No |
| PCI DSS | ✕ No | ✕ No |
| GDPR | ✓ Yes | ✓ Yes |
| CCPA | ✓ Yes | ✓ Yes |
| FedRAMP | ✕ No | ✕ No |
| EU data residency | ✓ Yes | ✓ Yes |
| Capability | Hanko | SlashID |
|---|---|---|
| Consent management | ~ Partial | ✕ No |
| Preference center | ~ Partial | ✕ No |
| Purpose-specific consent | ✕ No | ✕ No |
| Integrates with CMPs | n/a | n/a |
FAQ
- How does Hanko compare to SlashID on pricing?
- Hanko prices on tiered-mau; SlashID 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 Hanko to SlashID?
- 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 Hanko, evaluate SlashID on the specific axes flagged in the "When SlashID wins" list. If you're operating well within Hanko, the switching cost rarely pays back.
- Do Hanko and SlashID both support passkeys?
- Both Hanko and SlashID 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.