Choosing a Backend
Colota sends location data to a server you control. If you're not sure which backend to use, this page gives a quick comparison.
Comparison
| Backend | Best for |
|---|---|
| Dawarich | Location history, map visualization, stats and trip analysis |
| GeoPulse | Location tracking with trip visualization and timeline |
| Home Assistant | Home automation - use location as a trigger for automations and zones |
| OwnTracks | Self-hosted location history using the OwnTracks Recorder |
| Reitti | Location history with automatic visit and trip detection and daily timeline |
| PhoneTrack | Track devices from within an existing Nextcloud install |
| Traccar | Real-time GPS tracking platform for multiple devices and fleet management |
| Custom Backend | Any HTTP endpoint - configure field names and format to match your API |
Quick decision guide
- I want to visualize my location history with maps and stats - use Dawarich or GeoPulse
- I use Home Assistant for home automation - use Home Assistant
- I already run Nextcloud - use PhoneTrack
- I need to track multiple devices - use Traccar
- I want to send to my own API - use Custom Backend
- I want to send to multiple backends at once - point Colota at colota-forwarder and configure each target there
No backend needed
Colota works fully offline without any server. Locations are stored on-device and can be exported as CSV, GeoJSON, GPX, or KML at any time.