Reported impact
Business outcome
320k+ daily transactions with 99.99% uptime Accurate auto ticketing from GPS data Architecture flexible enough to expand into 6 countries
- Customer Experience
- Risk Reduction
- Scalability
Real-time Analytics
FAIRTIQ needed a scalable, high-availability backend to process 320k+ trips/day across six countries, ensure near-zero downtime, support rapid growth, and handle noisy GPS-based data accounting.
Reported impact
320k+ daily transactions with 99.99% uptime Accurate auto ticketing from GPS data Architecture flexible enough to expand into 6 countries
FAIRTIQ needed a scalable, high-availability backend to process 320k+ trips/day across six countries, ensure near-zero downtime, support rapid growth, and handle noisy GPS-based data accounting. Built on MongoDB Atlas, FAIRTIQ leverages a cloud-native, microservices-ready platform offering flexible performance, high uptime (99.99%), and rapid deployment. Users simply check in via the FAIRTIQ app at the start of their journey. Check-in triggers sensor data collection, the app detects when the trip ends, and a journey mapping algorithm reconstructs the route using timetables, graph algorithms, and neural networks. Currently FAIRTIQ processes 320,000 trips daily and is available in eight European countries where it’s used actively by over 1.3 million people. Now expanding into new markets, the company’s goal is to simplify sustainable mobility internationally.
Operational events, telemetry, or transaction data are ingested into MongoDB Atlas Data Federation and MongoDB Atlas, enriched or filtered where needed, retained for fast query access, and served to analytics, monitoring, or customer-facing workflows in near real time. Upstream and downstream integrations include AWS, ticketing systems, APIs.
“A big advantage is if you release the schema upgrade, you release the microservice – you don’t need a database migration script, which will complicate your release pipeline. That’s important if you have continuous delivery, so it was the right thing for us.”
“As a startup, you want to be fast,”
“The way I see it is that the schema sits inside the application as opposed to inside the database,”
“We had only four months to bring our journey mapper from a prototype to a full product with pricing payment, customer care service, and integrate it with public transport systems.”
Review how this reference was scored and trace each normalized claim back to its documented source.
Scoring methodology
Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.
Traceability
Field coverage shows which facts each source supports. Dates are shown only when documented by the source.
Related