Our client operates a multimobility platform that enables companies to manage all mobility types from one place: lease cars, bikes, public transport cards, shared cars, and work-from-home allowances. The idea is simple. The technical reality is not.
The problem: 150 sources, 150 formats
Every mobility provider delivers data in its own way. Leasing company A sends CSV files by email. Public transport provider B has a REST API. Bike supplier C works with SFTP uploads. And they all define their own fields, date formats, and status values.
Manual integration wasn't an option. With 150+ providers and growing, the team would spend more time on data processing than on product development.
The solution: standardized adapters
We developed an adapter framework that connects each provider to the Fleet platform via a standardized interface. Each adapter translates provider-specific data into a uniform format. Connecting new providers becomes a matter of configuring an adapter, not months of development.
Orchestration runs via n8n: data streams are scheduled, executed, validated, and automatically retried on failure. All data is stored in PostgreSQL and available to the platform in real-time.
Results
Integration time for a new provider dropped from an average of two weeks to two days. All 150+ data streams run autonomously without manual intervention. The platform now serves more than 45 companies with complete, current mobility data.
What other platforms can learn from this
Scalability starts with standardization. Not every problem is an AI problem. Sometimes the answer is a well-designed data model, standardized interfaces, and reliable orchestration. The technology doesn't have to be spectacular to deliver spectacular results.
