Built on a real fleet.
Rollio did not start as an idea in a slide deck. It started with vehicles that had to be rented, unlocked and billed correctly.
We built the system we needed ourselves first. Then we opened it to others.
Where the idea started
Rollio didn't start out as what you see today. The original idea was an ESPA-funded programme for rental electric cars. As we worked on it, the idea evolved: instead of one closed rental programme, we built a platform that could run any fleet, for any operator. That's how today's Rollio came to be.
We started with the hard part
Shared mobility looks simple until you try to operate it. The vehicle has to unlock reliably from a phone that may have poor signal. The driver has to be genuinely verified before a vehicle will open for them. And the charge has to come out right even when the battery runs out and the device stops sending a signal.
Those problems are not solved by gluing off-the-shelf tools together. So we built one platform where telematics, rentals, payments and verification are the same system.
From cars to anything that moves
The first version ran cars. When we added scooters, bikes and buggies we did not build a second system: same fleet, same management screen, same app — with a different unlocking mechanism underneath. That decision is why an operator can run all of them together today.
Then, other operators
When a second company asked to run its own fleet on the same platform, we rewrote the foundations. Each company now holds its own data, and the separation no longer depends on the application getting its checks right — the layer underneath enforces it. That is the difference between “it will not see the other company's data” and “it cannot”.
Who we are
Rollio is built in Xylokastro, Corinthia, Greece, by the same team that writes operations software for hotels and businesses — systems that have to work every day, not only in the demo.
See Rollio in action.
Half an hour is enough to walk the whole flow: vehicle, driver verification, unlock, charge.