Infrastructure
FastTrack Chat
Multi-tenant live chat you own: REST, WebSocket, operator inbox, and embeddable widget.
Shipped in production across multi-airport travel operations, replacing a rented LiveChat dependency under real customer load.
FastTrack Chat runs across FastTrack's multi-airport consumer sites and partner dashboards. Operators handle real booking inquiries under peak travel load. The system replaced a rented LiveChat dependency that charged per seat while holding conversation history the business could not fully access.
The problem
Rented live chat charges per seat for a WebSocket connection and locks your conversation history behind export limits. Your operators depend on someone else's uptime and pricing decisions.
For a multi-airport travel operation, that means every new operator seat adds margin pressure, every site embed depends on a third-party script, and customer conversations from Bangkok, Phuket, or partner sites sit in a vendor database you cannot query directly. When the vendor changes pricing or goes down, your frontline support stops with them.
The solution
A self-hosted chat platform built for multi-site, multi-tenant operations. Own the API, own the widget, own every message. Replaced rented LiveChat in production for a multi-airport travel service.
Deploy the Fastify API on infrastructure you control, embed the Preact widget on any consumer site, and run the operator inbox from a dashboard that reads directly from your Postgres. Web Push alerts reach mobile operators without a native app. Multi-tenant org and site isolation keeps partner brands separated without separate vendor accounts.
What you own
- ▸ Every message, attachment, and conversation record in your Postgres database
- ▸ The REST and WebSocket API, deployable on your cloud with your SSL keys
- ▸ The embeddable widget and React wrapper, no vendor script dependency
- ▸ Operator inbox, routing rules, and push notification configuration
What you stop paying for
- ▸ Per-seat live chat licensing that scales with operator headcount
- ▸ Vendor-hosted conversation storage with export limits and retention caps
- ▸ Third-party uptime and roadmap risk for your customer-facing support channel
Own vs rent
| Category | Rented (SaaS) | Owned (FastTrack Chat) |
|---|---|---|
| Pricing model | Per-seat monthly licensing that grows with every operator you hire | Fixed infrastructure cost regardless of operator headcount |
| Data location | Conversation history stored in vendor cloud with export limits | Every message and attachment in your Postgres database |
| API control | Vendor REST endpoints and embed script you cannot modify | Full REST and WebSocket API source, deployable on your stack |
| Vendor risk | Pricing changes, feature removals, and roadmap shifts affect your support channel | No third-party dependency for your customer-facing chat |
| Export / retention | Retention caps and CSV exports gated by plan tier | Direct SQL access and retention policies you define |
| Uptime dependency | Support stops when the vendor has an outage | Uptime tied to infrastructure you monitor and control |
Architecture overview
Talk about FastTrack Chat
Tell us how FastTrack Chat would fit your stack. We built it in production first and can speak honestly about what it does and what it does not.
Built in production. Shipped under real load.
Capabilities
- Fastify REST + WebSocket API with multi-tenant org and site isolation
- Operator inbox dashboard with real-time message delivery
- Embeddable Preact widget and React wrapper for any consumer site
- PWA + Web Push for mobile operator alerts without a native app
- Postgres + Redis stack you control, no per-seat toll
Architecture
Ready to own this layer?
Start a direct conversation about deploying FastTrack Chat on infrastructure you control.