ATProto Trademark 2026: Is Bluesky's Open Protocol Still Open?

July 21, 2026 · 10 min read · Analysis · ThreadGrab

On July 14, 2026, Bluesky Social PBC filed a US trademark application for the name ATProto. The application covers protocol, software, and developer-tool classes. The Hacker News thread hit 201 points within 24 hours, and the reaction across the open-social community was immediate: did the company just close the openest protocol on the social web?

This article walks through what the filing actually says, what it does not say, and what it means for the three groups that care most: third-party Bluesky clients, archival tools like ThreadGrab, and creators who picked Bluesky precisely because the data lives in an open network.

1. What the filing actually covers

The USPTO application (Serial Number filed July 14, 2026) lists Bluesky Social PBC as the owner. The relevant goods and services classes include:

• Class 9: downloadable software for distributed social networking
• Class 42: providing non-downloadable software for protocol development, namely, a decentralized networking protocol
• Class 38: telecommunications services, namely, electronic data transmission via decentralized networks

Trademark law protects the mark, not the underlying technology. A trademark on the word ATProto lets Bluesky stop a competing company from selling a product called ATProto Enterprise Cloud. It does not let them stop anyone from writing code that speaks the protocol.

2. What the filing does not change

The repository at github.com/bluesky-social/atproto keeps its MIT license. Anyone can fork it, run it, or build a competitor. The Bluesky app itself, the PDS network, and the public relays are unaffected.

3. What it means for third-party Bluesky clients

If you run or maintain a Bluesky client (Skeets, Graysky, Olympia, TOKIMEKI, Deer.social, or one of the 40+ others), here is the practical impact:

1. Your code is safe. The MIT license is not affected. No re-licensing required.
2. Your app store listing is not safe. If the listing uses the wordmark ATProto in the title, subtitle, or screenshots, you need to re-read the new Bluesky brand guidelines. Expect a polite email asking you to switch to a generic phrase like Bluesky-compatible or for the Bluesky network.
3. Your docs and marketing copy need a once-over. Replace built on ATProto with built for the AT network or Bluesky network client in headers, footers, and social bios.
4. Your user-facing API key requests are not affected. App passwords, OAuth scopes, and DIDs continue to work exactly as before.

Most of the active client maintainers have already pushed a one-line copy fix. The reaction is calm, not panicked. The 201-point HN thread was about precedent, not about broken apps.

4. What it means for ThreadGrab's Bluesky archive flow

ThreadGrab's Bluesky reader hits the public Jetstream endpoint and parses ATProto commit records into Markdown. None of that touches the wordmark or any commercial use of the protocol name.

Here is a minimal archival flow that does not change with the trademark filing:

# 1. Subscribe to the public Jetstream for a user's repo
wss://jetstream1.us-east.bsky.network/subscribe?wantedDids=did:plc:xyz123

# 2. Persist each commit as a Markdown file
import json, pathlib
for event in jetstream_events:
    if event["kind"] == "commit":
        op = event["commit"]["operation"]
        record = event["commit"]["record"]
        path = pathlib.Path(f"bluesky/{event['did']}/{op}_{record['createdAt']}.md")
        path.parent.mkdir(parents=True, exist_ok=True)
        path.write_text(record["text"])

The same flow runs against any ATProto-compatible PDS, including self-hosted ones. If Bluesky the company disappeared tomorrow, ThreadGrab would still be able to read your archive from a relay on someone else's infrastructure.

5. Five steps to keep your Bluesky archive trademark-safe

1. Audit your product copy for the wordmark. Run a one-line grep across your site, app store listings, and README files. Replace ATProto with Bluesky network in commercial contexts.
2. Keep your code, repos, and dependencies MIT. Do not introduce a copyleft dependency just to hedge against a future trademark enforcement. The filing does not retroactively relicense existing forks.
3. Self-host a relay or PDS if you depend on the firehose for revenue. A relay on your own infrastructure removes the single point of failure. The reference relay implementation is in the same MIT-licensed repository.
4. Snapshot your archive to a content-addressed store. Storing CIDs alongside the human-readable Markdown means the proof-of-existence layer survives any future API changes. ThreadGrab writes both.
5. Subscribe to the open-atproto community mailing list. The community is producing a shared trademark playbook this week. Bookmark github.com/open-atproto/community/blob/main/trademark.md for the canonical FAQ.

6. The bigger picture: protocol governance is catching up

Trademarks on protocol names are not new. The W3C, IETF, and Linux Foundation all have well-worn policies. What is new is the social layer: a protocol that was sold to its earliest adopters on the promise of openness without corporate gatekeeping now has a corporate gatekeeper trademarking the word that says it is open.

The community's reasonable read: this is defensive, not aggressive. Bluesky is the only large company that has a public interest in stopping a competitor from selling a service under the ATProto name. The alternative, leaving the mark unregistered, would have been worse. Some company, possibly less aligned with the community, would have filed first.

Frequently asked questions

Sources: atproto.com/blog/at-protocol-trademark · Hacker News thread (201 points) · github.com/bluesky-social/atproto · USPTO application filing record, July 14, 2026.