OpenFamily
7.7#1 in family locator appsFree planFree planAndroidiOSWebAPI
VisitOpenFamily vs OwnTracks
What both publish
| Fact | OpenFamily | OwnTracks |
|---|---|---|
| API | The public Go API documents health, configuration, authentication, family, place, device, location and alert endpoints plus a WebSocket stream. | The OwnTracks Recorder makes stored location data available through an API. |
| Integrations | Android notifications use UnifiedPush through ntfy, and the app does not require Google Play Services. | The booklet describes using OwnTracks with Home Assistant to show locations on a map and trigger automations when people enter or leave zones. |
| Privacy | Accounts, coordinates, saved places, and history are stored in PostgreSQL on the operator's server, and the app has no analytics SDK or crash reporter. | OwnTracks says users decide where to store their data, how to process it, and how long to retain it. |
OpenFamily plans
- Open source self-hostedFree
- Self-hosted OpenFamilyFree
OwnTracks plans
No prices published.
Pick OpenFamily if…
It suits households whose member can run a small Docker stack and who want shared location and safety tools. It is not designed for fleets or public tracking.
Pick OwnTracks if…
It suits people who want location sharing or history while choosing their own server and retention practices. It requires users to configure a backend and understand platform background limits.