What we build for clients
Services
We build and run every layer of a platform. These are the parts.
These are the capabilities we deliver for clients. For software we build and sell ourselves, see Products.
Platform development
Guest-facing and operations software, built to be used in four languages and by everyone.
- Web
- React, Vue, Angular. Guest portals for booking and preferences, admin dashboards for crew and operations, real-time analytics, mobile-responsive throughout. Arabic, Turkish, Russian and English. WCAG 2.1 accessibility.
- Mobile
- Native iOS in Swift, native Android in Kotlin, cross-platform in React Native. Guest apps covering pre-cruise to post-cruise, crew applications, offline-first operation, push notifications, fingerprint and face authentication.
- Progressive web apps
- Installable on mobile and desktop, offline-first, native-feeling, no app store required.
Backend and microservices
Services sized to a job, with the queues, caches and logging that keep them honest.
- Node.js with Express and Nest
- Python FastAPI for specialised work
- RabbitMQ and Apache Kafka for asynchronous processing
- Redis for sessions and performance
- WebSocket for real-time features
- Centralised logging on the ELK stack
Six core services in Guest 360: Guest (profiles and communication) · Booking (availability and reservations) · Payments (multi-gateway) · Notifications (multi-channel) · Analytics · Recommendations.
Middleware and integration
Most of the difficulty in an enterprise platform is between the systems, not inside them.
- Platforms
- Apache Camel for orchestration and transformation · MuleSoft Mule ESB for API management, routing and transformation · Boomi AtomSphere for cloud iPaaS with pre-built connectors · custom adapters where a legacy system leaves no other route.
- Typically connected
- Payment gateways across currencies and methods · SAP and NetSuite for GL posting and reconciliation · activity and excursion providers for live inventory · travel insurance for policy issue and claims · Salesforce and Zoho for guest data.
Databases
PostgreSQL unless there is a reason, and we will tell you the reason.
- PostgreSQL
- The default: open-source economics, ACID transactions, JSON where the schema needs to flex, and indexing that holds up under load.
- Oracle
- For estates already there: partitioning, RAC, and a supported path to PostgreSQL when it is time.
- SQL Server
- Windows environments, hybrid cloud, BI integration.
- NoSQL
- MongoDB for documents that will not sit still, Elasticsearch for search and logs.
- Services
- Schema design, performance tuning and indexing strategy, backup and disaster recovery, enterprise data migration, replication and automated failover.
CRM
- Salesforce
- Guest and contact management, bookings as opportunities, service ticketing, revenue forecasting, campaigns. Configuration and customisation, Apex and Lightning Web Components, API integration with the platform, user training, ongoing support.
- Zoho CRM
- Where the economics matter: guest profiles and interaction history, pipeline, support tickets, analytics, workflow automation. Setup, custom modules and workflows, platform integration, and Zoho Mail and suite optimisation.
- Both
- Real-time synchronisation, event-driven, bi-directional with conflict resolution, and a full audit trail of what changed and when.
One supplier, every layer
Web, mobile, backend services, integration, data and CRM under one service model. Nothing to hand across a boundary, no silo to reconcile, one team accountable for the whole thing — with open-source economics where they work and enterprise integration platforms where they are needed, and TraceIT monitoring all of it.