Papermark Accuses Corgi of Copying Its Open-Source Data Room

On June 24, 2026, the insurance startup Corgi launched a document-sharing product called Dataroom. Within a day, the founder of Papermark, an open-source data-room project, publicly accused Corgi of copying Papermark's code. Corgi denies it. No lawsuit has been filed, and nothing has been proven.

Information current as of 2026-06-25. This is a developing story about an unproven public allegation. It presents general legal information, not legal advice, and takes no position on whether any copying occurred.

What happened

Corgi, a Y Combinator-backed insurance startup, announced a product called Dataroom on June 24, 2026 through a press release and at dataroom.corgi.com, describing it as an all-in-one platform for document sharing, e-signatures, and engagement analytics. The launch materials presented the product as the team's own build and did not mention any third-party codebase.

The next day, Marc Seitz, a co-founder of Papermark, posted publicly that Corgi had not, in his words, "vibe coded" its data room but had taken it from Papermark's open-source and enterprise-licensed code. He demanded an immediate takedown, framed the conduct as fraud rather than ordinary fast-moving product work, and tagged Y Combinator. The exchange spread quickly on Hacker News and X, drawing wide comment from other founders.

What Papermark alleges

Papermark is an open-source alternative to document-sharing tools such as DocSend, with its source code published on GitHub. Seitz alleged that Corgi's Dataroom reproduced Papermark's code rather than being independently written, and that this violated both Papermark's open-source license and its separate enterprise license. He asked Corgi to take the product down immediately.

These are allegations by Papermark. They have not been adjudicated, and in the public thread reviewed for this article Papermark pointed to visual and product similarities and the speed of the launch rather than publishing a line-by-line code comparison. Whether the underlying code was actually copied is a factual question that has not been resolved.

What Corgi says

Corgi co-founder Nico Laqua responded in the Hacker News discussion that the team "did not use any of papermark's code" and that Dataroom was "made from scratch with inspiration from existing document sharing softwares." Corgi's launch announcement did not reference Papermark or open-source software. As of this writing, Corgi has not issued a separate formal statement or a legal response, and no filing by either company has appeared in public court records.

The gap between the two accounts is the heart of the dispute. Papermark says its actual code was copied. Corgi says it took only inspiration, which in copyright terms means general ideas and design patterns rather than protected expression.

The license at the center: the AGPL

Whether or not copying occurred, the dispute turns on a specific license. Papermark's repository is dual-licensed: the core is released under the GNU Affero General Public License v3 (AGPL-3.0), and its enterprise directories sit under a separate commercial license. The AGPL is the strongest copyleft license in common use. Under section 13, if you modify the software and let users interact with it over a network, you must offer those users the corresponding source code, even if you never distribute the software as a download.

That network clause is what makes the AGPL consequential for a software-as-a-service product. A company that built a closed, commercial data room on AGPL-licensed code, without either releasing its source under the AGPL or buying a commercial license, could face exposure on two fronts at once. Courts treat open-source license conditions as enforceable through copyright (Jacobsen v. Katzer) and as enforceable contracts (Artifex v. Hancom), so the same conduct can support both an infringement claim and a breach-of-contract claim. For the underlying rules, see our explainer on whether AI-generated code is copyright infringement.

Analysis

The "vibe coded" framing is what makes this more than a routine clone fight. A recurring claim in 2026 is that a product was rapidly generated with AI coding tools, which is sometimes offered as a kind of clean-room explanation for how a small team shipped a polished product fast. The license analysis does not work that way. If an AI tool reproduces someone else's licensed code and you ship it, you are the party distributing the result, and copyright infringement is strict liability, so a lack of intent does not erase the claim. It may reduce damages, not liability.

That said, the law cuts in Corgi's favor on one important point: copyright protects expression, not ideas. Building a similar product, copying a layout concept, or taking "inspiration" from how a competitor solved a problem is generally lawful. Independent creation is a complete defense. So if Corgi genuinely wrote its own code, the visual and feature similarities Papermark points to would not, by themselves, establish infringement. A case here would likely rise or fall on a line-by-line comparison of the two codebases and on Papermark's own enforcement choices, including whether it has registered the relevant code.

There is also a reputational layer that sits outside the law. Both companies are associated with Y Combinator, and the public nature of the accusation, the appeal to YC, and the speed of the response have made this as much a community-trust story as a legal one. None of that decides the legal question, which remains unresolved.

What happens next

No suit has been filed. Papermark's options range from a formal takedown demand, to insisting on a commercial license, to litigation that enforces the AGPL through both copyright and contract. Corgi's options range from open-sourcing the product to match the AGPL, to licensing, to rewriting any disputed code, to contesting the allegation outright if it maintains the code is its own. Until someone publishes a code comparison or a complaint is filed, the central factual question stays open. This article will be updated as the dispute develops.

This is general legal information, not legal advice, and a developing news story. It describes a public dispute as of 2026-06-25 based on publicly available statements. The allegations described here are unproven, no court has ruled, and this article takes no position on whether any copying occurred. Consult a lawyer licensed in your jurisdiction for advice on open-source licensing or any specific situation.

Related articles

• Is AI-generated code copyright infringement?
• AI copyright law in the United States
• AI model licensing and open-source attribution

Last updated: 2026-06-25.

Frequently Asked Questions

Did Corgi actually steal Papermark's code?

That is unproven. Papermark's co-founder publicly alleges that Corgi copied its code; Corgi's co-founder denies using any Papermark code and says the product was built from scratch. No court has ruled and no lawsuit has been filed as of June 25, 2026.

What is the AGPL, and why does it matter here?

The GNU Affero General Public License v3 is a strong copyleft license. Under its section 13, a party that modifies the software and offers it to users over a network must make the corresponding source code available. Papermark's core is AGPL-licensed, with enterprise features under a separate commercial license.

Can you freely use open-source code in a commercial product?

Not without following the license. Open-source code is licensed copyright, not public domain. Permissive licenses require attribution, while copyleft licenses like the AGPL can require that your derivative work also be open-sourced. Copying copyleft code into a closed product without complying can be both infringement and breach.

Does building a product with AI change the legal analysis?

No. If an AI coding tool reproduces protected code and you ship it, you are the distributor and you carry the liability, because copyright infringement does not require intent. Saying a product was 'vibe coded' does not relieve the company that ships it of license obligations.