Hi r/selfhosted,

I have been building LanGuard, an open-source network visibility tool for home networks and homelabs.

I wanted something between a basic device list and a full enterprise monitoring stack: an interface that discovers devices, keeps their history, organizes them into rooms, and makes network changes easy to understand.

Current features include:

• Automatic LAN discovery using ARP, reverse DNS, mDNS, LLMNR, SSDP, and NetBIOS
• Online/offline tracking, scan comparison, common port monitoring, and device history
• Hostname, vendor, role, and identity-confidence detection
• A visual Home Map for organizing rooms and devices
• Discord and Telegram notifications
• AdGuard Home integration with per-device DNS activity and blocked-query totals
• Inventory import/export and WatchYourLAN migration
• Docker Compose deployment and a native macOS version

LanGuard does not capture packet contents or inspect application traffic. The AdGuard integration stores aggregated domain counters rather than raw DNS responses.

One deployment detail worth mentioning: the Docker scanner uses host networking and privileged access so it can perform ARP-based LAN discovery.

GitHub: https://github.com/hillaliy/LanGuard

I would appreciate feedback from the self-hosted community, particularly about device identification, DNS integrations, and which network-controller integration would be most useful next.

Hello Daniel here,

it has been a while since my v4.0.2 post here. Development never really stopped, though, and a couple of days ago v5.3.0 finally landed. Instead of listing every version number in between, I simply want to share the progress I am most proud of.

Screenshots are in the gallery below.

For those who do not know reitti: it is Finnish for "route". Reitti is a self-hosted, privacy-first location tracking platform. Your device records where you go, reitti turns the raw points into visits, trips and a personal map diary. Everything stays on your infrastructure.

Highlights

• Custom map styles: Break free from the standard look. Upload your own style files, point reitti at hosted vector JSONs, or configure raster tile templates that fit your taste.
• Multi-device support and the workbench: Running more than one tracker? Aggregate them under a single account, stitch the timelines together and review or clean up individual points when devices disagree.
• Trips with multiple transport modes: Real life mixes modes. That walk to the car, the drive across town, the last stretch on foot is now recognized as one trip with separate segments. Tracks are color-coded by mode, transition badges appear where you switched, icons and colors are configurable, and you can reclassify historical trips from the settings.
• ⬡ Spatial coverage: Built on Uber's H3 hexagon grid, it shows how much of an area you actually explored ("You have covered 42 % of Berlin"), overlays visited cells on your main map and gives you a time slider to watch your footprint grow over the years. Like they say: "Hexagons are bestagons". Details in the spatial coverage documentation.
• FIT file import: Feed .fit exports from your watch or bike computer straight into your timeline, so workouts end up in your diary instead of living in yet another app.
• Immich integration with position write-back: You now can update your photos in Immich from reitti if they lack location information.
• Contextual diary: Annotate visits and trips with Markdown notes, moods and tags. Your history starts reading like a journal instead of a spreadsheet.

And plenty more underneath: additional community translations, Redis UNIX socket support, faster calculations, a much smaller PostgreSQL footprint when sharing the database with other apps, a revamped job status page, and countless fixes.

A word on Paikka, our own reverse geocoder

Reitti uses paikka (Finnish for "place") to name the places you visit. Since March it has handled close to 400,000 queries on my instance at an average of just under 40 ms, more than 13,000 of them on its busiest day, with zero recorded errors. reitti uses the free official instance by default, or you can self-host paikka. One of the gallery screenshots shows an estimate with all location it has resolved so far on a 50 km grid.

From MIT to AGPL-3.0

With growing interest from users, I moved reitti to the AGPL-3.0. My reasoning is simple: everyone keeps using and improving reitti freely, but the deal has to go both ways. If somebody builds on this work, their changes flow back under the same terms. That protects contributors against closed forks and keeps the project genuinely community-owned. There is no CLA either, so copyright stays entirely with whoever wrote the code.

Getting started

Every GitHub release ships with an attached docker-compose.yml. Head over to the documentation to set things up. Note: coming from pre-5.0 requires a database migration, please read the upgrade guide first.

For those already running reitti

I would love to hear how reitti fits into your daily life. What does your setup look like, what works well, and what is still clunky? Praise and criticism alike, every bit of it shapes where the project goes next.

Links

• GitHub: Report issues & view source
• Docs: dedicatedcode.com/projects/reitti
• RSS: Subscribe to the releases feed
• IRC: join #reitti on libera.chat
• Support: Ko-fi

AI usage disclosure:

• Implementation: Assisted. AI helps with boilerplate and problem solving, but architecture, design decisions and reviews remain entirely mine.
• Documentation: Pair. Release notes and docs start as an AI draft and are rewritten and finalized by me before anything ships.

Going forward I will post here roughly every couple of releases or when I feel about it. Everything in between lands in the releases feed. Thank you all for the support so far, happy tracking!

Daniel