Our Clients · Cities and transit authorities
Better coverage. Same budget. Proof included
Towns and city districts across Europe and Asia run Shotl services today — replacing empty fixed lines with on-demand coverage their residents actually use.

Who does what
Your service, your brand, our platform
The question every tender asks first. This is how the work splits in a city deployment.
| You | Shotl | |
|---|---|---|
| Service name and brand | YouYour service name and trademarks, in your colours. | ShotlWhite-label app themed per deployment: landing page, logo and colours. One app per OS for all your zones. |
| Rider accounts | YouYour own identity provider, so existing accounts work. | ShotlIntegrates sign-in with it; registration fields set to what you need. |
| Vehicles and drivers | YouYour fleet and drivers, or your operator’s. | ShotlReads drivers, vehicles, stops and zones from your systems instead of keeping a second copy. |
| Onboard hardware | YouThe units on board: CAN-bus or another OBU. | ShotlSoftware ready to integrate with them. Shotl does not supply the hardware. |
| Network data | YouYour GTFS feed. | ShotlCompatible with both, so the service sits inside your wider network. |
| Data and reporting | YouThe decisions: coverage, budget, the next zone. | ShotlActivity data with full detail, plus a query API with KPIs and real-time vehicle positions. |
How it works
What a city deployment looks like
Every city case on this page runs the same platform. A typical city starts with a simulation, launches one zone, and grows from the data.
Simulate the zone, size the fleet and build the business case your council can vote on.
- Draw the area, drop the stops, tell us the fleet
- A micro-simulation built on the figures you give us
- Graphs, KPIs, a fleet figure and a cost quote — walked through in a one-hour call
- 1 · Before launchFree simulation
Simulate the zone, size the fleet and build the business case your council can vote on.
- Draw the area, drop the stops, tell us the fleet
- A micro-simulation built on the figures you give us
- Graphs, KPIs, a fleet figure and a cost quote — walked through in a one-hour call
- 2 · In serviceDemand responsive
The end-to-end service: booking by app or phone, pooled routes, live operations.
- Riders book by app, web or phone — an operator can book on their behalf
- Ride now or schedule ahead, with a wheelchair field that follows the request
- Vehicles tracked in real time for riders and the control room
- 3 · Every quarterData and analytics
Coverage, waits and cost per trip — the numbers Torre Baró reports came straight from here.
- Activity data delivered with full analytical detail and mileage
- A query API exposing service KPIs, bookings and real-time vehicle positions
- Compatible with GTFS data, so it sits inside the network
Built to pass a tender
What a procurement team checks first
The requirements that come up in every public tender, and how the platform answers them.
- Your name on the serviceRun it under your own service name and trademarks, with your logo, colours and landing page.
- One app for every zoneOne app per operating system covering all the zones you integrate, showing only your service.
- Existing accounts sign inRider login through your own identity provider, with registration fields set to what you need.
- In your riders’ languagesFully configurable per language — Salento was delivered in Italian and English.
- Inside your networkCompatible with GTFS data, so it sits alongside your other lines.
- Your data, on requestActivity data delivered with full detail, plus a query API with KPIs and real-time vehicle positions.
- Hardware you already fitIntegrates with CAN-bus or another onboard unit. Shotl does not supply the hardware itself.
- Screen-reader readyThe rider app works with VoiceOver on iOS and TalkBack on Android.
ShuttleMare caters to all those who want to enjoy the beach and cannot get there.
— Roberta Frisoni, Councillor for Urban Planning and Mobility, Comune di RiminiSee what flexible transport would change in your area
FAQ
Questions cities and transit authorities ask
How do we start?
With a free first simulation. Sketch the service area, drop the stops and tell us the passengers and the fleet. We simulate it and walk you through a document with graphs, KPIs and a cost quote in a one-hour call — no commitment attached.
Can the service run under our own name?
Yes. A white-label licence lets you run it under your own service name and trademarks. The app’s landing page, logo and colours are set per deployment, and one app per operating system covers every zone you integrate.
How do riders book?
By app, on the web, or by phone — a call-centre operator can book on the rider’s behalf, which keeps the service open to people who don’t use digital tools. Trips can be booked to ride now or scheduled ahead.
Can riders change or cancel a trip?
Yes, within the policies set for the service. The rules are configurable per deployment rather than fixed by the platform.
Does it work with our existing network?
It is compatible with GTFS data, so the service can sit alongside the rest of the network. Rider sign-in can also run through your own identity provider.
What data do we get?
Activity data with full analytical detail and mileage, plus a query API exposing service status, bookings, KPIs and real-time vehicle positions for your own systems.
Do we need to buy hardware?
No new hardware is required from Shotl. The software integrates with onboard units you already fit, such as CAN-bus or another OBU — Shotl does not supply the hardware itself.
Proof
Related case studies
Demand responsive+1,000 /weekRimini
ItalyShuttleMare carried a thousand more passengers a week to the coast each season.
Read the case study
Dynamic bus line−15% mileageSant Vicenç de Montalt
SpainA bus line that keeps its spine but opens on-demand stops when requested.
Read the case study
Demand responsive−90% waitTorre Baró
SpainA steep, disconnected neighbourhood reached a 4.7/5 rider rating.
Read the case study