Platform overview
One platform, four connected parts
Customers rent through the app, operators run the business from the management console, and vehicles are reached through a connected vehicle layer. The Ridee platform sits in the middle and keeps all three in sync.
Customer App
iOS and Android app for finding, unlocking and paying for a vehicle.
Ridee Platform
Rentals, pricing, customers, vehicles and tenant data in one backend.
Operator Management Console
Web console for fleet, rentals, customers, pricing and access control.
Connected Vehicles / IoT
Provider-based layer that carries commands and device data between Ridee and the vehicle — through Ridee IoT or supported third-party IoT.
Customer App
The app your customers rent with
An iOS and Android app that is part of the Ridee platform — it shares the same rentals, pricing and vehicle data your operators see in the management console. It can be published under your own brand.
01
Home
See vehicles on the map, tap one to view its battery and price.
02
Start ride
One tap starts the rental; time and price run live.
03
End & park
A photo of the parked vehicle is required to finish.
04
My rides
Every past ride with its vehicle, distance and price.
05
Payment methods
Saved cards and add card.
What is in the app today
- Phone number sign-in with a one-time SMS code
- New customer registration and secure sessions
- Map with the available vehicles
- Vehicle detail with battery level and price
- Payment methods: saved cards and adding a card
- Rental start from the vehicle detail
- Active rental with elapsed time and running price, restored after an app restart
- Mandatory end-of-rental photo
- Receipt, My Rides and ride detail with route and photos
- Profile
- Turkish, English, German, French and Spanish
Operator Management Console
Run daily operations from one console
The web management console gives your team a live view of vehicles, rentals and customers, and control over pricing and who can do what.
Every vehicle on a map with its current state, battery and lock status.
Dashboard and fleet map
See where vehicles are and what state they are in, updated live without refreshing.
Vehicle management
Add, edit, activate, deactivate and retire vehicles; mark them for maintenance.
IoT device management
Register IoT devices, assign them to vehicles, and replace or unassign them.
Telemetry and commands
Device telemetry and per-vehicle IoT command history: what was sent and what was acknowledged.
Rental operations
Rental list and detail with pricing and payment information, route and photos.
Customer management
Customer list and detail with rental history and a read-only view of saved cards.
Pricing and settings
Per-minute pricing and currency (TRY, EUR, USD or GBP) are configured per operator.
Users, roles and account security
Per-area permissions, password management, login lockout and authenticator-app MFA with recovery codes.
Lists support search, filtering, pagination and CSV export.
Fleet management
Know the state of every vehicle
Ridee keeps a registry of your vehicles and their operational state, so your team works from one source of truth.
Vehicle registry
Each vehicle has its own record with details and history.
Fleet map
See vehicle positions and states on a map.
Availability and state
Available, in rental, in maintenance or deactivated.
Maintenance state
Take a vehicle out of service and bring it back when ready.
Connected vehicle data
The assigned IoT device, telemetry and command history are shown on the vehicle record.
Rental management
Every rental, fully traceable
Open any rental and see what happened from start to finish.
- Customer
- Vehicle
- Rental status
- Start and end time
- Pricing
- Route
- End-of-rental photos
- IoT events
- Payment state
Payments run through a provider-independent payment layer; the production payment provider is selected and integrated per project.
Rental lifecycle
How a rental works
The same flow runs end to end across the app, the platform and the vehicle.
Find
Available vehicles on the map
Select
Vehicle and payment method
Unlock
Ridee sends the unlock command and waits for acknowledgement
Ride
Elapsed time and running price
End
Customer ends the rental
Photo
Required photo, then the vehicle locks
Receipt
Final price and ride history
Ridee IoT
Our own IoT solution for connected Ridee fleets.
Ridee is more than fleet and rental software. Depending on the vehicles and operational requirements of the project, we can also provide our own IoT solution — connecting the vehicle, the IoT hardware, the Ridee platform, the customer app and the operational tools within one solution architecture.
- Vehicle
- Ridee IoT
- Ridee platform
- App & console
Supported vehicle-control functions can be configured according to the vehicle and controller architecture used in the project.
Our IoT solution or yours
Ridee IoT is an option, not a requirement. Ridee stays hardware-independent: supported third-party devices, IoT platforms and project-specific integrations run on the same platform.
See IoT integrationsBuilt for Ridee
Designed to work with the Ridee platform, management console and customer app.
Vehicle-to-platform link
Connects the vehicle to the Ridee platform for device data and commands.
Telemetry and fleet visibility
Device data feeds the fleet map, vehicle records and operational screens.
Device management
Devices are registered, assigned to vehicles and followed in Ridee device management.
Part of the rental lifecycle
Works within the Ridee rental flow, from the start of a rental to its end.
Project-specific vehicle integration
Integration with the vehicle and its controller is configured for each project.
Connected vehicles / IoT
Your hardware choice. One Ridee integration layer.
Ridee is hardware-independent. Use Ridee IoT, a supported third-party device or IoT platform, or have us integrate the hardware you already have — the rental experience stays the same.
Ridee IoT
Our own IoT solution
Teltonika
FTC305 · TFT100 direct device integration
Comodule
IoT platform integration
Custom IoT
Project-specific device and controller integrations
No hardware lock-in
Ridee IoT is optional; the rental platform is not hard-coded to any one hardware manufacturer.
Different devices in one fleet
Each vehicle is assigned its own IoT device and provider, so vehicles of the same operator can use different IoT solutions.
Need another IoT provider?
The provider-based architecture is designed for additional hardware and platform integrations, without rewriting the rental platform.
Consistent rental experience
Customers and operators see the same flow whichever device is on the vehicle.
What the layer is designed to carry
- Location / GPS
- Connectivity
- Telemetry
- Battery
- Vehicle commands
- Command acknowledgement
- Device status
Teltonika FTC305 and TFT100 are integrated directly at device level, and both can run side by side in one fleet. Comodule is integrated as an IoT platform through the Comodule Server API. Validation with the actual vehicles, controllers and devices is carried out per project. Vehicle-control functions such as lock and unlock depend on the vehicle, its controller, the IoT device and the project-specific integration.
IoT integrations
Ridee IoT
- Type
- First-party IoT solution
- Software status
- Native Ridee solution
- Validation
- Vehicle and controller setup per project
Teltonika FTC305
- Type
- Direct device integration
- Software status
- Implemented
- Validation
- Physical vehicle / controller validation per project
Teltonika TFT100
- Type
- Direct device integration
- Software status
- Implemented
- Validation
- Physical vehicle / controller validation per project
Comodule
- Type
- IoT platform integration
- Software status
- Implemented through the Comodule Server API
- Validation
- Cloud / device validation per project
Custom IoT
- Type
- Project-specific integration
- Software status
- Developed to project requirements
- Validation
- Per project
Payment integrations
The payment provider is chosen per project
Production payment infrastructure is selected according to the market and the operator's requirements, and integrated as part of the project through Ridee's provider-independent payment layer. The providers below are integration options, not existing live connections.
iyzico
Turkey
Project-based integration option
PayTR
Turkey
Project-based integration option
Param
Turkey
Project-based integration option
Sipay
Turkey
Project-based integration option
Custom payment provider
International / project-specific
Integrated to project requirements
Payment features such as 3D Secure, card storage, refunds and payment notifications depend on the selected provider and are scoped with that integration.
Vehicle types
Designed for more than scooters
Ridee is built to support short-term rental of different connected vehicles on the same platform.
E-scooters
E-bikes & bicycles
Motorcycles & mopeds
Cars
Snowmobiles & snow scooters
Other connected rental vehicles
Suitability for a specific vehicle depends on its connected device and controller. We review this with you during the demo.
Platform foundations
Built for operators, teams and tenants
Realtime operations
Management console screens receive live operational updates as rentals and vehicle states change.
Access and security
Phone + one-time code sign-in for customers, role-based management console access with permissions, and protected customer media.
Multi-tenant by design
Each operator works in its own isolated tenant with its own vehicles, customers, pricing and users.
Languages and currencies
The customer app and management console are available in Turkish, English, German, French and Spanish. Pricing supports TRY, EUR, USD and GBP.
Deployment
Ridee as a service
Ridee is delivered as SaaS on Ridee Cloud. No servers to set up, no infrastructure to maintain — you focus on your fleet.
Ridee Cloud
SaaSYour operation runs as its own isolated tenant on the Ridee platform, hosted and operated by Ridee.
- No servers or installation on your side
- Your own isolated tenant
- Product updates and maintenance by Ridee
- The same Ridee platform for every operator
Security built in
Isolated tenant data
Vehicles, customers, rentals, devices and users are kept per tenant; one operator never sees another's data.
Two-factor sign-in
Management console users can protect their accounts with authenticator-app (TOTP) codes and one-time recovery codes.
Roles and permissions
Each team member only sees and changes what their role allows.
Login lockout
Accounts lock after repeated failed sign-in attempts.
Secure sessions
Customers sign in with a phone number and one-time SMS code; operators manage their own passwords, and a password change ends existing sessions.
Protected customer media
End-of-rental photos are served only to the customer who took them and authorised console users.
Packages
Packages that follow the stage of your business
Core Ridee functionality is the same in every package. What changes is operational complexity, integration and IoT requirements, onboarding and support. Pricing is agreed per project.
START-UP
For operators launching or validating a shared mobility operation.
The complete Ridee platform on Ridee Cloud with a standard setup.
- Customer App and Operator Management Console
- Core rental lifecycle
- Fleet, vehicle, customer and rental management
- Pricing configuration
- Ridee IoT or a supported IoT integration
- Ridee Cloud deployment
- Standard onboarding and support
SCALE-UP
For established operators expanding their fleet, markets or integration complexity.
Everything in START-UP, with more help on integrations and operations.
- Support for more complex fleet operations
- Advanced roles and permissions setup
- Multi-provider and more complex fleet integration requirements
- Additional integrations with integration assistance
- Expanded operational configuration
- Assisted onboarding
- Priority support
ENTERPRISE
For larger organisations with custom IoT and controller integrations or business-system integrations.
Everything in SCALE-UP, shaped around your organisation.
- Custom IoT, OEM and vehicle-controller integrations
- Custom business integrations
- Tailored configuration
- Enterprise onboarding and implementation assistance
- Enterprise support arrangements
Compare packages
| Capability | START-UP | SCALE-UP | ENTERPRISE |
|---|---|---|---|
| Customer App | Included | Included | Included |
| Operator Management Console | Included | Included | Included |
| Fleet management | Included | Included | Included |
| Rental management | Included | Included | Included |
| Pricing & currency settings | Included | Included | Included |
| Realtime operations | Included | Included | Included |
| Localization (5 languages) | Included | Included | Included |
| Currencies (TRY, EUR, USD, GBP) | Included | Included | Included |
| Your brand on the customer app | Available | Available | Available |
| Users / roles / permissions | Standard | Advanced | Advanced |
| Connected vehicles / IoT | Standard | Multi-provider | Custom / OEM |
| Integration support | Standard | Assisted | Tailored |
| Custom business integrations | — | Optional | Available |
| Onboarding | Standard | Assisted | Enterprise |
| Support | Standard | Priority | Custom arrangement |
Frequently asked questions
Ridee is a shared mobility and short-term vehicle rental platform. It consists of a customer mobile app, an operator management console, a rental backend and a provider-based connected vehicle layer.
E-scooters, e-bikes and bicycles, motorcycles and mopeds, cars, snowmobiles and other connected rental vehicles. Suitability for a specific vehicle depends on its connected device, which we review with you.
Ridee uses a provider-based IoT architecture, so the rental platform is not tied to one manufacturer and different integrations can coexist in the same fleet. Options include our own Ridee IoT solution, direct integration with Teltonika FTC305 and TFT100 devices, and Comodule through its IoT platform integration. Remote vehicle commands depend on the capabilities of the selected IoT hardware and the vehicle controller. Other providers and OEM hardware are handled as integration work per project.
No. Ridee IoT is an option for projects that want software and connected-vehicle hardware from one team. You can also use supported third-party IoT devices and platforms, or have your existing hardware integrated as part of the project.
Yes. The customer app can be published under your brand as part of your Ridee setup.
No. Ridee is delivered as SaaS on Ridee Cloud: hosting, maintenance and product updates are handled by Ridee, and your operation runs in its own isolated tenant.
Ridee has a provider-independent payment layer. The production payment provider is selected according to your market and requirements — for example iyzico, PayTR, Param or Sipay in Turkey, or your existing provider — and integrated as part of the project.
The customer app and management console are available in Turkish, English, German, French and Spanish. Pricing supports TRY, EUR, USD and GBP.
There is no public price list. Packages are scoped to your operation and we prepare a proposal after a demo.
Planning or growing a shared mobility operation?
Let's look at Ridee together.
