Hi DEV!
I’m the maintainer of RIM, an open-source, self-hosted chat workspace.
The idea is to put your tools and everyday actions beside your conversations. RIM has channels, DMs, groups and threads, but the part I’m most interested in sharing is how you can shape the workspace through plugins, commands, shortcuts and macros.
For example, the Kubernetes plugin shows pods alongside chat and lets you restart one after confirmation. The GitHub pull-request plugin puts open PRs in a panel beside the conversation. There are also plugins for polls and release tracking.
A quick tour of RIM: plugin panels, commands and search. Recorded in the running app with fictional demo conversations.
Plugins run in your client and can add panels, commands and context actions. Sandboxed web plugins work in both the browser and desktop app. Desktop process plugins can also connect to tools on your computer, such as kubectl.
Commands bring those actions into a searchable palette. You can assign eligible commands your own shortcuts, and macros save sequences of supported commands with their arguments so you can run a routine again without repeating each step.
I’m curious what other people would build with that foundation—a connection to an internal tool, a useful panel, or an action their team repeats every day.
The server is written in Rust, backed by PostgreSQL. The client uses React and TypeScript, with Tauri for the desktop app. A documented Docker Compose setup runs the server, database and web client. Desktop downloads are available for Linux and Windows.
RIM connects independently operated servers through relays and workspace hosts. Your relay handles your account and routes requests and events between your devices and the servers hosting your workspaces. A workspace host manages its channels, membership, permissions and moderation.
One server can do both jobs, which is how the Docker Compose setup starts. People using different relays can message each other and join shared workspaces without creating a separate account on every workspace host. Your identity is based on keys, with device linking and a recovery phrase.
DMs and private groups support MLS end-to-end encryption. Workspace channels, including private channels, are readable by their host server.
This is early 0.0.x software, with one maintainer. There’s no mobile app or voice/video calling yet, and the identity and encryption implementation has not had an external cryptographic review. The public instance is a community test service, with no guarantees of availability or data retention.
I also want to be transparent about development: I use AI coding agents extensively. I make the product and architecture decisions, review every change, and test locally and in a real browser against a throwaway server before each release. I’m responsible for maintaining what ships.
If you’d like to explore:
RIM is Apache-2.0 licensed. I’m looking for early testers, feedback on the self-hosting experience, and people interested in experimenting with plugins.
What tool or action would you want beside your team’s conversations?
