Core Concepts
GGNomad's architecture is built around a small set of connected concepts that turn a destination into an itinerary, an itinerary into confirmed bookings, and bookings into a followed trip — all on one booking spine. Understanding these concepts is the fastest way to understand how the whole platform fits together.
Forward-looking capabilities in these concepts are flagged as roadmap or target experience.
The building blocks
🧭 Destination
The entry point — a place a traveler discovers by interest, season, budget, and search. Opening a destination surfaces the stays, tours, experiences, and events available there.
🏠 Listing
The unit of supply: a stay, a guided tour, or an experience owned by a host or operator. A listing moves through a verification lifecycle before it goes live.
🧳 Itinerary
The traveler's plan — a day-by-day collection of stays, tours, experiences, and tickets with a running total that updates as items are added.
Key components
Availability & pricing Calendar
Each listing carries its own bookable inventory:
- Per-date and seasonal pricing
- Per-date capacity and minimum stays
- Blackout dates
- An availability toggle that closes inventory without deleting it
Booking & trip timeline Lifecycle
A booking is a confirmed reservation with a durable identity and its own timeline:
- Booked → confirmed → upcoming → checked-in → completed (or cancelled)
- Every transition is stamped on the traveler's trip timeline and the host's booking queue
- A trip groups bookings and follows them on one timeline, with reminders
Event & ticket Entertainment
Concerts, shows, festivals, and attractions are discoverable by destination and date, and their tickets check out alongside stays and tours on the same booking spine — so an entertainment-led trip is one plan, not three.
Trust & governance
⭐ Review & rating
The trust layer:
- Travelers rate and review after a trip
- Hosts respond, turning feedback into a conversation
- Reviews roll up into a listing's overall rating, feeding discovery
- Verified listings gate discovery, bookings, and payouts
🔐 Roles & RBAC
A governed, multi-role marketplace:
- One identity can be a traveler, host/operator, or administrator
- Every action is scoped by role
- Every API operation is permission-checked before it runs
- Every change is attributable in the activity log
How they fit together
The same booking spine flows through the entire journey, so there is never any re-assembling between tools:
- A destination surfaces listings and their availability
- A traveler adds items to an itinerary with a running total
- The itinerary carries into a single checkout, materializing bookings
- Bookings live on one trip timeline through their lifecycle
- After the trip, reviews feed back into discovery
Our team is ready to help travel, tourism, and entertainment businesses get ready for launch. Contact us