Rippling and Deel Claims Survive Dismissal

The main takeaway is that this stopped being a short lived PR fight and became a durable operating risk for both companies. Judge Charles Breyer’s February 23, 2026 order let the core federal trade secret and RICO claims continue in California, which means the dispute now sits inside discovery, executive depositions, and trial prep rather than getting thrown out early. The allegations also map directly onto sales execution, product plans, and customer targeting, which are the nerve center of how both companies win deals.1 2 3 4

• The surviving claims matter because they go to alleged competitive theft, not a side issue. The court order recites allegations of more than 6,000 Slack searches and more than 600 accesses or downloads of Rippling’s customer list by the alleged spy, tying the case to pipeline data, battlecards, and roadmap material that could shape how a rival sells and builds product.1 2
• This sits inside a head on market collision. Rippling grew from HR and IT into global payroll and EOR, while Deel moved from contractor payments into EOR, global payroll, US payroll, talent management, and device management. The same products are increasingly sold to the same buyer, usually the finance or people team that wants one system to hire, pay, onboard, and manage access for workers everywhere.5 6 7
• The size and speed of both companies raise the stakes. Rippling was valued at $16.8B in May 2025 and reached an estimated $1.0B revenue run rate by March 2026. Deel was valued at $17.3B in October 2025 and reached an estimated $1.5B revenue run rate by June 2026. That makes the lawsuit a fight between two scaled category leaders, not a startup skirmish.6 7 8 9

From here, the case is likely to deepen the market split between bundled global workforce platforms and narrower point solutions. If Rippling and Deel keep expanding across payroll, EOR, HR, and IT while litigating over how that expansion happened, buyers will place even more weight on trust, security controls, and breadth of owned infrastructure when choosing a long term system of record.3 5 6 7