Open source at Curolia
Last updated: 10 June 2026
Curolia is built in the open. We believe map software should be transparent, inspectable, and respectful of the people who use it — not a black box that monetises your memories.
Why open source matters to us
Open source lets anyone review how the product works, contribute improvements, and run their own copy if they choose. That aligns with how we think about trust: you should not have to take our word for it.
Our code lives on GitHub. Issues, discussions, and pull requests are welcome.
How we choose third-party services
No product is an island. We rely on external services for hosting, authentication, analytics, and more. When we pick a provider, we look for three things:
- Open source — we prefer software we (and you) can read, audit, and self-host where practical.
- Security — sensible defaults, clear data handling, and infrastructure we would trust with our own maps.
- Privacy — providers that collect only what they need, do not sell personal data, and share our view that your map content is yours.
We are pragmatic: not every layer of the stack is fully open source today. When a proprietary option is unavoidable, we still apply the same bar for security and privacy, keep data in the European Union where we can, and favour processors with transparent practices.
Examples in our stack
- Maps: vector tiles and styles from OpenFreeMap and geographic data from OpenStreetMap contributors.
- Backend: Supabase (open source) for authentication and data storage in the EU.
- Analytics: Umami — privacy-focused, cookieless usage metrics without ad tracking.
- Error reporting: Bugsink — self-hostable error tracking hosted in the EU to help us fix crashes without profiling you.
Licences and attribution
Curolia bundles many open source libraries and map data sources. The summary and full dependency list live on our open source licenses page.
Related
See also our Privacy Policy, Terms and Conditions, and Contact.