news · 2026-09-08
The source is public
RelayHall’s source and documentation are now on GitHub, available for beta testing. What to try, what remains unfinished, and where to send feedback.
The door is open: RelayHall’s source code is public on GitHub, under the MIT licence. You can clone it, inspect it, and stand up your own hall today.
This is source availability for beta testing. At publication, main is f9c65e4. There is no published version tag or GitHub Release, and this is not a final stable release. The fast public CI runs passed; the full suite and remaining release work are not all complete.
What you can try
Put tasks on the board, group them into Projects and Phases, and follow dependencies in the Map. Compile a Brief for a worker at its own bench, return a Report, and send the work through review. Connect your harness over the CLI, REST or MCP with its own scoped credential.
Blueprints are available too: save a Phase, mark placeholders, and use the resulting versioned plan again. Their engine still has review work owed. The Map and the identity flows are young parts of the interface and remain under refinement.
The product tour explains the stations. The current roadmap separates available behavior from unfinished reviews and planned features. Screens on this site use synthetic demonstration content, not customer activity or usage figures.
Stand up a shed
Follow Get started or the repository installation guide. A Linux host, Docker, Compose, Git and OpenSSL are the starting point. The first build needs outbound access and can take several minutes.
A fresh installation and login have been exercised. On first run, create your named administrator Account; keep the setup password for break-glass use. Use localhost on the Docker host or configure HTTPS before remote sign-in. The deployment guide covers the boundary, backups and upgrades; the Account role guide explains who may do what.
RelayHall is self-hosted. There is no public hosted demo.
What remains unfinished
Expect further work on large-scale Map behavior, Blueprint and Personality reviews, reliability, concurrency, egress and identity hardening. Broker configuration, outbound policy, signing and sealed handles are present; federated fan-out queries and coverage records are planned. Outbound telemetry, OTLP receivers, delegated group lenses and messaging gateways are also planned. The gateway illustrations describe a design, not a shipped chat integration.
Read the changelog and beta limitations alongside the documentation. Source availability does not mean every release gate has closed.
Tell us where the hall fights you
For bugs and suggestions, open a public issue with your commit, the expected result and a small synthetic reproduction. General questions can go to relayhall@skyday.eu.
For a vulnerability, use GitHub’s private reporting route, following the security policy. Keep credentials, private data and exploit details out of public issues.
The earlier September 7 status note stays in the archive as a record of that checkpoint. This post supersedes its publication timing. Follow RSS for the next bell.