Dino vs matrix-corporal
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?
Dino
Modern XMPP chat client for the desktop
VS
matrix-corporal
Reconciliator and gateway for managed Matrix homeservers
| Feature | Dino | matrix-corporal |
|---|---|---|
| Category | Matrix & XMPP | Matrix & XMPP |
| License | GPL-3.0 | AGPL-3.0 |
| Language | Vala | Go |
| Setup difficulty | Easy | Hard |
| Min. RAM | 128 MB | 128 MB |
| Deployment | binary, source | docker, binary, source |
| GitHub stars | ★ 2,472 | ★ 163 |
| First released | 2017 | 2018 |
| Replaces | Skype, Slack | Slack admin tools |
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
Choose matrix-corporal if…
- Released under the AGPL-3.0 license
- First-class Docker support for quick deployment
- Written in Go
- Tiny footprint — runs in 128 MB RAM
Frequently asked questions
Is Dino or matrix-corporal better?
Dino is the stronger all-round pick: it has both the larger community and the simpler easy setup. Consider matrix-corporal if its specific feature set fits your needs better.
Are Dino and matrix-corporal free and open-source?
Yes. Dino is licensed under GPL-3.0 and matrix-corporal under AGPL-3.0. Both can be self-hosted at no software cost.
Can I run Dino and matrix-corporal with Docker?
Dino: check the project docs for container support. matrix-corporal: yes.