Idunn vs Mimirsbrunn
A side-by-side comparison of two self-hosted maps & gis options — licensing, setup difficulty, resource needs, and what each one replaces.
Not the right match-up?
Idunn
Geocoding and place API for self-hosted map frontends
VS
Mimirsbrunn
Geocoding engine for autocomplete address search
| Feature | Idunn | Mimirsbrunn |
|---|---|---|
| Category | Maps & GIS | Maps & GIS |
| License | Apache-2.0 | AGPL-3.0 |
| Language | Python | Rust |
| Setup difficulty | Hard | Hard |
| Min. RAM | 1,024 MB | 2,048 MB |
| Deployment | docker, source | docker, binary |
| GitHub stars | ★ 38 | ★ 7 |
| First released | 2018 | 2016 |
| Replaces | Google Places API, Foursquare Places | Google Places API |
Why pick each one
Choose Idunn if…
- Released under the Apache-2.0 license
- First-class Docker support for quick deployment
- Written in Python
Choose Mimirsbrunn if…
- Released under the AGPL-3.0 license
- First-class Docker support for quick deployment
- Written in Rust
Frequently asked questions
Is Idunn or Mimirsbrunn better?
Neither is universally better. Idunn has the larger community; both share a hard setup difficulty, so the decision comes down to features and licensing.
Are Idunn and Mimirsbrunn free and open-source?
Yes. Idunn is licensed under Apache-2.0 and Mimirsbrunn under AGPL-3.0. Both can be self-hosted at no software cost.
Can I run Idunn and Mimirsbrunn with Docker?
Idunn: yes. Mimirsbrunn: yes.