Hey Nico, you didn't vibe code your data room but stole it from Papermark

Original Article ↗ Hacker News Discussion ↗

A YC-backed insurance startup is accused of building its new “dataroom” product by copying the UI, text, and possibly AGPL-licensed code from Papermark, an open source DocSend alternative, while publicly claiming it was created from scratch using AI “vibe coding.” Commenters dissect whether this constitutes copyright or license infringement, how AGPL obligations work, and to what extent LLM-generated clones muddy the line between inspiration and theft. The incident also raises broader concerns about startup ethics, Y Combinator’s tolerance for copycat behavior, and the sustainability of open source when violations are common but rarely litigated.

Allegations and Context

  • An insurance startup launched a “dataroom” product that appears extremely similar to an existing open‑source/enterprise project.
  • The original project’s maintainer accuses them of copying AGPL code and UI, demands a takedown, and calls it fraud.
  • The accused company publicly claims the product was built from scratch, with “inspiration” from existing tools and no direct code copying.
  • Commenters point to screenshots showing nearly identical layouts and English text, including niche settings and warnings, and see the denial as implausible.

Open Source Licensing and AGPL

  • The original project is under AGPL:
    • Derivatives must share source, even when offered as a network service.
    • Downstream projects must also be AGPL (modulo careful separation).
  • Many argue that using AGPL code without complying is a clear license violation; some describe it as “stealing,” others stress it’s copyright infringement, not theft.
  • There is confusion between “open source” as “do anything” vs. copyleft obligations and attribution.
  • Several note that open‑source violations are increasingly common and rarely litigated, making enforcement weak.

UI, Copy, and Intellectual Property

  • Many emphasize that written copy and UI design can be copyrighted, not just source code.
  • Identical wording and nearly identical layout are seen as strong evidence of infringement, even if implementation differs.
  • Others downplay this, arguing:
    • The visual style is largely boilerplate from popular design systems.
    • Text is generic for this type of product and easily convergent.
  • There is debate over whether modest text changes would be enough to avoid infringement; no consensus.

LLMs, “Vibe Coding,” and Blurred Lines

  • Several suspect an LLM or design tool was asked to clone the original product (“make it like X”), rather than manual copy‑paste.
  • This raises questions:
    • If an LLM regurgitates licensed code or text, is the user still responsible? Most commenters think yes.
    • As LLM‑generated UIs converge, distinguishing inspiration from copying may become practically impossible.
  • Some see this as tech normalizing uncredited copying and undermining the economic basis of creative work.

Ethics, YC, and Legal Uncertainty

  • Many criticize the startup’s ethics and see this as part of a broader “move fast, ignore law” culture, including in major startup programs.
  • Others are more relaxed, seeing copying flows and copy as efficient and consumer‑neutral unless code was directly reused.
  • Several argue this kind of case “needs to go to court” to clarify how copyright and AGPL apply to AI‑assisted cloning, but note litigation would be slow, expensive, and outcome‑uncertain.