One operating view
A travel dashboard built around work that needs attention
Follow leads, overdue actions, quotes, pipeline, conversion, and revenue without stitching together a generic CRM and spreadsheets.
Open-source travel operating system
From first enquiry
to journey complete.
MooNsConfig connects CRM, itinerary curation, route maps, supplier RFQs, proposals, bookings, customer support, and governed Maya automation in one TypeScript platform.
Core modules run locally. Provider-backed AI, email, telephony, payments, WhatsApp, SSO, and live inventory require your own credentials and stay disabled when absent.
The core workflow
One traveller journey, not five disconnected tools.
The shortest way to understand MooNsConfig is to follow the work from enquiry to operation. Each step feeds the next and keeps its evidence attached.
- 01
Capture the enquiry
Bring a lead in from calls, chat, WhatsApp, callback requests, or a form and keep ownership, follow-ups, and history together.
- 02
Curate the trip
Turn a brief or inspiration image into an editable itinerary, then add activities, stays, transport, media, and route stops.
- 03
Request real rates
Choose scope, dates, hotels, and vendors. Review Maya's RFQ draft before anything leaves the workspace.
- 04
Build the proposal
Use catalogue and rate-card data to create a versioned quote and branded PDF without inventing missing supplier prices.
- 05
Book and operate
Keep services, participants, payments, invoices, incidents, messages, and trip status connected to one traveller record.
Guided product tour
Real screens from the running application.
These are direct Chrome captures from the local MooNsConfig interface. They show implemented workflows, not concept art or a fabricated customer deployment.
Lead workspace
Calls, email, WhatsApp, triage, notes, and follow-ups in context
The screenshot uses a clearly fictional 555 demo record. The in-app WhatsApp inbox supports human replies, templates, unread state, and delivery status when Meta is configured.
Itinerary studio
Edit every day instead of accepting an opaque AI answer
Generate a starting point, then control descriptions, time-of-day activities, locations, coordinates, route stops, and transport segments.
Route maps
Build brochure maps and animated journeys from the itinerary
Mix road, rail, flight, and cruise legs; adjust stops and curves; import or export JSON; and export static artwork for proposals.
Package operations
Package content, pricing, media, suppliers, and publishing in one place
Manage regional and seasonal packages, B2B cost, B2C selling price, margins, verification, SEO, itineraries, RFQs, and publishing.
Vendor outreach
Ask the right suppliers for the right information
Select package, hotel, transport, or cruise scope; require travel dates; choose vendors; and review the composed email before dispatch.
Governed automation
Maya has visible controls, approvals, and kill switches
Provider readiness, channel controls, approval queues, disruption cases, refund SLAs, and dead letters stay visible to operators.
Who this is for
Built for travel teams. Open for builders.
- Travel agencies replacing spreadsheets and disconnected point tools
- Tour operators building custom itineraries and supplier quotes
- DMCs coordinating packages, vendors, stays, cars, and activities
- Engineering teams exploring a multi-tenant travel SaaS foundation
- Contributors interested in maps, workflow automation, accessibility, and AI guardrails
$ git clone https://github.com/schowdary75/moonsconfig.git$ cd moonsconfig$ ./start.sh✓ MooNsConfig is readyEvaluate it yourself
One start command, documented configuration.
- 1Install Docker Desktop or Docker Engine with Compose.
- 2Clone the repository and enter the moonsconfig directory.
- 3Run ./start.sh on macOS/Linux or Git Bash on Windows.
- 4Open the printed local URL; run ./stop.sh when finished.
Open source, MIT licensed
Pick a small problem. Leave the travel stack better.
Start with documentation, accessibility, route-map polish, responsive UI, testing, sample integrations, or developer setup. The repository includes scoped issues, contribution guidance, recognition, and a code of conduct.