Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Cerby announced a $40 million Series B on May 28, 2025, led by DTCP, to expand its identity-automation platform for applications that conventional enterprise identity systems cannot readily manage. Existing investors Okta Ventures, Salesforce Ventures, Two Sigma Ventures, Ridge Ventures and Bowery Capital also participated. SecurityWeek reported that the round brought Cerby’s total funding to $72.5 million.
The announcement is a May 2025 funding event, not a newly announced financing. Cerby’s pitch is to help organizations extend existing identity controls to disconnected applications—not to replace their core identity provider. Cerby’s announcement and SecurityWeek’s report describe the round and its stated purpose.
Funding round: amount, investors and reported total
The $40 million financing was a venture Series B. DTCP led the round, with participation from existing investors Okta Ventures, Salesforce Ventures, Two Sigma Ventures, Ridge Ventures and Bowery Capital. SecurityWeek put Cerby’s post-round funding total at $72.5 million; that total is reported by the outlet, rather than stated in the company’s announcement.
Cerby said the round followed 10× annual recurring revenue growth and 5× growth in its customer base since its Series A. It also reported serving more than 100 organizations and automating workflows across more than 2,000 applications. These are company-reported figures, not independently audited metrics in the available funding coverage. Application counts also do not establish that every application has the same depth of functionality or production reliability.
What Cerby means by “disconnected applications”
A disconnected application is not necessarily offline. It is an application that an organization cannot reliably bring under its usual identity controls because it lacks, or does not adequately expose, standard integrations. Those standards and interfaces include SAML or OIDC for single sign-on (SSO), SCIM for account provisioning, and APIs for other automated tasks.
The gap can affect older on-premises software, proprietary internal systems, smaller SaaS products, nonfederated services, advertising platforms and business social-media accounts. Some vendors offer SSO or provisioning only on particular product tiers. Where an application cannot be connected through a supported standard or API, teams may resort to help-desk tickets, spreadsheets, CSV imports, custom scripts, browser procedures or shared passwords.
That creates a practical identity-security problem: disabling an employee in the company’s identity provider does not necessarily remove that person’s account or access in an application the provider cannot manage. The organization may also lack a reliable record of who has access, who approved it or whether it was revoked.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11How Cerby is intended to fit into an identity stack
Cerby positions its platform as an orchestration layer that extends an existing identity and governance stack to applications its usual connectors cannot reach. Its materials describe integrations with systems including Okta, Microsoft Entra ID, Ping Identity, SailPoint, Saviynt and Veza. In this model, the existing identity provider or governance platform remains central to employee identities, policies and approvals; Cerby attempts to execute the resulting actions in the less-integrated application. Cerby describes this approach on its platform page and in its lifecycle-management overview.
A simplified workflow might look like this:
- An employee joins, changes roles or leaves, and the event is recorded in the organization’s identity or governance system.
- An assignment, request or lifecycle event is passed to Cerby through the relevant integration or workflow.
- Cerby applies an application-specific mapping and attempts the required action—for example, creating an account, changing a role or removing access.
- The action and its outcome can be recorded for visibility and audit purposes.
Cerby says it uses application-specific mappings, an access-orchestration layer, robotic process automation and APIs where available. Its product materials cover credential management and SSO, MFA, identity lifecycle tasks such as provisioning and deprovisioning, privileged-access workflows, and centralized control of shared business social-media accounts. The precise capabilities depend on the target application and integration; a broad catalog does not mean every application supports every workflow.
This makes Cerby different in emphasis from a primary identity provider, a full identity governance and administration (IGA) suite, or a password manager. Those products may remain part of the architecture. Cerby’s stated role is to address the long tail of applications that existing controls do not manage well. The company’s product materials present the platform as an extension to existing systems, not a rip-and-replace alternative.
Rank #3
Why investors may see an opportunity
The investment thesis follows from a persistent mismatch: organizations can have established identity platforms while still depending on manual work for important applications. Extending existing infrastructure may be more practical than replacing a core identity system or building and maintaining a custom integration for each unsupported application. Manual account handling, lingering access after departures and shared credentials can also create operational, audit and security costs.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsThis is an interpretation of the market opportunity, not a complete statement of DTCP’s investment rationale. In Cerby’s announcement, DTCP described identity security as an industry due for transformation and praised the company’s platform approach. The funding indicates investor backing for the proposition; it does not independently validate the product’s coverage, performance or customer economics.
What Cerby plans to do with the money
Cerby said it would use the financing to expand its Cerby Application Network, continue developing agentic AI capabilities, improve platform extensibility and advance its product suite. It also identified go-to-market expansion in North America and Europe, the Middle East and Africa, with Germany, France, the United Kingdom and selected Middle Eastern markets among its priorities. The announcement did not specify hiring targets, acquisition plans, revenue goals or release dates.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What buyers should verify
Automation for applications without standard interfaces involves application-specific engineering and operational dependencies. A browser flow can break when a vendor changes its interface, authentication process or administrative permissions. MFA may involve time-based codes, push approvals, hardware keys or other methods; the workflow that works for one application may not work for another. Cerby’s help material discusses authenticator-app and TOTP configurations, but buyers should validate the exact MFA method and recovery path for each critical target application.
Before adopting an automation layer for identity workflows, a buyer should test the applications and actions that actually matter:
- Coverage: Does the integration support the organization’s exact application edition, tenant type and region? Which functions are available—login, provisioning, deprovisioning, role changes, access reviews, credential rotation or privileged access?
- Reliability: How are failures detected, retried and escalated? What happens after a user-interface or authentication change, and can an automation be paused safely?
- Security: Where are credentials stored? How are administrative privileges separated? How are MFA, time-limited access and credential recovery handled?
- Governance and evidence: Are requests, approvals, changes and exceptions traceable? Can action logs be exported to the organization’s audit or security systems? Does the existing identity or governance platform remain authoritative?
- Continuity and exit: What happens if the service is unavailable? What are the support commitments, recovery procedures and options for exporting configurations or moving away?
- Economics and deployment: Does a pilot reduce manual work or custom-integration maintenance enough to justify the service? What application-owner and security-team effort is required? Cerby’s reviewed product pages use a demo-led sales path and do not show public list pricing.
Shared social-media and advertising accounts merit particular care. Centralized credential handling may reduce uncontrolled password sharing, but it does not by itself resolve excessive permissions, unclear ownership, agency separation, account recovery or platform terms-of-service requirements.
Best Value
Who may benefit—and who may not
Cerby is most relevant to organizations that already have an identity provider or governance platform but still manage a meaningful set of important applications through manual workarounds. High employee turnover, difficult offboarding, shared business accounts and audit requirements can make those gaps especially consequential. A pilot should use the organization’s hardest disconnected applications and measure actual changes in provisioning time, revocation speed, manual workload and audit evidence.
It may be less compelling for smaller teams with few applications and simple access needs, or for organizations whose applications already have dependable SSO, SCIM and API-based lifecycle integrations. It is also not positioned as a substitute for buyers seeking a primary workforce identity provider or a full IGA replacement. If the target application’s automation cannot meet the organization’s reliability, security or compliance requirements, native integration or a different operational approach may be preferable.
The funding takeaway
Cerby’s Series B backs a specific proposition: extend identity automation into applications beyond the reach of conventional integrations. That addresses a recognizable enterprise problem, but funding and company-reported application counts are not proof that every integration is equally capable. For a prospective customer, the deciding evidence should be whether Cerby can reliably govern the organization’s own difficult applications, produce usable audit evidence and reduce the cost and risk of manual access management.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
