Skip to content

Your charging network, under your name

Run the MileUp platform, consoles and driver app as your own: your brand, your tariffs, your payment account and your TRN on every invoice. One codebase for every operator, never a fork.

Talk to us about onboardingSee the modules

Switch on what you need

Every module is enabled per operator by configuration. Turning one off hides its screens, blocks its APIs and keeps its data.

  • Core

    Always on

    Identity, tenants, assets, OCPP central system, session engine, tariffs, CDRs, ledger and audit.

  • Driver app

    Per operator

    iOS and Android: map, booking, charging, payment, receipts and support.

  • Guest web

    Per operator

    Scan a QR code, pay by card and charge, with no account.

  • Owner console

    Per operator

    Sites, chargers, tariffs, revenue share, exports and sub-roles.

  • NOC console

    Per operator

    Network view, incidents, tickets, command desk and KPIs.

  • Fleet console

    Per operator

    Organisations, drivers, vehicles, cards, quotas and invoices.

  • Edge

    Per operator

    A local OCPP gateway that keeps sites running offline and syncs later.

  • Booking and payments

    Per operator

    Reservations, pre-authorisation, invoices, refunds and settlement.

  • Roaming

    Per operator

    OCPI 2.3.0, as charge point operator and as e-mobility service provider.

  • Energy

    Per operator

    Site power caps, load sharing, and sites with solar or batteries.

  • Marketplace

    Per operator

    An equipment storefront for your own buyers, on the same checkout.

  • Partner API

    Per operator

    REST, webhooks, a sandbox and OAuth for your integrations.

A branded app without a branded codebase

Your iOS and Android apps are produced from the shared codebase by configuration: bundle ID, name, icons, colours, fonts, strings and enabled modules.

  1. Built and signed in CI

    A new operator app builds, signs and uploads to the App Store and Google Play test tracks in one run.

  2. Published under your accounts

    Your developer accounts and your store listings, with listing text and screenshots in English and Arabic.

  3. Changed without a release

    Modules, map layers, payment methods and feature flags load at start-up, so most changes need no store update.

  4. Updated together

    Fixes reach every operator app at once, with staged rollout and rollback.

Your money, your tax identity

  • Your payment account

    Driver payments settle to you as a sub-merchant. The platform fee is split automatically and recorded in the ledger.

  • Your TRN on every invoice

    Receipts and tax invoices carry your legal name and TRN, in English and Arabic.

  • Isolated by design

    Your data, users, prices and money are kept apart from every other operator, and tested for leaks.

  • Your call on the public map

    Choose whether your stations appear on the MileUp map and app, and on what terms. It stays off until you agree.

  • Export and exit

    A full data export in documented formats, whenever you need it.

From contract to live

The path every operator follows. Most of it is configuration, not code.

  1. Provision your tenant

    Created from a template with its own admin, data scope and audit trail. No code, no deploy.

  2. Brand and domain

    Logo, colours, fonts, copy, receipt templates and your own domains with managed certificates.

  3. Payments and tax

    Connect your payment account and tax identity, so money and invoices are yours from day one.

  4. Import sites and chargers

    Bring existing sites and chargers across, or commission new ones bought on the marketplace.

  5. Build your app

    Your branded apps build from the shared codebase and go to store review.

  6. Go live

    Switch on the modules you need and open to drivers.

Launching a charging brand?

Tell us about your network: sites, chargers, the emirates you cover and the modules you need.

Talk to us about onboardingContact sales