Driveosplatform catalogue

Whose is what: company, platform and data

Why one platform can hold several companies, and what belongs to the company versus the platform. Explained without technical words, using DEMO-TAXI as the example.

Think of a building with several flats. The building is the platform: power, water, the lift and the roof are shared and nobody deals with them separately. A flat is the company: you live in it, you arrange it to your taste and you pay rent. A neighbour does not walk into your flat, and you do not touch their furniture.

LevelWhat it isExample
PlatformOwner of the system: companies, plans, modules, billing, monitoring, design systemDriveos
Company (tenant)A taxi association or carrier with its own brand and dataDEMO-TAXI, slug taxi-a
People and assetsOwner, dispatcher, operator, drivers, vehicles, passengersdriver D-014, vehicle ZG-1234-AB

Isolation between companies

All companies share one database, but they do not share data. Every record that belongs to a company carries a tenantId, and access is limited on two levels:

  1. Application check — the session carries the user’s company; no query accepts tenantId from the request, it always comes from the session.
  2. Row Level Security — PostgreSQL RLS only releases rows of that company, so even a code mistake stays inside the company.
  3. An API key belongs to one company — the same principle for server-to-server access; there is no parameter that selects a company.
Verified, not assumedIsolation is measured by dedicated checks (node web/tests/run.mjs groups company-isolation-check, platform-tenant-check, api-permissions-check): an attempt to read another company’s record must return 404, not 403.

Who owns what

ThingOwnerWhat it means
Rides, drivers, passengers dataCompanyNever mixed between companies
Brand: name, colour, logo, app iconCompanyEdited in the company console’s Brand studio
Store appsCompanyThe company is the publisher; store accounts are its own
Company slugCompany, permanentlyDefines the address and the app identity; it does not change after release
Price list, zones, ride rulesCompanyPrice is computed on the server, not in the app
Terms and privacyCompanyThe company fills the texts; the platform provides a template
System, modules, platform billingPlatformA module is enabled per company; core modules are always on

What the brand actually changes

A brand is not just a button colour. From the company’s data the platform derives the name inside the apps, the colour and its shades, the logo and icon, the app name on the home screen, the ride-tracking address, the e-mail signature and the look of the receipt.

FieldWhere it appearsChanges without a new build
Display nameApp headers, receipts, notificationsYes
Brand colourButtons, badges, map, UI accentsYes
Logo and iconSign-in, headers, store iconYes, except the store icon
App name under the iconPhone home screenNo — requires a new build and release
App bundle idStores, push, deep linksNo — permanent
A rule that is never brokenThe platform name inside the app may appear only next to the version number (e.g. “Driveos 1.0.7”), never as the product name shown to a passenger. The passenger sees the company, not the platform.

Roles and permissions

RoleScopeWhat it may do
OWNERCompanyEverything in the company, including brand, users, store releases and invoices
DISPATCHERCompanyRides, dispatch board, map, driver assignment
OPERATORCompanyPhone bookings and the call centre
ACCOUNTANTCompanyMoney: reports, payments, settlement
SUPER_ADMIN, ADMIN, SUPPORTPlatformCompanies, users, billing, monitoring — any access to ride data stays in the audit log

DEMO-TAXI in the examples

All examples, screenshots and code use one company: DEMO-TAXI, slug taxi-a, city of Zagreb, currency EUR, language hr. The price list has three service types (Standard, Comfort, Start), vehicles carry Zagreb plates, and driver names do not match real people.

jsonGET /api/public/companies/taxi-a — dio odgovora
{
  "company": {
    "slug": "taxi-a",
    "displayName": "DEMO-TAXI",
    "brandName": "DEMO-TAXI",
    "brandTagline": "Vaš grad, vaše ime.",
    "brandColor": "#4B63DD",
    "currencyCode": "EUR",
    "countryCode": "HR",
    "locale": "hr",
    "mapProvider": "MAPBOX",
    "rating": { "average": 4.9, "count": 284 },
    "serviceAreas": [
      { "label": "Zagreb", "center": { "latitude": 45.815, "longitude": 15.9819 }, "radiusMeters": 25000 }
    ]
  },
  "serviceTypes": [
    { "id": "a1", "name": "Standard", "meterMode": "KM", "paymentMethods": ["CASH", "CARD"], "seatCount": 4 },
    { "id": "a2", "name": "Comfort",  "meterMode": "KM", "paymentMethods": ["CASH", "CARD"], "seatCount": 4 },
    { "id": "a3", "name": "Start",    "meterMode": "KM", "paymentMethods": ["CASH", "CARD"], "seatCount": 4 }
  ]
}

That response is the entry point for both apps: before sign-in, the app learns the name, colour, language, maps and service types. That is why a brand change in the console takes effect immediately, without a new app version.