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?
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.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazing Product and Service
What do you like best about the product?
I love that it works with okta. It automatically removes access to termed employees, and with password, rotation turned on, account passwords are changed automatically for added security. I love the amazing team, everyone on Cerby is amazing, I cannot say enough great things about the team. They are very hands-on and eager to listen, adapt and constantly improve the platform.
What do you dislike about the product?
I do not have anything I dislike about Cerby. Maybe having a feature that can automatically capture new logins and update them within the Cerby portal might be helpful
What problems is the product solving and how is that benefiting you?
Access management of 3rd party platforms. With Cerby, we can better manage who has access to non-centrally managed platforms, by putting controls that ensure only authorized users have access to these platforms.
cerby review
What do you like best about the product?
Its part of my Okta dashboard. With cerby it's easy to share with coworkers.
What do you dislike about the product?
it requires signing into okta in order for to chrome app to work.
What problems is the product solving and how is that benefiting you?
able to separate from personal password saver. Able to get access to password after the user has left employeement.
Very intuitive, make the signing in process smooth
What do you like best about the product?
Clean UI, easy to understand, robust all
What do you dislike about the product?
the testing environment only, couldn't get the full collaborative experience
What problems is the product solving and how is that benefiting you?
easiness to have password secured for easy login
good but not essential
What do you like best about the product?
having my passwords in one place sometimes gets me out of a hurry to be faster but logging into cerby to register each time makes the process more difficult and I wish it was more intuitive.
What do you dislike about the product?
every time I have to enter my password in cerby as it is not permanent and I have to do it every day every time I log in or sometimes several times which makes it a bit annoying in my perception.
What problems is the product solving and how is that benefiting you?
I am supposed to have all my passwords centralized in one place so I don't have to struggle to access different platforms without the need to capture passwords and also manage with other people or work team in case I need it.
I think Cerby is a good option to have an easy conection to platforms of your daily work
What do you like best about the product?
easy access with google chrome extension, use the same user different people
What do you dislike about the product?
sometimes my cerby session is closed several times in the same day
What problems is the product solving and how is that benefiting you?
easy access, and have two-step verifications are faster
Excellent and easy to use
What do you like best about the product?
Makes it incredibly easy to share login information across teams, even on mobile. It would be extremely frustrating to have to share passwords and sign in multiple times, and this makes it easier to do what you need to do.
What do you dislike about the product?
Honestly there's not much to dislike. It's easy to use and doesn't require a steep learning curve or significant instruction. Maybe making it a bit more clear on how to copy authentication codes.
What problems is the product solving and how is that benefiting you?
Sharing social logins across multiple team members could have been an incredibly frustrating process. Cerby makes it a lot easier to get people logged in and sharing content.
Good experience and it makes your work easier
What do you like best about the product?
The security it offers you for access in a work team, quality of dynamism, and one of the best options for organizing access and work platforms.
What do you dislike about the product?
At the moment, it helps us a lot at work, it can improve the interface, make the inbox panel more visible, it can improve the login process to the dashboard to make it more agile.
What problems is the product solving and how is that benefiting you?
Centralize access to different platforms we use daily, providing the necessary security and making you more productive. Additionally, it securely stores passwords privately.
An all-in-one solution for managing social media accounts credentials
What do you like best about the product?
Cerby allows creators, publishers and businesses to manage multiple social media accounts credentials from a single dashboard and ease common problems like having to create multiple phone numbers, email addresses and 2FA.
What do you dislike about the product?
I would love to create and onboard accounts from the Cerby interface as opposed to having to go to the Social Media Platforms themselves. Additionally, to change basic account details from there instead of having to manually log in like changing the header, name, description, email, etc. I'm curious if this is something that could be done via the API or create a bot that logins into the account and do the changes.
What problems is the product solving and how is that benefiting you?
Before Cerby, we had to create new email addresses for every account, borrow phone numbers from coworkers and issues storing/sharing 2FAs/passwords with team members!
Organization and better use of passwords
What do you like best about the product?
Handling with the equipment is much better, avoiding accidents with passwords and improper access.
I like that it links to corporate email, which makes it easier and safer to access.
What do you dislike about the product?
More detailed documentation of its use is needed.
The team often has issues with the interface but nothing to be alarmed about. The interface of the platform could improve.
What problems is the product solving and how is that benefiting you?
It prevents improper access, which prevents us from any existing vulnerability. Controlling passwords is a good way to stay organized. I think that is the main situation.
