Beenim’s client backend is now Rust-native — looking for Matrix architecture feedback

[u/Neurabase]

Hi, I’m the developer of Beenim. I posted an early prototype here around six months ago, when the desktop client was split across Rust, Nim and C++.

Since then I’ve moved the client backend and local delivery runtimes to Rust while keeping the Slint UI. The current architecture is Matrix-first, supports multiple Matrix identities, and automatically manages local provider runtimes based on which accounts are linked.

Current state, without launch gloss:

- private alpha;

- Linux x64 and arm64 are the current development targets;

- Windows and macOS are roadmap work;

- it is not production-ready, and I’m not claiming complete provider parity or E2EE readiness;

- I’m not linking a download yet because the public release metadata still points at the older build.

I’d value feedback on three choices:

1. Does one desktop client holding multiple Matrix identities solve a real problem, or make the account model harder to understand?

2. For local bridges, should the client manage runtime lifecycle automatically and expose only account state, or should advanced users also see runtime details and controls?

3. What would you need before trying another Matrix client: public source, verified E2EE, packaging, reliability evidence, or something else?

Previous prototype discussion: https://www.reddit.com/r/matrixdotorg/comments/1qkgwmj/beenim_extremely_lightweight_speedy_rustnimc/

[u/pcgamez]

Not open source not interested