Bluesky Acquires AT Protocol Trademark to Safeguard the Open‑Source Ecosystem

Bluesky Acquires AT Protocol Trademark to Safeguard the Open‑Source Ecosystem

Bluesky Secures the AT Protocol Trademark to Protect the Ecosystem

Bluesky PBC has purchased the U.S. trademark for “ATPROTOCOL” and its variants, preventing a third‑party from threatening legal action and allowing the atproto community to use the name freely. This defensive acquisition ensures that developers can continue building open‑source tools without the risk of a trademark dispute.

Why the Trademark Matters for an Open‑Source Protocol

Owning the trademark lets Bluesky enforce the mark against bad actors while keeping it free for everyday use. In the United States, a trademark holder must actively defend the mark or risk losing it to another party. By acquiring the rights, Bluesky can block anyone who tries to claim the name for unrelated or malicious purposes, thereby safeguarding the protocol’s brand integrity.

"Our crack legal team tells me if you don’t enforce your mark, then anyone can come along and claim it." – Bluesky legal team, AT Protocol trademark announcement

What the New Policy Allows and Restricts

Use case License required? Conditions
Mentioning AT Protocol in documentation, blog posts, or open‑source package names (e.g., atproto-feed-tool) No Be accurate, do not imply official endorsement, keep your own brand at least as prominent as the mark.
Branding a product, company, or service as "AT Protocol" or using the official logo Yes Must obtain a license, use the mark in good faith, and avoid impersonation or scams.
Paid or sponsored events, merchandise, domain names that suggest official status Yes License required; the trademark owner may grant permission if the use aligns with the protocol’s ecosystem.
Internal references or non‑public discussions No No formal license needed.

The full terms are detailed in the AT Protocol Trademark Policy. Good‑faith use is defined in section 8 of the policy and essentially means that the user is building compatible software or services without attempting to mislead others about official affiliation.

No Licensing Fees for the Community

Bluesky has explicitly stated that it will not charge licensing fees for ordinary developers. Fees would only be considered for commercial enterprises that wish to incorporate the trademark into their branding or product offerings for profit.

"Discussions about licensing fees will only arise if a commercial enterprise wants to use the mark (for profit) as part of its branding or product offerings." – AT Protocol trademark FAQ

Future Governance Plans

Bluesky acquired the trademark using its public‑benefit corporation resources for speed and practicality. The organization plans to transfer ownership to an independent governance body once such an entity is established, ensuring long‑term stewardship that aligns with the decentralized ethos of the protocol.

"We plan to transfer that ownership to an appropriate, independent protocol governance organization in the future." – AT Protocol trademark announcement

Community Reactions on Hacker News

  • Positive endorsement: A CEO of an independent AT Protocol implementation (Blacksky) confirmed they have received a license and are actively building services, emphasizing that commercial use is viable under the new policy.

    "We also received a license from Bluesky for the atproto trademark. There are no qualms in the ecosystem from people making money, getting users, and providing new experiences about this." – @rudyfraser

  • Clarification of intent: Commenters noted that the policy is designed to be simple and that most developers will not need a license.

    "The policy around usage is shared in the rest of the post but the goal is to make this very simple for everyone." – @pfraze

  • Skepticism about centralization: Some expressed concern that a single for‑profit entity controlling the trademark could lead to vendor‑lock‑in, drawing parallels to other centralized standards.

    "Single vendor owned & controlled standards always turn out badly, just a question when." – @eqvinox

  • Supportive sentiment: Several users simply welcomed the move, noting that it removes a legal threat.

    "Thank god!" – @bbor

How to Obtain a License If Needed

Developers or organizations that believe their use falls under the licensed category should:

  1. Review the trademark policy.
  2. Contact the trademark team at trademarks@atproto.com with a brief description of the intended use.
  3. Await confirmation; no public disclosure of the license is required.

Comparison with Other Open‑Source Projects

Bluesky’s approach mirrors trademark strategies used by Wikimedia, Red Hat, Rust, Python Foundation, Apache, Mozilla, Linux, and Debian. These projects also hold trademarks to protect their names while offering free usage for non‑commercial, descriptive purposes.

Takeaway: By acquiring and defensively managing the AT Protocol trademark, Bluesky removes a legal obstacle, enables open‑source developers to use the name without fear, and sets a clear path for future independent governance.

References

Sources