AdventureOS
The complete platform for planning, logging, and sharing outdoor adventures
Features
- •Four specialized studios — Trail, Peak, Sky, and Float — each purpose-built for a different adventure type
- •Universal asset management for vehicles, vessels, aircraft, and gear across all modules
- •Offline mode with full functionality in remote areas and background data sync on reconnect
- •Weather integration with real-time alerts and route impact analysis
- •Professional logbooks with regulatory-compliant hour tracking and certifications
- •Internationalization across 19 languages with automatic detection
What it is
AdventureOS is an outdoor adventure platform built for people who take their time outside seriously. It covers four major categories — off-road (Trail Studio), mountaineering and hiking (Peak Studio), aviation (Sky Studio), and boating and water sports (Float Studio) — through a unified interface that keeps all your gear, logs, and plans in one place.
The platform is designed around a simple idea: every type of adventure has its own vocabulary, its own equipment, and its own regulatory requirements, but the underlying operations — tracking assets, logging trips, planning routes, managing safety — are the same. AdventureOS provides specialized tooling per adventure type while keeping data consistent across all of them.
The stack is a Turborepo monorepo: Next.js 15 and React 18 on the frontend, Prisma with PostgreSQL for the database, NextAuth.js for authentication, and Redis for caching. It is built for production on DigitalOcean with Docker Compose handling local development.
Current status
AdventureOS was previously known as OverlandOS and began life focused on off-road and overlanding. The product has since expanded scope to cover all outdoor adventure types under the AdventureOS name, and the codebase is currently mid-migration to the new architecture. The core database schema, universal asset management system, and shared UI component library are complete. Active work is focused on wiring real external API integrations (VIN lookup, FAA registry, HIN lookup), applying the Redis caching layer across all API routes, and reaching 70% test coverage before a production re-launch.
How it works
When a user signs in, they land on a dashboard organized by studio. Each studio exposes the same core surfaces — an asset registry for vehicles or equipment, a logbook for trips and hours, a planning tool for upcoming routes — with domain-specific fields layered in. A pilot's logbook includes FAA-style hour breakdowns; a boater's vessel log tracks HIN numbers and float plans. Weather data and alerts are surfaced contextually within each planning view. Everything written to the platform is available offline via a service worker and syncs back when connectivity is restored.