Distronode Publishes Its Open-Source Work and the Software District AI Runs On
One public page now names the open-source software District AI runs on and the two Apache-2.0 projects Distronode publishes: bridgewatch and District Scheduler.
Distronode has published a single public record of its relationship to open-source software at distronode.com/open-source. The page names the open-source projects District AI runs on, with the licence of each, and presents the two projects Distronode publishes itself, both under the Apache-2.0 licence.
The first is bridgewatch, a menu-bar app for macOS and Linux that tells a software team whether a change actually went live, across both GitLab and GitHub. Version 1.0.0 was released on September 19, 2026. The second is District Scheduler, the scheduling engine behind every District AI booking and the booking page included in every plan. It is Distronode's version of the open-source Calnode project, with one addition that keeps many businesses' calendars safely separated inside one system.
Both public repositories are the ones Distronode deploys from, with their issues, changelogs and security policies in the open. When Distronode fixes a bug in a project it builds on, the fix is sent back to that project rather than kept as a private patch. Its fixes to Calnode are part of Calnode today and reach every business that runs it.
"A telecommunications company built on frontier AI asks customers to trust where their calls are handled," said Sean Dean, Founder and CEO. "That should be easy to check. We already publish where your data lives and who helps us process it. Publishing the code is the same promise, kept one step further."
Nothing changes for customers, and no action is needed. The background and the reasoning are in the blog post. The projects are on GitHub, and Distronode's public group is on GitLab.
Two projects, one page
bridgewatch 1.0 and District Scheduler are public under Apache-2.0, and the fixes we make to the software we build on go back to it. See distronode.com/open-source.

