Did a YC startup copy a source-available project's code?

The founder of an open-source DocSend alternative accused a YC S24 company of copying their commercially licensed code, sparking a debate on X about IP ethics in the 'move fast' era.

Where it happened

The accusation was first made public on June 24, 2026, in a thread on X by Nico Laqua, founder of the open-source project Papermark. The post, which included side-by-side screenshot comparisons, was then amplified on platforms like Reddit's /r/SaaS, where a community of founders and developers discussed the implications. The accused company, Corgi Insurance (YC S24), had just launched a new free data room product. As of this writing, Corgi Insurance has not publicly responded to the allegations.

Side A: This is a clear violation of a commercial license

Nico Laqua (@nico_laqua), the primary proponent of this view, argues that Corgi Insurance's new 'DataRoom' product is a direct copy of Papermark's Enterprise Edition (EE). The evidence presented consists of screenshots showing nearly identical user interfaces, layouts, and even verbatim copy. Papermark is developed in the open, but its EE features are distributed under a commercial license that explicitly forbids unpaid commercial use. The license is designed to support the project's development by having companies pay for advanced features while keeping the core transparent.

Proponents of this side argue this is not a case of inspiration but of infringement. They contend that Corgi Insurance, a well-funded YC company, leveraged Papermark's work to quickly launch a competitive product as a marketing tool without attribution or compensation. This behavior, they claim, undermines the sustainability of commercial open-source projects and disrespects the intellectual property of smaller developers.

Side B: This is convergent design in a solved product category

A steelman defense for Corgi Insurance, in the absence of a public statement, rests on the principles of rapid development and market standards. The argument is that data room software is a mature category with established UI/UX patterns. Any new entrant would likely arrive at a similar design through independent discovery of best practices. The visual similarities could be a case of 'convergent evolution' rather than direct copying. Startups, especially those in accelerators like YC, are pressured to ship products quickly, often building features that are commoditized.

This perspective suggests that the Corgi team may have viewed Papermark as a reference for a standard feature set, rebuilding it from scratch with their own code. The identical marketing copy could be an oversight by a junior team member using placeholder text. While potentially careless, this view frames the action as a mistake born of speed, not malicious theft. The core of this argument is that functional UI layouts are not protectable IP in the same way as patented inventions or specific codebases.

What's underneath

This dispute highlights a persistent and growing confusion in the software world between 'open source' and 'source-available'. Many developers see a public GitHub repository and assume the code is free to use under a permissive license like MIT. However, many modern open-source companies use licenses that make the code visible for audit and transparency but restrict commercial use to paying customers. Papermark's EE license is one such example. The conflict is a predictable outcome of the growing confusion between truly open source software and commercially restricted source-available projects. One side sees a clear license violation, while the other may have operated under the mistaken assumption that public code is fair game for inspiration or replication.

The investor read

This incident signals a rising operational risk for fast-moving startups. The line between 'inspiration' and IP infringement is becoming a key due diligence checkpoint, especially concerning source-available licenses (e.g., BSL, SSPL). A 'move fast' culture that overlooks licensing details can create significant legal and reputational liabilities overnight. For investors, this highlights the need to scrutinize a portfolio company's code provenance and internal IP policies. It also signals the maturation of the commercial open-source (COSS) market, where license enforcement is becoming a more common and visible battleground.

Pull quote: “The conflict is a predictable outcome of the growing confusion between truly open source software and commercially restricted source-available projects.”