Software development for automotive and mobility

We build connected-vehicle dashboards, EV charging platforms, fleet telematics and over-the-air update systems that link vehicles to the cloud.

What the software has to handle

The constraints that shape architecture, security and delivery in this sector.

Real-time telemetry
Processing a constant stream of sensor data from connected vehicles.
Safe updates
Delivering firmware updates to vehicles in the field without leaving them inoperable.
Safety standards
Software components that have to fit into ISO 26262 safety processes.
Fleet scale
Monitoring and managing large fleets of vehicles at the same time.

What we build

Connected mobility depends on reliable data from the vehicle to the cloud and back. We build the telemetry pipelines, platforms and apps around it.

Connected dashboards
Real-time vehicle status, diagnostics and infotainment interfaces.
EV charging platforms
Station management, payment processing and grid load balancing for charging networks.
Fleet telematics
GPS tracking, driver behaviour scoring and predictive maintenance alerts.
Over-the-air updates
Secure, delta-based firmware delivery with rollback.
CAN bus integration
Embedded software that bridges vehicle bus systems and cloud platforms.

Typical first projects in automotive and mobility

Mobility companies rarely begin with a complete platform. They start with one link between vehicle, cloud and driver that has to work reliably, and build outwards from there.

Telematics ingestion from an existing TCU fleet
Taking data from telematics control units already fitted in vehicles, over MQTT or a supplier API, decoding binary or protobuf payloads and storing them for dashboards and analytics. Clock drift, duplicate messages and data buffered during coverage gaps make this harder than it looks. It usually starts with a discovery phase on a sample of real vehicle data.
OCPP backend for EV charge points
A charge-point management system that speaks OCPP 1.6J and 2.0.1, authorises sessions by RFID card or app, sends smart-charging profiles and firmware updates, and connects to roaming hubs through OCPI. Each charger model interprets the protocol slightly differently, so we test against the client’s hardware from the first sprint. A fixed-price MVP from €15k covers a first set of stations.
Driver companion app with remote commands
A React Native or native app for charging status, pre-conditioning, lock and unlock, trip history and service booking. Commands travel through the cloud to the vehicle and can fail without any visible error, so the app needs explicit pending and failed states and a record of who sent which command. Engineers often join the client’s existing mobile team.
Over-the-air campaign management console
The back office around software updates: targeting vehicles by model, hardware revision and software baseline, staged rollouts with automatic stop conditions, and reports that document each vehicle’s software state for UNECE R156 update-management obligations. A dedicated squad from €15k per month typically builds this alongside the manufacturer’s embedded team.
Fleet maintenance and fault-code dashboard
Turning OBD-II or J1939 diagnostic trouble codes, odometer readings and battery-health data into maintenance tasks for fleet managers, with links into workshop or ERP systems. The hard part is mapping manufacturer-specific codes to actions a dispatcher understands. Teams often begin with engineers at €45–65 per hour extending a fleet product they already run.

Questions to ask an automotive software development company

Automotive work crosses the boundaries between embedded systems, cloud and apps. These questions reveal whether a vendor knows where its responsibility starts and where it ends.

Which parts of the system fall under functional-safety processes, and who owns them?
Cloud dashboards and companion apps rarely sit inside the safety case, but anything that changes vehicle behaviour might. A good vendor maps each component against your safety and ASPICE processes, states which work it will do inside them, and leaves safety-relevant ECU software with the teams responsible for it.
How do you meet UNECE R155 cybersecurity requirements in the backend?
Expect specifics: mutual TLS between vehicle and cloud, per-vehicle certificate provisioning and rotation, signed update packages, keys held in a hardware security module or cloud KMS, and logs that feed your cybersecurity management system. Type approval stays with the manufacturer; the vendor should document the controls that support it.
How will you test without a full fleet on hand?
Ask about simulators that replay recorded CAN or telematics traces, hardware-in-the-loop benches provided by you or your supplier, and a small group of test vehicles for final checks. The answer should explain how edge cases such as lost connectivity or a low 12-volt battery are reproduced on demand.
What happens when connectivity drops during a command or an update?
Vehicles pass through tunnels, underground car parks and roaming borders. A sound design uses idempotent commands with an expiry time, store-and-forward buffering on the device, downloads that continue from where they stopped, and an explicit state machine for every update. Ask the vendor to walk through one failure scenario step by step.
Who owns the data model if we change hardware suppliers?
Telematics providers often keep data in their own formats. Ask whether signals will be normalised into a model you own, for example one aligned with the COVESA Vehicle Signal Specification, so that a new TCU or charger supplier means writing one adapter rather than rebuilding the platform.

Why companies choose elitics

The questions your legal, security and finance teams will ask, answered before the first line of code.

Intellectual property
NDA and IP assignment are signed before work starts. You own all code, designs and documentation.
Your environment
Engineers work in your repositories, ticketing and communication tools, under your access policies.
Quality controls
Code review on every change, automated tests and CI/CD on every project.
Visibility
Weekly sprint demos and progress reports, with a named lead accountable for delivery.
Continuity
If an engineer is not the right fit, we replace them at no extra cost.
Flexibility
Scale the team up or down month to month as your roadmap changes.

Common questions

Do you work on in-vehicle software or only on the cloud side?

Both, with a focus on connectivity: CAN bus integration and embedded bridges in the vehicle, and the telemetry, dashboard and fleet platforms in the cloud.

How do you make over-the-air updates safe?

We use secure, delta-based delivery with verification and rollback, so a failed update can return the vehicle to its previous working version.

Can you build an EV charging management platform?

Yes. We build station management, payment processing and load balancing for charging networks, with apps for operators and drivers.

Can you work with our Tier 1 supplier or telematics hardware vendor?

Yes. We generally take the hardware and its firmware as given and build against the interfaces the supplier provides: MQTT topics, REST APIs, DBC files describing CAN signals, or an SDK. Where an interface is undocumented, we agree a test plan with the supplier and record the decoded behaviour in your repository, so the knowledge stays with you rather than with us.

Is vehicle location data treated as personal data?

Usually, yes: under GDPR, location traces from a vehicle that an identifiable person drives count as personal data. We design for this with pseudonymised vehicle identifiers, coarse positions where exact points are not needed, retention limits and role-based access. Our team works from Kosovo, outside the EU, so its access is covered by Standard Contractual Clauses in the contract, and the data stays in your cloud accounts.

How does a project with an automotive software development company like elitics start?

With a call about the vehicles, hardware and systems involved, followed by a written proposal within 24 hours. Well-bounded pieces such as a charging backend or a companion app start as a fixed-price MVP from €15k. Open-ended platform work starts with a two-week trial of a dedicated squad from €15k per month; if you are not satisfied, you do not pay for those two weeks.

Let’s build what comes next.

Tell us what you need to build or scale. You will get a proposal and estimate within 24 hours.

Or write to us directly

hello@elitics.io+383 49 171 069

Dukagjini Center, Prishtina, Kosovo