How can small bootstrapped startups fight copyright infringement by big companies?

the missing fourth move: ship the conversation publicly the moment you spot the copy. not after the legal letter, not after consulting advisors. within 24 hours.

big companies count on the time gap between "founder notices" and "founder is ready to make noise." that's the window where the story dies internally and never reaches the audience that would care.

watched this happen to a friend last year. waited 3 weeks to "do it right." by the time he posted, the narrative had shifted to "why didn't you say something sooner?" and his moment was gone.

real leverage for small startups isn't legal. it's distribution timing. you have 24-48 hours to make the story permanent. after that the algorithm forgets and the copy just becomes a competitor with better SEO.

This is actually much more common than people think. Even last week there was a really close person who had a legal issue on X.

Honestly, there is no universally “right” way to react. Legal threats are often sent mainly to intimidate the smaller company, even when the sender may not have a particularly strong case. This situation appears to be different, but I would still advise founders to preserve as much evidence as possible before contacting the other side and before they have the opportunity to change their repository or product.

Take screenshots, archive the relevant pages and repositories. Also record the product in use if necessary, document the timeline, and speak with a lawyer immediately. Both the US and Europe have procedures that can help when protected material has been copied. But litigation is generally a very slow and expensive process, especially for a bootstrapped startup.

One slightly positive side effect is that situations like this can create a lot of visibility. Papermark has already received significant attention on X and coverage from the media. Of course, that has nothing to do with the legal merits of the case. But if you are already forced into such a situation, it makes sense to communicate it carefully and try to extract at least some reputational or business value from the attention.

Worth checking the license before anyone reaches for the legal playbook (and usual disclaimer, not a lawyer). Papermark is AGPL-3.0, which changes the whole thing.

AGPL doesn't forbid copying. Anyone can take the code and modify it. What it requires is share-alike: run a modified version as a hosted product and you have to release your own full source under AGPL too. So the question isn't whether Corgi copied it, that's allowed, it's whether they complied. If they took it and they're running a closed-source SaaS on top, that's the breach, and breaking AGPL terminates the license. No license, and you're back to plain copyright infringement.

That's a better spot for the smaller side than it sounds, because the ask is clean and public: open-source your whole product or stop using ours. None of the murky "did they copy the look and feel" stuff that usually goes nowhere.

There's also backup here a bootstrapped team wouldn't normally have. The Software Freedom Conservancy and the FSF actually enforce GPL and AGPL, and developers get loud about violations. "They're running our AGPL code closed-source" is a sharper story than "big company copied us," and it reaches the people who'd care. A DMCA still works as the fast lever too, since the moment the license is broken their copy is unlicensed.

Only caveat: this needs them to have actually used the AGPL code and not complied. If they reimplemented it clean-room or just took the idea, AGPL and copyright probably can't reach them, and it's back to the evidence-and-narrative game everyone above described.

@busmark_w_nika I’d probably handle it on two tracks at once: quietly preserve every piece of evidence, but also make the story clear enough for the community to understand what happened. Small startups usually can’t outspend a big company legally, but they can move faster on trust, transparency, and public credibility. The worst move is waiting too long and letting the copied version become the default story.

Great question @busmark_w_nika and while I don't have anything to really contribute to the topic, it's good to be aware that such things can happen. Thanks for raising the awareness!

I definitely worried about this when my project was completed. This is what I have done and hopefully it might help someone. File for a patent as soon as possible. It takes a long time (18 months wait period) but that's the only weapon you have to fight Big Tech from stealing from your invention.

It’s not easy, and unfortunately, it’s becoming increasingly common. Financial clout remains the main issue; large companies have the resources to defend themselves, whereas for a startup, protecting one's work is difficult—not least because it costs money that is often better spent elsewhere, such as on raising awareness of the product.

That said, in theory, if all commits, pull requests, and so on are made in a Git repository, you should be able to prove your code predates the copied version. However, even then, it isn't hard to have an AI agent rewrite existing code so that it differs from the original source while retaining the same functionality.

This ties into the issue with major LLMs, which didn't hesitate to train their models on everything they could find across the internet—or even the darknet—regardless of intellectual property rights.

Ultimately, I feel luck plays a part. If a startup’s product succeeds, generates buzz, and gains visibility, there isn't much to worry about. On the other hand, if someone creates something innovative, functional, and interesting but struggles to get it off the ground, the risk is that a large corporation will swoop in and—armed with the necessary resources—make it a success for themselves.

That is clearly a concern for any creator. I’m preparing to launch a solution in September, and that is exactly what I’m worried about: messing up the launch and inadvertently giving ideas to market leaders.

This is honestly one of the scarier parts of building something small.

I’ve been thinking about this a lot with my own product too. There’s a proprietary method behind it, and in an ideal world I’d love to protect it properly. Patent it, lock the IP, do everything “by the book”.

But in reality patents are expensive. Legal work is expensive. And when you’re bootstrapping, that same money is also your product runway, your design budget, your user research, your next release.

So you end up in this strange place where you know you should protect what you’re building, but protecting it too early can also slow you down.

For now, I think the most realistic defense for small founders is a mix of things: document everything, keep clean version history, make sure authorship is visible, build in public where it makes sense, and create enough trust around the founder/product that copying you doesn’t look harmless.

Because having legal rights is one thing. Being able to afford enforcing them is another.