Gleam Mirrors Source Code on AT Protocol-Based "tangled"

On July 18, 2026, the Gleam project added the AT Protocol-based (Authenticated Transfer Protocol) code forge “tangled” as a mirror for its source code. According to a report from imustaskforhelp via Lobsters on tangled.org, Gleam’s development repository is now publicly available on tangled, allowing anyone to access and fork the code.

Background on the Gleam Language

Gleam is a statically-typed functional programming language designed to operate on the Erlang VM (BEAM). It is characterized by its type safety, scalability, and user-friendly learning curve. Its ability to catch type errors during compilation has made it well-regarded for developing large-scale distributed systems.

One distinctive feature of Gleam is that it is not owned by any corporation. The project is supported through sponsorships and is community-driven in its development. The official website explicitly states, “Gleam is not owned by a corporation,” emphasizing its independence from corporate control. The decision to mirror its code on tangled can also be seen as aligning with this decentralized philosophy.

The AT Protocol and the tangled Forge

tangled is a code forge that utilizes the AT Protocol. While the AT Protocol was originally developed by Bluesky as a decentralized social networking protocol, its applications extend beyond social media. This protocol enables authenticated data transfer and serves as a decentralized foundation for code hosting.

Traditional code hosting services have relied on centralized platforms such as GitHub and GitLab. In contrast, tangled leverages the AT Protocol to create a decentralized repository management system that does not depend on a single entity. This allows users to maintain sovereignty over their identities and data.

tangled’s URL structure follows the format “tangled.org/username/repository-name.” For Gleam, this translates to “tangled.org/gleam.run/gleam.” This structure facilitates self-authenticating addressing by combining domain names with project names.

Trends in Decentralized Code Hosting

The decentralization of code hosting has gained attention in recent years. Reliance on centralized platforms comes with risks, such as service outages, corporate acquisitions, or policy changes, which can disrupt developers’ workflows.

Gleam’s decision to mirror its code on tangled is a symbolic example of this trend. While the project’s main repository remains on GitHub, the additional mirror on tangled helps build a distributed development infrastructure across multiple platforms. This move likely aims to mitigate single points of failure and ensure community access to the code.

Other initiatives, such as the lightweight Git forge “GitRoot,” also exemplify efforts in decentralized code hosting. GitRoot offers a self-hostable forge with a minimal configuration, providing an alternative to centralized platforms. Unlike GitRoot, however, tangled emphasizes interoperability through a common protocol like the AT Protocol.

Implications and Future Outlook

Gleam’s decision to mirror its code on tangled carries two significant implications for the developer community.

First, it demonstrates the practicality of applying the AT Protocol to code hosting. While the protocol has been primarily associated with Bluesky, this move highlights its potential as a foundation for software development. Other open-source projects may follow Gleam’s lead and adopt tangled in the future.

Second, it underscores Gleam’s commitment to decentralization. By actively reducing its reliance on centralized platforms, a project that is not owned by any corporation is setting an example that could influence the direction of the open-source community.

However, the extent to which tangled can attract a substantial user base remains uncertain. GitHub’s network effects are still dominant, and decentralized forges face challenges related to user experience and discoverability before becoming mainstream.

Editorial Opinion

In the short term, Gleam’s decision to mirror its code on tangled is expected to increase awareness of the AT Protocol within the developer community. For developers interested in the practicality of decentralized protocols, the presence of actual hosted code serves as an important reference point. Over the next three to six months, the number of projects hosted on tangled will likely serve as a key indicator of the platform’s success.

From a long-term perspective, a gradual decentralization from centralized platforms is anticipated. While existing platforms like GitHub are likely to maintain their dominant position, decentralized forges with protocol-level interoperability, such as tangled, could carve out a niche for themselves. Community-driven projects like Gleam, which are free from corporate ownership, could pave the way for other projects to follow suit.

The editorial team believes that for decentralized code hosting to achieve genuine widespread adoption, it must offer benefits beyond simple mirroring. These could include features like cross-platform issue management and integrated CI/CD workflows.

References

• “Gleam has mirrored its source code on tangled (an AT-protocol based forge)”, by tangled.org via imustaskforhelp — Lobsters, 2026-07-18T21:21:41.000Z (ARR)
• Source URL: https://tangled.org/gleam.run/gleam