Wayli

Privacy-first location tracking and trip analysis. Self-hosted, no third-party data sharing.

Features

• Trip Detection - Automatically detects trips from GPS data with transport mode classification
• Statistics - Distance traveled, transport modes, and interactive visualizations
• Data Export - Export everything in JSON, GeoJSON, or CSV
• Privacy-First Geocoding - Uses Pelias, an open-source geocoder, keeping location lookups off commercial services
• OwnTracks Integration - Import location data from OwnTracks

Screenshots

Automatically detected trips with cover photos and transport modes

Distance traveled, transport modes, and interactive maps

Tech Stack

• Frontend: SvelteKit, TypeScript, Tailwind CSS
• Backend: Fluxbase (PostgreSQL, Auth, Storage, Jobs)
• Geocoding: Pelias (self-hostable, privacy-preserving)
• Mapping: Leaflet

Quick Start

Docker Compose:

cd deploy/docker-compose
./generate-secrets.sh
# Edit .env with your configuration
docker compose up -d

Kubernetes (Helm):

helm install wayli oci://ghcr.io/nimbleflux/charts/wayli -n wayli --create-namespace

See the Deployment Guide for detailed instructions.

Development

cd web
npm install
npm run dev

See CLAUDE.md for development conventions and web/README.md for architecture details.

Privacy

Your location data is sensitive. Wayli is designed to be self-hosted, giving you complete control over your data. All trip data, place visits, and personal information stay on your server.

For geocoding, Wayli uses a hosted Pelias instance at pelias.wayli.app by default (a Wayli-managed server)—coordinates are sent for address lookup but no user information is included and nothing is persisted. You can also self-host Pelias for complete independence.

Contributing

See CONTRIBUTING.md for guidelines.

License

AGPL-3.0. See LICENSE.