Dino vs Element Call
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?
| Feature | Dino | Element Call |
|---|---|---|
| Category | Matrix & XMPP | Matrix & XMPP |
| License | GPL-3.0 | AGPL-3.0 |
| Language | Vala | TypeScript |
| Setup difficulty | Easy | Hard |
| Min. RAM | 128 MB | 1,024 MB |
| Deployment | binary, source | docker |
| GitHub stars | ★ 2,472 | ★ 984 |
| First released | 2017 | 2022 |
| Replaces | Skype, Slack | Zoom, Google Meet |
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 Element Call if…
- Strong encryption
- Federated via Matrix
- No app install needed
Frequently asked questions
Is Dino or Element Call better?
Dino is the stronger all-round pick: it has both the larger community and the simpler easy setup. Consider Element Call if its specific feature set fits your needs better.
Are Dino and Element Call free and open-source?
Yes. Dino is licensed under GPL-3.0 and Element Call under AGPL-3.0. Both can be self-hosted at no software cost.
Can I run Dino and Element Call with Docker?
Dino: check the project docs for container support. Element Call: yes.