Industry: Automotive

Software development for automotive

Software for the vehicle, the dealer, the charger and the supplier. We build connected vehicle and telematics platforms, EV charging backends, dealer and aftersales apps and supplier portals, and connect them to the DMS and ERP systems the business runs on. Senior engineers own the architecture, AI coding agents carry the volume, and every line is reviewed by a human.

Get a free assessment Generative AI in automotive

Key highlights

We build cloud and mobile software around the vehicle: telematics platforms, EV charging backends, dealer and aftersales apps and supplier portals.
We integrate with dealer management systems such as CDK, Reynolds and Reynolds, Keyloop and Dealertrack, and with SAP and other ERPs.
EV charging backends speak OCPP 1.6J and 2.0.1 to chargers and OCPI to roaming partners, with ISO 15118 Plug and Charge support where hardware allows.
Back end and update services are designed to support your UNECE R155 cybersecurity and R156 software update management obligations.
A focused first release, such as a service booking app on your DMS or a charge point backend for one network, usually ships in 8 to 12 weeks.

Industry challenges we solve

Automotive software now spans the car, the cloud, the forecourt and the supply chain. The hard part is rarely one system. It is making them agree.

DMS data locked in one vendor. Customer, vehicle, service and parts data sits in the dealer management system, and every new app or report needs a slow, costly integration through the vendor's certified program.

Telematics data with no product around it. Vehicles stream location, diagnostics and battery data, but it lands in a raw store nobody queries, so fleet, warranty and service teams never see it.

Chargers from five manufacturers. Each charger brand implements OCPP slightly differently, firmware updates break sessions, and roaming partners report failed authorisations you cannot reproduce.

Aftersales on phone calls and paper. Service bookings, vehicle health checks, approvals for extra work and warranty claims move by phone and paper, so retention and warranty recovery both suffer.

Supplier communication by spreadsheet. Forecasts, ASNs, quality issues and PPAP documents travel by email between OEMs and tier suppliers, and EDI only covers part of the network.

Cybersecurity rules that reach the cloud. UNECE R155 and R156 put obligations on the whole vehicle ecosystem, and back end services built without threat analysis or update controls become an audit finding.

Capabilities

Our automotive software capabilities

We build the cloud, mobile and integration layers around the vehicle, and leave safety critical embedded ECU software to the specialists you already use.

Dealer and DMS integration

Service booking, sales lead, digital retail and reporting apps connected to CDK, Reynolds and Reynolds, Keyloop or Dealertrack through their partner APIs, with data normalised across rooftops and brands.

Connected vehicle and telematics

Ingestion over MQTT and OEM data APIs, vehicle digital twins, trip and diagnostic event processing, geofencing and remote commands, with dashboards for fleets, service and warranty teams.

EV charging platforms

Charge point management on OCPP 1.6J and 2.0.1, smart charging and load balancing, roaming through OCPI 2.2.1, ad hoc payment, driver apps and ISO 15118 Plug and Charge integration.

Aftersales and warranty

Online service booking, digital vehicle health checks with photo and video, customer approval of extra work, parts lookup and warranty claim workflows with evidence checks before submission.

Supplier portals and EDI

Supplier portals for forecasts, call offs, ASNs, quality notifications and PPAP documents, integrated with EDIFACT, ANSI X12 and VDA messages and your SAP or other ERP.

Software update back ends

Campaign management, vehicle targeting, staged rollout and audit logging services for over the air updates, designed to feed the evidence your R156 software update management system needs.

How we deliver

From one use case to the whole ecosystem

01
Ecosystem and threat mapping
We map vehicles, chargers, dealers, suppliers and the systems between them, and run a threat analysis on anything that touches the vehicle. Output: an architecture and a ranked use case list.
02
Ship one use case
One production ready flow, such as service booking on the DMS or a charger backend for one site, built end to end and piloted with real users or hardware.
03
Integrate and harden
ERP, DMS, roaming and payment integrations, security testing and the documentation your cybersecurity and quality teams need for audits.
04
Scale and hand over
Roll out to more dealers, sites, vehicles or suppliers, add analytics on the data now flowing, and train your team to run the platform.

Compliance and security considerations

Automotive buyers expect suppliers to meet the industry's security, quality and safety frameworks. We design cloud and mobile software to support yours, and are clear about where specialist embedded work is needed.

UNECE R155 cybersecurity (CSMS) UNECE R156 software updates (SUMS) ISO/SAE 21434 ISO 26262 awareness TISAX information security IATF 16949 support OCPP and OCPI EU AFIR (charging) GDPR and UK GDPR

Vehicle connected services follow R155 and R156. Under UNECE R155 and R156, vehicle manufacturers must run certified cybersecurity and software update management systems covering the vehicle and its back end. We apply ISO/SAE 21434 style threat analysis, signed update packages, strong device identity and audit logs so our services fit inside your CSMS and SUMS.

Information security that OEMs recognise. Many OEMs require suppliers handling their data to hold a TISAX label based on the VDA ISA catalogue. We work inside your TISAX scope, follow your information classification and keep prototype and partner data in your environments.

Quality and safety boundaries are explicit. We support IATF 16949 traceability and supplier quality processes in the systems we build. Safety critical ECU software under ISO 26262 is specialist embedded work: we design cloud services with awareness of it and do not position ourselves as your functional safety supplier.

Tech stack we use for automotive

Open charging and messaging standards, scalable streaming in the cloud, and adapters for the DMS and ERP platforms the industry runs on.

OCPP 1.6J and 2.0.1 OCPI 2.2.1 ISO 15118 integration MQTT and AWS IoT Core Apache Kafka TimescaleDB and PostgreSQL CDK, Reynolds and Keyloop APIs EDIFACT, ANSI X12 and VDA SAP S/4HANA integration Java, Go and Node.js services Flutter and React Native apps Kubernetes on AWS and Azure

FAQ

Common questions

Do you build embedded ECU or safety critical software?

No. We build the cloud, mobile, dealer, charging and supplier software around the vehicle. Safety critical ECU software under ISO 26262 needs specialist embedded teams and tooling, and we integrate with that work rather than replace it.

Can you integrate with CDK, Reynolds and Reynolds or Keyloop?

Yes, through their partner programs and APIs. Access to DMS data usually requires enrolment in the vendor's integration program, which the dealer group or vendor arranges. We build the integration, normalise data across rooftops and handle the certification steps.

Which OCPP version should our chargers use?

OCPP 2.0.1 for new deployments where the hardware supports it, because it adds stronger security profiles, better device management and ISO 15118 support. Many installed chargers still run 1.6J, so our backends support both and let you migrate site by site.

How do your services support UNECE R155 and R156?

By building the back end to fit your CSMS and SUMS. We run threat analysis on vehicle facing services, use signed and versioned update packages, strong device identity, staged rollouts and full audit logs, and deliver the documentation your cybersecurity team needs. Type approval remains the vehicle manufacturer's responsibility.

How long does a first automotive project take?

Usually 8 to 12 weeks for one use case. That covers mapping, threat analysis and one production ready flow such as service booking on your DMS or a charge point backend for one network. Wider rollouts follow in phases.

Who owns the code and the vehicle data?

You do. Every engagement includes full IP assignment and an NDA, the code lives in your repositories, and vehicle, driver and customer data stays in your own cloud environment.

Keep exploring

Related services and industries

Free consultation, no commitment

Ready to connect vehicles, dealers and chargers?

Tell us about the use case and the systems involved. Written scope, timeline and cost estimate within 48 hours.

Book a free consultation All industries