Bluesky Acquires 'ATPROTOCOL' Trademark to Protect Devs
16 Jul 2026
Bluesky has acquired the trademark rights to "ATPROTOCOL" and its variants—including "AT Protocol" and "atproto"—in a move the company says is meant to keep the underlying protocol open rather than lock it down.
What happened
According to the report, another company had been threatening legal action over use of the AT Protocol name—a threat that could have restricted Bluesky and other developers from freely using the term. In response, Bluesky moved to acquire the trademark itself.
Bluesky says it will not charge for everyday, non-commercial use of atproto. Licenses will instead be required for what the company classifies as brand-like uses: product, company, or service names built around AT Protocol; paid or sponsored events; merchandise; registered domain names; and official-sounding certifications.
Notably, Bluesky has stated it plans to eventually transfer ownership of the trademark to an independent protocol governance organization—though no timeline for that handoff has been provided.
Why the move
Bluesky's stated rationale is defensive: trademarks that go unenforced can be claimed by anyone. By securing "ATPROTOCOL" now, the company argues it's preventing a scenario where a third party could restrict how the wider ecosystem uses the protocol's name.
What's still unclear
Several details remain unspecified in Bluesky's announcement:
- The identity of the company that threatened legal action has not been disclosed.
- There's no timeline for when trademark control will move to an independent governance body.
- The specific licensing fee structure for brand-related uses hasn't been detailed.
- It isn't yet clear how "everyday use" will be distinguished from licensable "brand use" in practice—an ambiguity that could matter a great deal to developers building products, tools, or services on top of the protocol.
Why founders should care
For startups and developers building on AT Protocol, this news carries mixed signals. It's likely that simple, non-commercial use of the protocol will remain free and unaffected—Bluesky has been explicit on that point. However, founders who are naming products, companies, or services around AT Protocol, planning sponsored events, selling merchandise, or registering domains tied to the protocol's name should probably assume they may need a license, though exact terms and pricing are not yet public.
There's also a reasonable chance that the current arrangement—trademark held directly by Bluesky—is temporary. If ownership does transfer to an independent governance organization as promised, it could shift AT Protocol toward a more decentralized, community-trusted model, which may reduce long-term concerns about one company controlling the ecosystem's branding. Until that happens, though, some builders may view centralized control of the trademark as a risk worth watching, especially given the lack of a firm transfer timeline.
Bottom line
Bluesky's trademark acquisition appears designed to close a legal vulnerability before another company could exploit it—but it also introduces new questions about enforcement, licensing boundaries, and governance timing. Founders active in the AT Protocol ecosystem should treat the current licensing categories as provisional and keep an eye on how "everyday use" gets defined in practice, since that distinction could directly affect branding and product decisions.