Dawarich: A Self-Hosted Google Timeline Replacement with Real Import and Sharing Limits

What Dawarich Actually Replaces

Dawarich targets a specific pain point: Google Timeline, formerly Google Location History, is a proprietary service that collects your location data and stores it on Google's servers. Dawarich is a self-hostable web app that gives you the same core functions, tracking and visualizing location history, but on your own infrastructure. It is built in Ruby and released under AGPL-3.0. The intended user is someone who already exports their Google location data and wants to keep it locally, or someone who wants to track location live without sending it to a third party. The README is explicit about the scope: 'Your favorite self-hostable alternative to Google Timeline.' That is not a marketing claim; it is the entire project's reason for existence. The audience is privacy-conscious individuals, not enterprises. There is no mention of multi-user access beyond family sharing, and no mention of LDAP, SSO, or role-based permissions. If you need those, this is not the tool.

The Data Flow: From Phone to Map

The mechanism is straightforward. You install one of the supported tracking apps on your device, configure it to send location updates to your Dawarich instance, and the app stores and displays that data. Supported sources include Dawarich's own iOS and Android apps, a community Android app, Overland, OwnTracks, GPSLogger, PhoneTrack, and Home Assistant. For historical data, you import files from Google Maps Timeline, OwnTracks, Strava, Immich, GPX/GeoJSON files, and photos' EXIF data. The visualization layer offers several map styles: heatmap, points, lines between points, and a 'Fog of War' mode. The data flow is one-directional for imports, but live tracking is continuous. The README does not describe the internal architecture, database schema, or API endpoints. It only states that you run a Docker Compose command and access the app at localhost:3000. The lack of architectural detail is a limitation for anyone who wants to extend the project or understand how location points are stored.

Getting It Running: Docker Compose and a Demo Account

The quick start is a two-step process. Clone the repository, then run `docker compose -f docker/docker-compose.yml up`. Access the app at `http://localhost:3000`. To stop, press Ctrl+C. You can use default values or create a `.env` file based on `.env.example` to customize settings. The default credentials are `demo@dawarich.app` with password `safepassword`. The README says to change them in account settings. That is a real security concern: a demo account with known credentials is shipped by default. If you expose the instance to the internet without changing that, anyone can log in. The documentation covers environment variables and settings on the website, but the README does not list any specific variable names. For production use, you will need to consult the docs for reverse proxy setup, which is linked but not detailed in the README. The Docker Compose file is the only provided deployment method; there is no mention of bare-metal installation or Kubernetes manifests.

The Update Warning Is the Real Story

The most honest part of the README is the disclaimer. It says, in capital letters, 'DO NOT UPDATE AUTOMATICALLY'. It also states: 'Under active development: Expect frequent updates, bugs, and breaking changes.' This is not a caveat; it is a core operational fact. The recent release history supports it: version 1.14.0 was pushed on 2026-08-27, and 1.13.1 on 2026-08-23, meaning there were at least two releases within a week. The project is moving fast, and the maintainer is telling you that automatic updates may break your setup. You must read release notes before updating, back up your data before upgrading, and never delete your original data after importing it into Dawarich. This means the maintenance cost is not zero. You cannot set and forget. For a self-hosted tool, that is a significant trade-off. If you are not prepared to monitor releases and perform manual backups, Dawarich will eventually break your setup, and you will have no one to blame but the README, which warned you.

Features That Go Beyond a Simple Map

Dawarich is not just a map viewer. It includes family sharing, where each member can enable or disable location sharing individually. There is an Areas feature where you draw areas on the map and Dawarich suggests visits there. Visits is a beta feature that suggests places you have visited and lets you confirm or reject them. Statistics break down countries, cities, distance, and time by year and month. Insights generate natural language summaries like 'Your most visited place is home, with 120 visits' or 'You spent 30 days in Paris in 2024'. The 'Days in country' feature is explicitly useful for tax residency purposes. Trips let you visualize travel between two points in time, with route, distance, time, and notes, and if you integrate Immich or Photoprism, you can see photos from the trip. These features give Dawarich a distinct identity compared to a raw location logger. The integration with photo management apps is a concrete differentiator, because it ties location data to visual evidence, which is useful for trip recall and personal archives.

Limitations and Failure Modes

The most obvious limitation is the update policy. The README warns that automatic updates may break your setup, which means you must treat every release as a potential breaking change. That is a high operational burden for a personal tool. Another limitation is the lack of detail on data retention and privacy. The README mentions family sharing, but does not explain how consent is enforced or whether location data is encrypted at rest. For a privacy-focused tool, that is a gap. The import process is not described step by step in the README; it only lists sources and links to a tutorial. If the Google Takeout import fails due to a format change, you are on your own. The Visits feature is labeled beta, so you should not rely on it for accurate place history. The 'Days in country' feature is useful, but the README does not specify how it handles border crossings or time zones, which could produce inaccurate counts. For wrong-tool cases: if you need a location tracking system for a fleet or a business, Dawarich is not designed for that. There is no mention of geofencing alerts, real-time notifications, or API access for external systems.

Alternatives and How They Differ

The most direct alternative is OwnTracks, which is also self-hostable and supports live location tracking with a broker like MQTT. The difference is in scope. OwnTracks is a lightweight tracker that sends location points to your own server, but it does not provide a web-based timeline, statistics, family sharing, or photo integration. You would need to build or assemble those components yourself. Dawarich is a full application that includes the map, the statistics, and the import tools out of the box. Another alternative is Traccar, which is a self-hosted GPS tracking platform that supports many devices and protocols, but it focuses on real-time tracking and fleet management, not personal history or travel insights. Traccar has a different data model and a more complex setup. The choice between Dawarich and OwnTracks comes down to how much you want to assemble. If you want a single web app that does everything, Dawarich is the option. If you prefer a modular setup and are comfortable configuring an MQTT broker and a separate visualization tool, OwnTracks gives you more control.

Maintenance, License, and Upgrade Costs

The AGPL-3.0 license means you can use, modify, and distribute the software, but if you offer it as a network service, you must make your modified source code available to users. That is a real obligation if you run a public instance. For personal use, the license is permissive enough. The maintenance cost is high because of the update cadence. The README explicitly tells you to read release notes before updating and to back up before upgrades. There is a backup and restore tutorial linked, but the README does not summarize it. You will need to set up a backup routine yourself. The project is not archived, and the last push was on the same day as the latest release, so it is actively maintained. However, active development means breaking changes are likely. The upgrade cost is not just time; it is the risk of data loss if you ignore the warnings. The README's advice to never delete your original data after importing is a critical safety net. Keep your Google Takeout archive, your GPX files, and your OwnTracks exports. Dawarich is a tool for viewing and analyzing that data, not the only copy.

Editorial conclusion

Adopt Dawarich if you want a self-hosted, actively developed replacement for Google Timeline and are comfortable with frequent updates and manual upgrades. Do not use it if you need a stable, production-grade system with automatic updates or if you cannot commit to backing up before every change. Before adopting, verify that your location source (iOS, Android, Overland, OwnTracks, GPSLogger, PhoneTrack, Home Assistant) is supported and that your data import format (Google Takeout, GPX, GeoJSON, Strava, Immich, EXIF) matches the documented procedures. Also confirm that the demo account is changed immediately and that your reverse proxy setup follows the official guide, since the README explicitly warns that automatic updates may break your setup.

Official sources

1. Official documentation
2. Official README
3. Project repository
4. Release notes