Papermark Accuses Nico Laqua of Code and License Infringement

Papermark Alleges Code Theft by Nico Laqua

Papermark has publicly accused Nico Laqua and the team at UseCorgi of infringing on copyright and licenses by allegedly stealing code from Papermark's open-source and enterprise-licensed repositories to build a data room product. The accusation, delivered via X (formerly Twitter), claims that the product was not "vibe coded" (a term referring to rapid, AI-assisted development) but was instead a direct copy of Papermark's work.

Marc Seitz of Papermark characterized the action as "fraud" rather than "moving fast and breaking things," stating that the incident reflects poorly on both the business in question and the Y Combinator community.

Dispute Over "Code" vs. "Design"

In response to the allegations, Nico Laqua stated that the data room was built from scratch with inspiration from existing document-sharing software and denied using any of Papermark's code. However, critics point to evidence suggesting a deeper level of duplication than mere inspiration.

According to community observations and screenshots shared in the dispute:

• Multiple pages of the product appear to be identical to Papermark's in both design and text.
• The verbatim nature of the copy extends to obscure pages, which observers suggest is highly unlikely to occur through independent development.

One commenter noted the discrepancy in the defense:

"The founder, Nico Laqua, basically responding with 'we didn't copy code' and not taking any responsibility says a lot about his and his company's moral code."

Legal and Licensing Implications of AGPL

The Papermark project is licensed under the AGPL (Affero General Public License). This license has specific requirements that impact how the software can be used in a commercial or networked environment:

• Source Disclosure: Users must share the source code if the software is modified and used over a network.
• Derivative Works: Any project incorporating AGPL code must also be licensed under the AGPL.

While some argue that it is impossible to "steal" open-source code if the license terms are followed, the AGPL's strict requirements regarding network interaction make compliance difficult for proprietary products unless the AGPL components are strictly isolated from the core business logic.

Community Perspectives on AI and Open Source

The incident has triggered a broader discussion regarding the intersection of LLM-generated code and open-source licensing. Several points of contention emerged from the community discussion:

• LLM Hallucinations of Code: Some argue that LLMs may generate code patterns that closely mirror existing licensed code they were trained on, potentially leading to unintentional license infringement.
• The Nature of FOSS: Some commenters argued that the purpose of Free and Open Source Software (FOSS) is to be used and modified, suggesting that the outcry over "theft" is contradictory to the spirit of open source.
• Verification: There are calls to see "agent traces" (the logs of AI agent activity) to determine if the code was truly generated by an AI or copy-pasted from a repository.