OpenFamily

Overview

OpenFamily combines live household location sharing with place alerts, safety check-ins, SOS, and historical trails. It is designed for a family server rather than fleet management or public tracking. Deployment uses a Docker Compose stack on a VPS, Synology NAS, home server, or LAN machine, so the practical fit depends on having a suitable host and someone willing to maintain it.

Accounts, coordinates, saved places, and history are kept in PostgreSQL on the operator’s server. The app has no analytics SDK or crash reporter, but it does not encrypt database rows itself. Production operation therefore calls for strong secrets, closed public registration, backups, production mode, and host disk encryption. Default map-tile hosts can see the areas being viewed; iOS push goes through APNs, and optional SMS goes through Twilio.

Key features

Live location and places

The live map uses OpenStreetMap and displays family members with photo avatars, battery level, last-seen time, and movement state. WebSocket updates make it suitable for checking current household whereabouts without repeatedly refreshing. Saved places can trigger arrival and departure alerts, useful for routine coordination such as home, school, or work. Operators can select another raster provider or supply their own tiles, giving technically capable households more control over map delivery.

Safety tools

SOS starts with a ten-second countdown, providing a brief chance to cancel an accidental activation. Check-ins support notes, and a non-emergency family-help flow covers situations that do not warrant SOS. These tools make OpenFamily more than a passive map, although their usefulness still depends on a working self-hosted service and participating family members.

History and family access

Location history presents map trails, place stays, stops, and in-transit segments, with detailed history retained for 90 days. That is enough for recent context but not a long-term archive. Members join through an invite code and can receive admin, member, or child roles, allowing a household to separate management duties from ordinary access.

Administration and notifications

The web administration panel manages accounts and families, creates invites, configures optional SMS, downloads the Android APK, and shows the live map. Android notifications use UnifiedPush through ntfy, and Android operation does not require Google Play Services. This is valuable for households avoiding Google’s mobile dependencies, but it adds another service component for an operator to configure.

Pricing

Plan	Price	Includes
Open source self-hosted	Free	Self-hosted deployment under AGPL-3.0

There is no subscription charge for the software, but hosting, storage, backups, security work, and any optional SMS usage remain part of running it. The plan is best for a household that can supply and maintain its own infrastructure; families wanting a managed service should look elsewhere.

Platforms

OpenFamily supports Android, iOS, web, an API, and self-hosted deployment. The combination covers mobile members and browser administration, while the API and self-hosting options are most relevant to technically capable operators.

Who it's for

Choose OpenFamily when a household wants family location, alerts, and safety workflows while keeping its core records on a server it operates. It is particularly suitable for people comfortable with Docker Compose, backups, secrets, and host hardening, or for those who need Android notifications without Google Play Services. It is not the right choice for a family seeking turnkey setup, for a fleet, or for public tracking.

Pros and cons

Pros

• Self-hosted data: PostgreSQL storage on the operator’s server gives the household control over accounts, coordinates, places, and history.
• Broad safety coverage: SOS, a countdown, noted check-ins, and non-emergency help address more situations than location viewing alone.
• Useful live context: Avatars, battery, last-seen time, movement state, and WebSocket updates make the map practical for daily coordination.
• Open mapping flexibility: OpenStreetMap is the default, with support for another raster provider or self-supplied tiles.
• No Google Play Services requirement on Android: UnifiedPush through ntfy provides an alternative notification path.

Cons

• Real operational burden: The household must deploy, update, secure, back up, and monitor the Docker stack.
• Database rows are not app-encrypted: Host protection and disk encryption matter if the server is compromised.
• External-service exposure remains: Default tile hosts see viewed areas, while APNs and optional Twilio SMS handle some communications.
• History is limited: Detailed location records are retained for 90 days, not indefinitely.

Alternatives

For a broader comparison, see Family Locator Apps.

• Hauk is another free self-hosted option for Android, Linux, web, and PHP-based hosting.
• Family Locator suits readers who prefer freemium mobile apps, a free version, and a one-time Lifetime plan at 14.99 USD.
• Findmykids is a freemium Android, iOS, and web choice with a free Básico tier and paid Cuidar plan.
• Glympse fits users wanting a free mobile location-sharing app or a separate 15.00 USD-per-month PRO offering.
• iSharing offers freemium Android, iOS, and web access, including a free tier with one place alert and seven-day history after watching an ad.
• OtoZen is a freemium Android and iOS alternative with a free annual plan.
• Be Closer provides free real-time location on Android and iOS, with a 3.99 USD monthly Premium plan.
• Bluelane is an iOS and web alternative with a free tier and a 47.99 USD annual Pro subscription.

Verdict

OpenFamily is a strong choice for a technically comfortable household that wants family location and safety features on infrastructure it controls, especially when avoiding Google Play Services matters. Look elsewhere if you want managed reliability, minimal setup, or longer-term history without maintaining servers and security yourself.