Plan once. Go everywhere.

Nilago is a constraints-aware travel OS. It turns intent and limits into a feasible plan, then helps you keep time on the day—no chaos, no guesswork.

How Nilago thinks
Intent
  • • Where & when
  • • Budget & pace
  • • Must-do / avoid
Constraints
  • • Open hours
  • • Drive windows
  • • Capacity & season
Output
  • • Feasible itinerary
  • • Alternatives ready
  • • Day-of runbook

The real problem

Trips fail in the details: closures, queues, hidden buffers, and suppliers you can’t verify. Plans that ignore real-world constraints collapse on day two.

Today
  • • Tabs, guesswork, and fragile itineraries
  • • No shared truth for timings & handoffs
  • • Suppliers unclear; pricing opaque
With Nilago
  • • Constraints-first plan that’s actually feasible
  • • Alternatives pre-published; buffers explicit
  • • Clean runbook that keeps the day on time

The idea

Itinerary Engine

Balances days against time budgets, open hours, and drive windows. Produces honest plans with alternates.

Supplier Graph

Stays, transport, activities, guides; seasonality, blackout dates, and capacity rules.

Runbook & Discipline

Check-ins, timeboxing, incident logging, and escalation ladders keep the day moving.

How it works

State intent & limits

Dates, pace, non-negotiables, exclusions, and budget.

Draft within constraints

Engine composes feasible days with buffers and alternates.

Day-of guidance

Simple runbook with timings, handoffs, and quick swaps if things change.

Example day
08:00
Depart
09:20
Viewpoint (45m)
12:00
Lunch (60m)
15:30
Check-in / Rest
Buffers are explicit. Alternates are pre-listed. Timings reflect drive windows & open hours.
Nilago OS

The constraints-aware planner

Turns intent and limits into feasible days, with clear buffers and ready-to-swap alternates. Surfaces: planner, day-of runbook, offline cache.

  • Itinerary engine with time budgets
  • Supplier graph with docs & seasonality
  • Runbook with check-ins & incident log
Nilago EXPEDITIONS

Trips built on the OS

A concept line of small-group departures assembled from our route blocks. Each departure shapes itself to travellers’ pace and priorities — more like a tailored fit than a set menu.

Cohort or privateDesign-forward, not luxury-label Anywhere blocks

Architecture

Data

Places, hours, drive times, seasonality, supplier docs.

Engine

Constraint solver produces feasible days & alternates.

Surfaces

Planner, runbook, messaging, offline cache.

Ops

Check-ins, manifests, incident log, escalations.

FAQ

Is this a luxury travel business?

No. Nilago isn’t a luxury label. We care about reliable, design-forward planning; comfort is selectable, not our identity.

Are expeditions cookie-cutter?

Departures are shaped to travellers’ pace and priorities—think tailored cadence and optional layers, not a one-size checklist.

Is this a travel agency?

Nilago is software first. Expeditions are a concept line built on the OS, not a traditional agency catalogue.

Will it book things for me?

Early versions focus on planning accurately; booking integrations come later.

Does it work offline?

Yes. Your runbook and essentials cache for day-of use.

When can I try it?

Join the waitlist below. We’ll invite a small group to the first public beta.

Join the Nilago beta

Be first to try a constraints-aware planner—and get updates on concept expeditions built on it.