Conduit vs Dino
A side-by-side comparison of two self-hosted matrix & xmpp options — licensing, setup difficulty, resource needs, and what each one replaces.
Not the right match-up?
Conduit
Simple, fast and reliable Matrix homeserver in Rust
VS
Dino
Modern XMPP chat client for the desktop
| Feature | Conduit | Dino |
|---|---|---|
| Category | Matrix & XMPP | Matrix & XMPP |
| License | Apache-2.0 | GPL-3.0 |
| Language | Rust | Vala |
| Setup difficulty | Easy | Easy |
| Min. RAM | 128 MB | 128 MB |
| Deployment | docker, binary, source | binary, source |
| GitHub stars | ★ 2,200 | ★ 2,472 |
| First released | 2020 | 2017 |
| Replaces | Slack, Discord | Skype, Slack |
Why pick each one
Choose Dino if…
- Released under the GPL-3.0 license
- Easy to set up — beginner-friendly
- Active community (2.5k GitHub stars)
- Written in Vala
Frequently asked questions
Is Conduit or Dino better?
Neither is universally better. Dino has the larger community; both share a easy setup difficulty, so the decision comes down to features and licensing.
Are Conduit and Dino free and open-source?
Yes. Conduit is licensed under Apache-2.0 and Dino under GPL-3.0. Both can be self-hosted at no software cost.
Can I run Conduit and Dino with Docker?
Conduit: yes. Dino: check the project docs for container support.