SaaS · Web Application · Product Development
Masar Travel
Travel Operations Platform
A multi-tenant platform for managing travel agencies, permits, providers, services, and operational workflows.
Overview
- Industry
- Travel
- Project type
- SaaS
- Status
- In Development
- Year
- 2026
- Awwam's role
- Product definition, UX/UI, Frontend, Backend, Architecture, Infrastructure
Overview
Masar Travel is an operations platform for travel businesses that need one system for agencies, providers, permits, and day-to-day service delivery. Awwam is designing and building the product end to end — from the operating model and UX through the multi-tenant architecture.
The Challenge
Travel operations were split across agencies, providers, permits, and follow-up work. Teams needed a shared system that could keep organizations separate, make requests visible, and turn disconnected steps into a reliable operating workflow.
What We Built
Agency management
Organize agencies, staff, and operating boundaries inside a multi-tenant product.
Agency operations home Request management
Move operational requests through a structured path instead of chat and spreadsheets.
Provider operations
Coordinate providers, services, and fulfillment from one operational layer.
Financial operations
Give finance a clearer view of charges, balances, and operational money movement.
Reporting
Surface the operational picture teams need without exporting everything to a spreadsheet first.
Users and permissions
Control who can see and change what across agencies, roles, and organizations.
Admin and access control
Product Screens
Our Role
- Product definition
- UX/UI
- Frontend
- Backend
- Architecture
- Infrastructure
Technology
- Next.js
- TypeScript
- Fastify
- PostgreSQL
- Prisma
- Redis
Outcome
Masar is becoming a single operating system for travel agencies and providers — replacing disconnected tools with structured workflows, clear permissions, and a foundation that can support more than one organization.
Engineering decisions
Why multi-tenant architecture?
The product has to serve separate travel organizations with shared software, not a one-off internal tool. Tenancy is part of the product, not an afterthought.
Why PostgreSQL?
Operational, financial, and permissioned data needs a relational model with real transactions — not a document store stretched into a business system.