All blog posts
Updates 2 min read

Commonveil Plans Rust Realtime Rooms and Updates

An open pull request proposes Rust support for realtime WebSocket rooms, background maintenance and server update operations.

By Comutability Published Update from
Illustrated Rust-backed realtime chat rooms linked to a server, with maintenance and update symbols.

Project update: 15 November 2026. GitHub pull request #16: open proposal, not merged. Commonveil has not been independently security audited.

An open pull request proposes Rust support for realtime WebSocket rooms, background maintenance and server update operations.

Why this matters

Realtime presence, voice-room signalling and scheduled clean-up are among the remaining operational pieces of a fully Rust-based server. Unlike the preceding migration stages, this pull request was still open when the archive was prepared, so the article records work under review rather than a completed integration.

Detailed change record

The public engineering notes below describe what was implemented or proposed and the evidence recorded with the change. Historical instructions in the notes describe the pull request at the time it was raised.

  • Realtime (actors, rooms): the WebSocket host at /api/actors// with the Presence and VoiceRoom rooms. Uses axum's ws feature and futures-util (both MIT/Apache-2.0, already in the tree through axum).
  • Scheduled tasks (maintenance): expire, inactive and deliver, on the same timers as the Node.js server.
  • Updates (updates): the release check, backups before an update, the updater handshake and /api/admin/updates.

Verified

  • tests/parity_realtime.rs: the same WebSocket script against both servers. Every message each connection receives, and every close code and reason, matches. tungstenite (dev-only, same version as axum's) is the test client.
  • tests/parity_updates.rs: both servers against a stand-in release list and updater. Every answer matches.
  • tests/maintenance.rs: the three tasks against a fresh site's data. The Node.js server runs these only on its own timers, so they can't be compared side by side.
  • cargo clippy --all-targets -D warnings and the full cargo test pass locally.

Outstanding

  • Federation, which is on by default, so the Docker switch waits for it. The admin CLI (make-admin, reset-password, setup-code, backup, version) also needs porting.

Decisions and principles behind the work

Comutability is building towards privacy, user control and genuinely self-hostable software. That does not mean every proposal is already deployed. The Rust backend is being checked for parity with Node.js before it can replace the existing Docker image.

What comes next

Finish review and parity testing, preserve update backups and release only after the complete server has been checked on actual deployments.

Check the sources

Sources and further reading

Explore the evidence and original project records behind this article.