We build connected vehicle, dealer, EV charging and fleet platforms for automotive companies across the UAE. Our Dubai-based engineers know RTA and Salik integration, write code that handles real telematics flow, and have shipped to live fleets running thousands of vehicles in production.
Mobility software has two audiences: the fleet operator who needs every vehicle visible right now, and the driver who needs the app to just work. We build for both from sprint one.
Most engagements pair one platform build with two or three add-on services.
Telematics ingestion, vehicle state, trip history and driver-facing apps for OEMs and fleet brands.
Live fleet view, utilisation reports, driver scoring and maintenance workflows your ops team trusts.
Lead capture, test-drive booking, deal flow and DMS sync for showroom and online sales.
OCPP-compliant charger management, session billing, roaming and driver apps for UAE EV operators.
Ride-hailing, car-sharing and subscription apps with payments, identity and dispatch on commodity cloud.
Tolling, registration, charging-network and city-mobility APIs wired in cleanly, with the edge cases handled.
These are ranges from real engagements. We measure them because retainers depend on them.
Default target for the platforms we ship, on standard cloud (AWS Bahrain region) with MQTT and Kafka.
OCPP backends with proper retry, idempotency and session reconciliation. Drivers stop seeing 'session failed' errors.
From kickoff to a real-time fleet view with vehicle state, trips and exceptions for thousands of vehicles.
Where dispatch, idle detection and maintenance scheduling are automated. Operators move from paperwork to decisions.
We pick stacks proven on real fleets. High throughput where it matters, low overhead everywhere else.
MQTT and AWS IoT Core for vehicle messages. Kafka for downstream fan-out. Backpressure and dead-letter queues from day one.
TimescaleDB and InfluxDB for telemetry history. Postgres for current vehicle state and bookings. ClickHouse where the query volume needs it.
OCPP 1.6 and 2.0.1 backends in Go. Session reconciliation, tariff engines and eMSP roaming adapters that pass real-world certification.
React Native and Flutter for driver and operator apps. React for fleet web. Offline-first patterns for areas with patchy signal.
AWS Bahrain for UAE-region work. Terraform, Datadog and PagerDuty for the operational layer. Cost dashboards because telematics bills surprise people.
Pricing shared openly during scoping. Smallest engagement starts around the cost of one senior in-house hire.
A two-week review of your telematics platform, data flows and dealer or charging integrations before scale-up.
Dealers, OEMs and EV operators preparing for fleet growth or a major platform upgrade
A senior pod shipping vehicle, fleet and driver-app features alongside your team each sprint.
Dealers, EV networks and fleet operators shipping new products, regions or integrations
We own your telematics pipelines, charger backends and ops dashboards on a monthly retainer.
Live operators past go-live who want one steady partner for mobility engineering
Mobility platforms live or die by a few decisions made in the first quarter. We focus there and leave clever for the analytics layer.
Vehicles drop signal in tunnels and parking basements. Our ingestion pipelines accept events with old timestamps, reorder them in the time-series layer, and never overwrite newer state with stale data.
A vehicle can ask for the same update twice, or report success after a network blip. Our OTA pipelines treat re-delivery as normal, track versions per VIN, and never push a partial bundle.
OCPP messages can arrive late, twice or out of order. Sessions, meter values and billing reconcile continuously. Driver disputes drop to almost zero.
-- Row-level tenant isolation.
-- One schema, many tenants, zero "where did this data leak from" tickets.
ALTER TABLE invoices ENABLE ROW LEVEL SECURITY;
CREATE POLICY tenant_isolation ON invoices
USING (tenant_id = current_setting('app.tenant_id')::uuid);
-- Application sets the tenant for every connection.
-- If we forget, the query returns zero rows, not someone else's.
SET LOCAL app.tenant_id = '8f3a-...-c1';
SELECT id, amount_cents, status
FROM invoices
WHERE status = 'pending'
ORDER BY created_at DESC
LIMIT 25;
An example of per-fleet tenant isolation we apply to vehicle and session data. The same principle underpins our segregated telematics pipelines for multi-brand operators.
Walk the depot or showroom (in person or remotely), read the telematics feeds, talk to drivers, dispatchers, dealers and ops. We listen for the breaks that always happen on Monday mornings.
Milestones, risks, and what we would do first. Including the work we would recommend you do not do this quarter.
Our senior pod is in your repos shipping production features. Your team owns the merges, we own the cadence.
Measured against the outcomes we agreed on. The people who start with you are the same people in month six.
SKIMBOX rebuilt our telematics pipeline and fleet dashboard in one quarter. Our dispatchers stopped working from a spreadsheet, and we now see every vehicle in the fleet within two seconds of an event.
Manual prep replaced by a real-time fleet view.
Dispatch now sees position and status essentially live.
Across three quarters since we rebuilt the OCPP backend.
Yes. Our team has shipped tolling, registration and charging-network integrations for UAE operators. We work alongside your ops counsel, build the audit trails inspectors look for, and rehearse the integration changes before they happen.
Tell us what is slipping on the fleet, what is breaking at the chargers, and what your dealer team is bracing for. Written plan in two weeks, or an honest 'we are not the right team'.