ONARLY DRIVE

The complete operating platform for taxi and mobility companies.

In development

One platform for bookings, dispatch, drivers, customers, payments and settlement — with a customer app, a driver app, web booking and an admin / dispatch application on one shared backend.

ONARLY / ONARLY DRIVE
01 / WHAT IT IS

The complete operating platform for taxi and mobility companies.

ONARLY DRIVE is the complete taxi and mobility operating platform. It connects every part of a taxi company's day: customers booking in the QabGo app or on the company's website, dispatch reviewing and assigning trips, drivers receiving and completing jobs in the ONARLY Driver app, and payments, receipts and settlement flowing through to accounting. Every surface works on the same shared backend, so the booking the customer sees is the booking dispatch controls and the job the driver completes.

02 / PRODUCT STRUCTURE

One platform. Four surfaces. One backend.

ONARLY DRIVE is the platform. Each surface serves one party in the trip, and all of them work on the same shared booking data.

PLATFORMONARLY DRIVE

The complete taxi and mobility operating platform

SHARED BACKENDShared ONARLY DRIVE backend

One platform behind every surface: bookings, pricing, users, drivers, payments, statuses and business logic. A booking made in QabGo, on the website or by dispatch is the same booking everywhere.

  • Bookings
  • Pricing
  • Users
  • Drivers
  • Payments
  • Statuses
  • Business logic
03 / WHO IT IS FOR

Taxi operations should not depend on systems that do not talk to each other.

Taxi companiesMobility and transport operatorsRegional operators with contracted driversOperators who want a branded customer experience
The problem it solves

Many operators combine a booking form, a separate dispatch system, a driver app from another vendor, manual receipts and spreadsheet settlement. Every handoff is a chance for a wrong price, a lost booking or a driver paid incorrectly. DRIVE puts the whole trip on one platform.

04 / HOW YOU WORK WITH IT

The work, step by step.

  1. 01

    Customers book

    Through QabGo or the booking form on the company website.

  2. 02

    Dispatch controls

    Admin / Dispatch reviews, prices and assigns bookings and manages drivers and fleet.

  3. 03

    Drivers deliver

    ONARLY Driver receives the job, guides the trip workflow and records the completion.

  4. 04

    Money settles

    Payment or invoice, receipt, driver settlement and handoff to accounting.

05 / WORKFLOW

One booking, from request to settlement.

Every step happens on the same shared booking, so customer, dispatcher and driver always see the same state.

  1. 01Customer booksIn QabGo or on the company websiteQabGo / WP Plugin
  2. 02Booking receivedStored in the shared backendBackend
  3. 03Admin reviews / approvesChecked by dispatch where requiredAdmin / Dispatch
  4. 04Driver assignedDispatch or automated assignmentAdmin / Dispatch
  5. 05Driver receives jobPushed to the driver appONARLY Driver
  6. 06Driver acceptsCustomer sees the updateONARLY Driver
  7. 07Trip startsStatus shared with customer and dispatchONARLY Driver
  8. 08Trip completedFinal fare recordedONARLY Driver
  9. 09Payment / invoicePaid, or invoiced to a business accountBackend
  10. 10ReceiptDelivered to the customerQabGo
  11. 11Settlement / accountingDriver settlement and bookkeepingAdmin / OPERA
Approval and assignment rules depend on how each company configures its operation.
06 / CORE CAPABILITIES

What it does.

In development. A beta run from QabGo booking through dispatch and the driver app to OPERA settlement has passed end to end in a development environment; production release is pending.

01Quotes and bookings API
02Booking workflow with approval and assignment
03Driver offers with a two-minute window
04Dispatch application
05Customer app (QabGo and white-label)
06Driver app with live GPS
07Final fare and taximeter gateway
08Trip status for every party
09Web booking for WordPress sites
10Settlement handoff to OPERA when a trip completes
Product principle

One trip. One truth.

The customer, the dispatcher and the driver all work on the same booking in the same backend. There is no second copy to drift out of sync.

07 / CONNECTS WITH

Useful alone. Stronger connected.

Connections are optional. Each link below explains what the combination adds.

BusinessOPERA

Hand payments, receipts and settlement to commerce and accounting.

BusinessONARLY WEBSITE BUILDER

Give the operator a public website with booking built in.

Integration directionPayments

Card and digital payments through connected payment providers, depending on configuration.

Integration directionAccounting

Trip revenue, receipts and settlement structured for bookkeeping.

Integration directionWebsites

Booking on existing WordPress sites through the ONARLY Driver – WP Plugin.

Integration directionWhite-label customer experience

The customer app and booking experience under the operator's own brand.

08 / COMMERCIAL MODEL

How it is priced.

ONARLY DRIVE is the platform. Admin / Dispatch, ONARLY Driver, QabGo and the ONARLY Driver – WP Plugin are connected surfaces using the shared DRIVE platform and backend — they are not priced as four competing subscriptions. DRIVE Core starts from 399 SEK / month plus applicable transaction and usage fees. Exact packaging may evolve.

What is included
  • ONARLY HUB workspace access
  • Admin / Dispatch
  • ONARLY Driver (driver app)
  • QabGo (customer app)
  • ONARLY Driver – WP Plugin
  • Shared DRIVE backend
Core framework tierFrom 399 SEK/ month + applicable transaction and usage fees
Billing unit
Per taxi company / operating platform + applicable transaction and infrastructure usage
Built from
  • Base licence per taxi company / operating platform
  • Access to all connected DRIVE surfaces
  • Higher packages for advanced operations, branding and scale
Usage charges
  • SMS notifications
  • Map, routing and geolocation API usage
  • AI processing (credits) where used
Transaction fees
Transaction fees depend on payment and platform configuration.
See the full ONARLY pricing model→

DRIVE Core

Core framework tierFrom 399 SEK/ month + applicable transaction / usage fees

The DRIVE platform with its connected surfaces.

  • Admin / Dispatch
  • ONARLY Driver
  • QabGo
  • ONARLY Driver – WP Plugin

DRIVE Pro

PricingPricing on request

For operators that need more than day-to-day dispatch.

  • Advanced operations
  • Automation
  • Reporting
  • Contractor and driver economics
  • Broader integrations

DRIVE White Label

PricingAdd-on · pricing on request

The customer experience under the operator's own brand.

  • Customer-facing branding
  • Branded customer app / site experience
  • Custom domain and identity options

DRIVE Enterprise

PricingContact ONARLY

For larger fleets and advanced deployments.

  • Custom integrations
  • Larger fleets
  • Dedicated infrastructure / SLA
  • Advanced deployment requirements
09 / CURRENT STATUS

Where it stands today.

In development

ONARLY DRIVE is in development. Public availability and individual module rollout will be announced separately.

Family: Mobility

Roadmap direction
  • Shared DRIVE backend and booking model
  • Standalone Admin / Dispatch application
  • QabGo customer app
  • ONARLY Driver app
  • ONARLY Driver – WP Plugin on the shared backend
  • OPERA accounting handoff
  • White-label customer experience
10 / FAQ

Questions about DRIVE.

01Are ONARLY DRIVE and ONARLY Driver separate platforms?

No. ONARLY DRIVE is the platform. ONARLY Driver is the driver mobile app inside it, alongside Admin / Dispatch, QabGo and the ONARLY Driver – WP Plugin.

02Do I pay separately for each app?

No. DRIVE Core gives the operator access to the connected surfaces. Exact packaging may evolve.

03What does DRIVE Core cost?

DRIVE Core starts from 399 SEK / month plus applicable transaction and usage fees. Transaction fees depend on payment and platform configuration.

04Can DRIVE connect to our accounting?

DRIVE is designed to hand payments, receipts and settlement to OPERA and onward to accounting. Other accounting connections depend on configuration.

05Can customers see our brand instead of QabGo?

That is what DRIVE White Label is for: customer-facing branding, a branded app / site experience and custom domain and identity options.

ONARLY Systems

Talk to ONARLY about DRIVE

Tell us how your current operation works and where the difficult handoffs happen.

Request accessJoin the beta