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?
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.
It´s easy and fast to login to different platforms
What do you like best about the product?
You can log in easier and faster to different platforms using Cerby than if you log in individually, the share inbox is really usefull, Cerby helps me reduce work time
What do you dislike about the product?
Sometimes Cerby takes you out of the session of the platform that you are using or takes a lot of time to attempt login, or sometimes you can´t access to some platforms both on pc and on the app
What problems is the product solving and how is that benefiting you?
It helps me to share account of different platforms with my team, it helps us to reduce the creations of new accounts and users of the different connected platforms
Cerby Has Made Social Media Producing Easier
What do you like best about the product?
All of our accounts are in one place, which enables ease of access. Our passwords are stored and rotated to ensure safety so we never have to worry about someone outside of our organization gaining access. I like the control that Cerby offers.
What do you dislike about the product?
I have issues with the 2FA system set up. I wish the process was uniform throughout the apps. Additionally, there's only a limited about of applications that Cerby recognizes and if more websites and applications were recognized, it would make the uniform appearance and storage of all of our accounts that much easier.
What problems is the product solving and how is that benefiting you?
As the only Social Media Video Producer for my team, the best thing that Cerby does for me is to remove 2FA issues. I no longer have to wait by my phone to give access codes to 50 different people each day - they have the ability to safely login themselves.
Sometimes bumpy but extremely helpful
What do you like best about the product?
Not having to worry about passwords and account security anymore - especially with keeping a log on used emails and phone numbers
What do you dislike about the product?
Not being able to share accounts via mobile app.
What problems is the product solving and how is that benefiting you?
We don't have to watch out for who has what account access anymore and don't have to have a team member for every 2FA method/phone number anymore
The security capabilities and offerings of the platform are great - overall solid product.
What do you like best about the product?
The fact that all ad accoutns for all platforms live in one place. Moreover, the fact that in this one platform (Cerby), we can take control over the security of these accounts, something that is a challenge as a big organization give.
What do you dislike about the product?
Having to ensure that everything we own in all business managers is in Cerby and easily accessible. Ad accounts only account for some of the assets we own - businesses own Pixels and Pages as well, need to ensure these are also a smooth oboarding as business managers.
What problems is the product solving and how is that benefiting you?
Ad account security and ownership as this is our biggest challenge since we are a business with a great amount of brands and a large team. Being able to centralize this within Cerby is great!
Remarkable Product
What do you like best about the product?
Being able to log into all of our company accounts in one place is incredibly helpful and efficient.
What do you dislike about the product?
I wish they had a version that worked on mobile because right now you have to have a browser extension that doesn't work on phones.
What problems is the product solving and how is that benefiting you?
Allowing our entire organization to log into multiple accounts without password sharing.
Great Trick For Companies
What do you like best about the product?
I love that it is easy to log into any account our company has!
What do you dislike about the product?
I don't really see a downside. The site is quick and easy to naviagte.
What problems is the product solving and how is that benefiting you?
Our company has many people and many accounts to log into. We are all able to get into needed accounts easily.
