IPplan vs TREK

IPplan is a free, self-hosted web application for administering and tracking IP address space. It can manage one or multiple networks and customer records, including overlapping address space. Administrators can find free ranges, split or join networks, search records, review statistics and keep an audit log of contents before and after changes. Network definitions can be imported from routing tables, tab-delimited files or NMAP XML. For DNS, IPplan supports forward and reverse zones, zone-transfer imports and XML exports. Group-based profiles let administrators set address-space boundaries, including read-only access. Authentication can use IPplan’s internal scheme or an external Apache module, including LDAP-based schemes and SiteMinder. Templates can add custom circuit, host-configuration and asset fields, while triggers can call user-defined functions on events. An external poller can scan subnets for active addresses, and configured SNMP support can read router routing tables. Deployment requires a web server, PHP and a database; documented database options include MySQL, PostgreSQL, Oracle and Microsoft SQL Server. The documentation prefers Apache and notes some workarounds may be needed with databases other than MySQL.

TREK is a self-hosted travel planner for organizing trips collaboratively in real time. Users can arrange places by day, optimize routes by distance, and send a day to Google Maps for turn-by-turn directions. Collaborators can edit itineraries together, see live presence, chat, run polls, track attendance, and share read-only public links. Reservation records hold confirmation numbers, files, and statuses for flights, stays, and restaurants. Budgets support multiple currencies and per-person or per-day totals; packing lists include templates and item assignments. OpenStreetMap is the default place search, Google Places is optional, and 16-day forecasts use Open-Meteo without API keys. Optional addons include travel statistics, vacation planning, journaling, and MCP integration. TREK runs on operator-controlled hardware, stores trip data in a SQLite file, and supports scheduled snapshots with retention policies. It can be installed as a PWA and has deployment documentation for Docker, Kubernetes, Unraid, Proxmox, Raspberry Pi, and Apple Silicon, with AMD64 and ARM64 images. It is open source under AGPL-3.0 and free for personal and internal company use.