Overview

Product video
Cerby is the first and only comprehensive access management platform for nonstandard applications. Harnessing the power of identity providers, Cerby makes passwordless authentication an immediate reality for any application by extending single sign-on (SSO) and lifecycle management capabilities. Onboard, offboard, and manage users at scale, with just a few clicks.
Cerby makes it possible to securely extend access, minimize risk, and lower costs.
With Cerby, your team can:
- Go passwordless (and ditch your password manager)
- Automate offboarding
- Securely manage social media accounts
- Get SSO for any app
- Control SaaS sprawl and optimize spend
- Secure SaaS privileged accounts
- Automate 2FA for enrollment
Highlights
- Unlock the full potential of your identity and goverance programs with Cerby
- Extend your reach, not your budget
- Manage access to all your apps with no exceptions
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
Dimension | Description | Cost/12 months | Overage cost |
|---|---|---|---|
Shared Apps | Per shared credential (username and password) | $0.00 | |
Standard Apps | Per application | $0.00 | |
Premium Apps | Per application | $1.00 | |
Cerby Core | Cerby platform including EPM, Cerby SSO to Any App, Secure Credential Sharing, Secrets Management, Cerby Application Network, Web / Mobile / Browser Clients, Security Health Dashboard, Activity Logging, IdP Integration. | $1.00 | - |
Cerby EPM+ | Cerby integrations for websites / business apps not requring idLCM for shared and individual user credentials. Includes authentication automations (password rotations, MFA enforcement, session management/logout). | $1.00 | - |
Cerby IDCLM | Cerby full integrations for websites & business apps including idLCM. Includes authentication automations (password rotations, MFA enforcement, session management/logout) + idLCM integrations for User Provisioning, Entitlement Management, deprovsioning, & IGA integrations | $1.00 | - |
Cerby Secure Social | Cerby's integrations for social media platforms and accounts. | $1.00 | - |
Cerby Premium Support | Includes: Email, phone and chat support. Dedicated support channel (Slack, Teams, etc.). Proactive monitoring. Self-learning materials (documentation and videos). Customer success manager. Success planning. Security strategy reviews (Monthly). Roadmap reviews (Quarterly). | $1.00 | - |
Cerby Standard Support | Includes: Email, phone and chat support. Self-learning materials (documentation and videos). Customer success manager. Security strategy reviews (Quarterly). | $1.00 | - |
The following dimensions are not included in the contract terms, which will be charged based on your usage.
Dimension | Description | Cost/unit |
|---|---|---|
additional | Additional Usage | $0.00 |
Cerby Core Platform | EPM, SSO, Secure Sharing, App Network, IdP, and Security Analytics. | $0.00 |
Cerby IDLCM | Web/App integrations & idLCM. Includes Auth Automations & Full Identity Governance. | $0.00 |
Cerby Premium Support | Full Support & CSM, Omnichannel help, proactive monitoring, and monthly security reviews. | $0.00 |
Vendor refund policy
All fees are non-refundable and non-cancellable except as required by law.
Custom pricing options
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Resources
Vendor resources
Support
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Standard contract
Customer reviews
Identity governance has strengthened and enforces MFA and shared SaaS access controls
What is our primary use case?
Cerby is primarily used for MFA enforcement via LDP, automated JML, secure non-SAML OIDC SaaS, and Shadow SaaS governance.
For MFA enforcement, the use case involves a legacy SaaS app with SAML OIDC that is not integrated with Azure AD , where users access it via local credentials with no native MFA support. Cerby acts as an identity orchestration layer, enforcing upstream LDP MFA, blocking direct credential logins, and removing local password visibility. The outcome from Cerby includes no password sharing, compliance-ready access governance, and MFA enforcement on non-federated apps.
Additional use cases for Cerby include shared privilege access to SaaS accounts, automated deprovisioning, and Shadow IT governance.
What is most valuable?
The top features that Cerby offers are shared account session attribution and audit logs, credential brokering and vaulting, and automated JML without SCIM.
Using Cerby for shared SaaS admin accounts, access is brokered per user. No one sees the password, and each session is mapped to the individual via LDP identity with full timestamps plus activity logs. During audits or incidents, I can trace exactly who accessed what and when, eliminating accountability gaps.
The underrated feature of Cerby is its non-invasive deployment model, which requires no API dependency or app-side integration. From an infrastructure perspective, the browser-based identity orchestration allows us to extend zero trust controls to unmanaged SaaS without waiting for vendor support, which is highly valuable in fast-moving MSP environments.
Cerby has positively impacted my organization by reducing identity risk across non-federated SaaS through the enforcement of LDP-based MFA and centralized role-based access control without app changes. I have seen faster JML execution, no orphaned accounts, elimination of shared credential exposure, and improved audit readiness.
With Cerby, the JML for non-SCIM SaaS moved from manual tickets to near real-time deprovisioning. Orphaned accounts reduced by 70 to 80 percent after the enforcement of automated access revocation and centralized role-based access control sync. Audit preparation time dropped to 30 percent due to consolidated session logs and shared account attributions.
What needs improvement?
The key improvement areas for Cerby are few, but they should be addressed. I would like to see deeper API level integration wherever necessary to reduce browser dependency, stronger reporting analytics dashboards, and granular multi-tenant segregation controls for larger MSP environments.
Additional improvement areas for Cerby include providing clarity on high availability architecture, bulk lifecycle operations for large user migrations, and advanced conditional access support.
For how long have I used the solution?
I have been using Cerby for two and a half years.
What do I think about the stability of the solution?
Cerby is stable.
What do I think about the scalability of the solution?
Cerby is scalable. I have been using it for fewer customers earlier, but I am now using it for more customers as well, and the performance has not decreased even after that.
How are customer service and support?
Cerby customer support is good. Till now, there have been no issues with the response and solution provided.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I previously used CyberArk and native LDP control via Microsoft Entra ID . I switched to Cerby to cover non-SAML, SCIM SaaS where PAM vaulting did not provide true per-session attribution or automated JML. Cerby filled the identity governance gap without requiring app-side integration.
What was our ROI?
Using Cerby has delivered a measurable return on investment in identity, operational efficiency, and risk reduction. Cerby's JML ticket turnaround has dropped from 24 to 72 hours to just under 15 minutes, which is 70 to 95 percent faster processing. The risk and compliance level has lowered, with orphaned SaaS accounts reduced by 80 to 90 percent, thereby lowering security exposure and support rework. Additionally, less manual IAM ticket handling has reduced support load, enabling 0.1 to one FTE reallocations in the larger team. These metrics vary by organization size and SaaS footprint, but they demonstrate tangible operational and security values that Cerby provides.
What's my experience with pricing, setup cost, and licensing?
Cerby's pricing is competitive versus legacy PAM plus proxy tooling cost cycles with seat counts and managed apps. The setup cost is low during the initial implementation overhead, with no app-side integration required. The licensing is on a per-user, per-seat model, which aligns with enterprise IAM budgeting, making it predictable but can rise with broad SaaS coverage.
What other advice do I have?
I would advise others looking into using Cerby to first map non-federated, non-SCIM SaaS in their environment because that is where Cerby delivers maximum value. Additionally, I would suggest testing shared account governance and JML automation in a pilot phase with high-risk apps. I would rate this product an 8 out of 10.
