Start with the problem you actually have.
IdRa does one job, access, in several situations. Here’s how it fits each one.
Moving off Okta
Keep your standards-based apps and much of your scripting, and move at your own pace.
- An Okta-compatible API under /api/v1
- Federation with Okta while you switch
- A published list of what isn’t there yet
Your first identity provider
Get SSO, MFA and a directory in place without a per-seat bill, before a security questionnaire forces the issue.
- Self-serve signup and a setup wizard
- Passkeys and required MFA for admins from day one
- Reports and a System Log your auditors can read
Identity on your own infrastructure
Run identity where your data rules require it. IdRa is one process and one Postgres. Available once the repository is public.
- Builds into a single container image
- Secrets encrypted at rest with your key
- No dependency on IdRa’s hosted service
Hosting identity for your customers
Give every customer organization its own database, address and branding from one deployment.
- A database per tenant, enforced by Postgres
- Custom domains with DNS verification
- A platform console for tenants and limits
Giving partners access
Let contractors and partner companies in without creating and tracking their accounts yourself.
- A partner portal with its own admins
- Bring-your-own identity provider
- Scoped, expiring access
Tightening what you already have
Use IdRa alongside your current stack to find risky accounts across SaaS and cloud.
- Posture connectors for nine vendors
- Universal Logout and risk rules
- Shared Signals with the rest of your tools
Create your organization.
Pick an address and confirm your email, then sign in as its first admin. A setup wizard takes you through the rest.