Software Engineer Intern

Rippling has partnered with Apex Fintech Solutions to launch an integrated treasury product for its 30,000-plus business customers. The collaboration will enable US entity accounts to access Apex's Money Market Fund Sweep programme through Rippling's platform, with plans to expand into additional fixed income instruments. The offering integrates Apex's cloud-native infrastructure, Apex AscendOS, into Rippling's existing system. Key features include real-time account opening, instant cash transfers, and automated cash sweeps into designated funds. Apex will handle regulatory compliance and account approval, typically within one business day. The product allows Rippling customers to manage treasury alongside payroll, benefits, and spend management in a single platform. Apex Clearing will serve as the FINRA-registered broker dealer for the service.

What does the Rippling vs. AI startup trade secret lawsuit mean for SaaS founders in 2026? Rippling faces a trade secret lawsuit from a NYC AI startup in 2026. Learn what this legal battle means for SaaS IP protection and startup risk. If you're planning to build a scalable product, choosing the right service is critical. Its expertise includes Mobile App Development, Digital Marketing, Cloud Services. Rippling is pushing back hard. After a New York-based AI startup filed a trade secret lawsuit accusing the HR and payroll platform of misappropriating proprietary technology, Rippling has publicly denied the claims and moved to counter them - turning what started as one company's legal complaint into a messy, high-stakes battle that founders in every SaaS category should be watching. What is the concept. A trade secret lawsuit alleges that one company improperly obtained or used another's confidential business information - source code, algorithms, customer data, pricing models, or internal processes - without authorization. Unlike patents, trade secrets aren't publicly registered, which means proving theft usually comes down to circumstantial evidence: hiring patterns, access logs, code similarities, and the movement of employees between competitors. In this case, the AI startup claims Rippling accessed or replicated technology it considers proprietary. Rippling's response - a public denial paired with an aggressive countering strategy rather than a quiet settlement - signals it sees the claim as either meritless or damaging enough to fight in the open, even at reputational cost. Why it matters now (2025-2026 context). Trade secret litigation between SaaS and AI companies has spiked as competition for talent, data pipelines, and proprietary models intensifies. When an engineer or executive moves from one company to a direct competitor, both sides now face immediate scrutiny: did knowledge move with them, and can it be proven? Boards and investors are increasingly asking about this exposure during due diligence, not just after a lawsuit lands. For founders, the lesson isn't about Rippling specifically - it's about how fast a reputational and financial hit can materialize even from an unproven allegation. Legal fees, discovery costs, and distracted leadership time can rival the cost of losing an actual product feature. How AI is changing this. AI has made trade secret disputes both easier to allege and harder to defend. Code similarity detection tools can flag suspicious overlaps in days instead of months, giving plaintiffs faster ammunition. At the same time, AI-assisted product development means teams increasingly build on shared open-source foundations, blurring the line between 'independently developed' and 'derived from prior knowledge' - a gray zone courts are still learning to navigate. This is the contrarian insight most founders miss: the same AI tooling that accelerates your product roadmap also accelerates your legal exposure, because it leaves a more detailed, more discoverable trail of exactly how your technology was built. Real-World examples. This dispute follows a broader pattern in the HR-tech and workforce software space, where rival platforms have repeatedly accused each other of poaching talent to gain a technical edge - including public allegations of planted employees and leaked internal systems between competing payroll platforms in the past year. These cases rarely stay private; they play out in press releases, court filings, and social media threads simultaneously, shaping public perception long before a verdict is reached. The pattern is consistent: the company that controls the narrative early - through a clear, documented, public response - tends to suffer less long-term brand damage than the one that goes quiet and lets speculation fill the gap. Practical insights / actions. Founders should treat trade secret protection as an operational discipline, not a legal afterthought. That means: documenting independent development with timestamps and version control, running exit interviews and access audits for every departing employee, and using NDAs and non-solicitation clauses that are actually enforceable in your jurisdiction rather than boilerplate templates copied from another startup's cap table. Call this the Provenance Ledger framework - maintain a running, timestamped record of who built what, when, and from which inputs, for every core piece of proprietary technology. It's the single artifact that turns a 'he said, she said' trade secret dispute into a documented timeline, and it costs almost nothing to maintain if you start early. The founder mistake here is treating this as a legal team's job; it needs to be built into engineering workflow from day one, because retrofitting it after a lawsuit is filed is nearly impossible. Future outlook. Expect trade secret litigation in SaaS and AI to keep rising through 2026 as more startups compete for the same narrow pool of technical talent and the same enterprise buyers. Companies that can demonstrate clean provenance - for code, data, and hiring - will increasingly use that as a selling point in enterprise deals and fundraising, not just a defensive posture. The hidden opportunity is that rigorous IP hygiene, done publicly, becomes a trust signal that shortens sales cycles with risk-averse enterprise buyers. Conclusion. The Rippling case is still unfolding, and the facts will be decided in court, not in headlines. But the operational lesson is available right now: trade secret exposure is a byproduct of how you hire, build, and document - not just how you litigate. Businesses serious about scaling securely should treat IP and data protection as infrastructure. RP SoftTech works with growing SaaS and AI teams to build secure development and data governance practices that hold up under exactly this kind of scrutiny - get in touch for a technology risk audit before it becomes a legal one. About RP SoftTech: RP SoftTech is a software development company helping startups and SMEs build mobile apps, web platforms, and AI automation systems. Contact RP SoftTech or explore its services. Suggested reading. trade secret lawsuit SaaS corporate espionage lawsuit AI startup IP lawsuit protecting trade secrets startups SaaS legal risk 2026 Looking to build a similar solution?

Now Rippling is counter-suing tiny startup Runlayer. This lawsuit follows one filed last month by Runlayer that accused Rippling of stealing its product ideas. It's a seller- and buyer-beware market warn HR startup Rippling filed a lawsuit Monday accusing MCP gateway startup Runlayer of infringing on three of its patents, according to the lawsuit seen by TechCrunch. The filing comes after Runlayer sued the HR startup last month, accusing it of breach of contract and stealing its product ideas. It's the latest saga between the two companies after Rippling spent nearly a year testing the startup's MCP product. The two companies never agreed on a price, and the trial never turned into a paid contract. Instead, Rippling built its own MCP server, and will soon offer it as a product that competes with Runlayer. (Rippling often turns its internally used tech into products, like its recently released AI Spend Console.) Their battle serves as a warning of how the relationship between customers and startups can devolve in this AI-powered age of fast product building. Runlayer, which launched its product about a year ago, bundles an MCP gateway with cybersecurity features like threat detection. MCP is an open standard that allows AI agents to connect with data and software systems needed to work independently. Runlayer has raised a total of $42 million and was founded by third-time founder Andrew Berman. (His previous companies were baby-monitor maker Nanit and an AI video conferencing tool Vowel, which sold to Zapier in 2024). Rippling became one of Runlayer's earliest potential customers trialing its software. The most dramatic detail in the lawsuit is Runlayer's claim that a Rippling employee reached out to Berman to warn him that his employer was building a "copy" of Runlayer's product. A Rippling spokesperson tells TechCrunch that its employee has since revised that view. On Rippling's side, perhaps the most dramatic claim is that it informed Runlayer of the patents it believed Runlayer had infringed soon after the startup filed its lawsuit. One might infer that the suit is intended as leverage to bring Runlayer to the settlement table. Indeed, that's how Runlayer views it. "This is a desperate, retaliatory ploy to distract from the fact Rippling misappropriated our proprietary technology. We clearly have a standout AI product that has nothing to do with these patents. No attempt to bully or distract will prevent us from protecting our IP and continuing to innovate and create the best product for our fast-growing customer base," Berman said in a written statement. Rippling loves a good fighting-words statement too. Its spokesperson told TechCrunch: "It takes a certain boldness to accuse a competitor of violating intellectual property laws while infringing on that competitor's inventions. But that's exactly what Runlayer has done here. Rippling's lawsuit calls out Runlayer's hypocrisy. Having manufactured claims against Rippling to distract from its business failures, it now has to face a lawsuit for repeatedly copying Rippling's inventions in building its own products." Now it's up to the courts to unwind who did what to whom, unless the parties settle. But these dueling cases still serve as a buyer- and seller-beware warning. With AI advances, enterprises have never before been more empowered to build tech in-house. Yet they still may put a startup through its paces before choosing that option.