Tag: self-hosting

One host, 20 Unix users, 20 rootless Docker daemons. The isolation model that beats a single shared daemon, plus the trade-offs nobody tells you about.

Stop letting Google Maps know where you've been. Pair OsmAnd on your phone with self-hosted tiles for offline-first maps that don't snitch on you.

Tired of gluing OSRM + a tile server together? OpenRouteService bundles routing, isochrones, matrix, and elevation APIs behind one self-hosted stack.

A real workload, a real bill, and a real migration. What Google Maps API actually costs, what self-hosting actually saves, and what the migration cost in time.

SQL for OpenStreetMap. Overpass lets you ask 'every coffee shop in Brooklyn near a subway.' Self-host it and stop fighting public-instance rate limits.

Replace Google Maps with self-hosted Nominatim, PostGIS, and a Martin tile server. Geocoding, reverse geocoding, and vector tiles, all on one box.

Vector vs raster tiles. MBTiles vs PostGIS-on-the-fly. Here's the actual storage and CPU cost of running each tile stack at home, with no marketing fluff.

Real RAM, disk, and CPU numbers for self-hosted Nominatim. Planet vs region, mini PC vs server, what survives the import and what doesn't.

Strava and Google route cyclists onto highways. BRouter's elevation-aware profiles know what a bike actually wants. Here's the self-hosted setup.

Run OSRM in Docker with a regional OSM extract, compile a routing profile, and get your own /route endpoint live. Profile compilation gotchas included.

Three open-source routing engines, three philosophies. OSRM is fast, Valhalla is flexible, GraphHopper is balanced. Here's how to actually pick one.

Wire local Nominatim into Home Assistant for reverse geocoding without leaking GPS coords to Google or Mapbox. Privacy-respecting smart home in 30 lines.