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.
| Level | What it is | Example |
|---|---|---|
| Platform | Owner of the system: companies, plans, modules, billing, monitoring, design system | Driveos |
| Company (tenant) | A taxi association or carrier with its own brand and data | DEMO-TAXI, slug taxi-a |
| People and assets | Owner, dispatcher, operator, drivers, vehicles, passengers | driver 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:
- Application check — the session carries the user’s company; no query accepts
tenantIdfrom the request, it always comes from the session. - Row Level Security — PostgreSQL RLS only releases rows of that company, so even a code mistake stays inside the company.
- An API key belongs to one company — the same principle for server-to-server access; there is no parameter that selects a company.
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
| Thing | Owner | What it means |
|---|---|---|
| Rides, drivers, passengers data | Company | Never mixed between companies |
| Brand: name, colour, logo, app icon | Company | Edited in the company console’s Brand studio |
| Store apps | Company | The company is the publisher; store accounts are its own |
| Company slug | Company, permanently | Defines the address and the app identity; it does not change after release |
| Price list, zones, ride rules | Company | Price is computed on the server, not in the app |
| Terms and privacy | Company | The company fills the texts; the platform provides a template |
| System, modules, platform billing | Platform | A 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.
| Field | Where it appears | Changes without a new build |
|---|---|---|
| Display name | App headers, receipts, notifications | Yes |
| Brand colour | Buttons, badges, map, UI accents | Yes |
| Logo and icon | Sign-in, headers, store icon | Yes, except the store icon |
| App name under the icon | Phone home screen | No — requires a new build and release |
| App bundle id | Stores, push, deep links | No — permanent |
Roles and permissions
| Role | Scope | What it may do |
|---|---|---|
OWNER | Company | Everything in the company, including brand, users, store releases and invoices |
DISPATCHER | Company | Rides, dispatch board, map, driver assignment |
OPERATOR | Company | Phone bookings and the call centre |
ACCOUNTANT | Company | Money: reports, payments, settlement |
SUPER_ADMIN, ADMIN, SUPPORT | Platform | Companies, 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.
{
"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.