Keeping fleet vehicles updated sounds straightforward until you realize those vehicles are never in one place, never on a reliable connection, and can’t be taken offline every time a map layer changes or a software patch ships. For operations where uptime is non-negotiable, unplanned downtime to push an update isn’t an option.
For IT leaders and fleet managers supporting fire departments, EMS teams, or any mobile operation, over-the-air updates are the only practical path. But most distribution tools weren’t built for this environment. They were built for endpoints that sit on Ethernet, stay connected, and don’t drive through canyons.
And it isn’t only a public-safety problem. If you build or operate a distributed platform with edge components such as retail sites, industrial gateways, IoT fleets, or actual vehicles, the underlying challenge is identical: keeping configuration, models, and artifacts consistent across nodes you can’t count on reaching, without routing every transfer through a central server. A fire engine driving through a canyon is just an unusually hostile edge node. The connectivity is worse, the files are bigger, and the stakes are higher, but the failure mode is the one every platform engineer knows: a transfer that dies at 89% and starts over from zero when the link comes back.
This post covers what makes OTA updates for fleet vehicles genuinely difficult, what to look for in a distribution platform, and how one public safety technology company solved it in production across real fleets with thousands of vehicles.
Watch the full webinar on fleet data sync for first responders to see this in action, or read on for the full breakdown.
The Problem with Traditional Software Distribution for Moving Fleets
Most enterprise software distribution tools make a core assumption: the endpoint is reachable, connected, and stationary. That assumption breaks completely when the endpoint is a fire engine.
Fleet vehicles operate on wireless connections only, LTE, 4G, 5G, and satellite, and they switch between them constantly depending on location and availability. Coverage drops mid-transfer. Vehicles power down unexpectedly. A unit that was online when a job started may be offline an hour later and back online two days after that.
Traditional download tools handle this poorly. When a connection drops mid-transfer, most restart the update process from zero when the connection returns. For a small configuration file, that’s a minor inconvenience. For a full-state GIS map that runs hundreds of megabytes, it means a vehicle can attempt and fail a download dozens of times without ever completing it.
“I may be on 5G and have hundreds of megabytes available. Then I drive through a canyon in the Sierras, and I get close to zero. A lot of traditional download systems start to download, the network gets disrupted, they cancel it, and when the network comes back, you start over again.”
— Petr Peterka, CTO, RadioMobile
The operational consequences compound over time. Software release cycles slow down because IT can’t reliably push updates. GIS teams produce updated map layers that never reach the vehicles that need them. Pre-plans for new buildings are stored on a server, while crews in the field work from outdated information.
What a Reliable OTA Fleet Update Platform Actually Requires
RadioMobile, a public safety technology company that builds mobile data management systems for fire and EMS fleets, evaluated several platforms before building its IQ OTA distribution service on Resilio Active Everywhere. Their criteria translate into a portable evaluation checklist: if you’re assessing distribution for any distributed edge platform, such as vehicle fleets, retail and industrial sites, IoT gateways, or remote nodes, these are the four non-negotiables.
Fault-tolerant delivery over unstable networks: edge resilience as a property. Transfers have to survive dropped connections without restarting. The platform tracks exactly how much of a file has been delivered, holds that state when the link drops, and resumes from that precise point when the node reconnects, whether the node is a fire engine in a canyon or an edge gateway on congested cellular backhaul. A degraded or disappearing connection pauses progress instead of erasing it.
Support for large files. GIS maps for an entire state, software executables, firmware, and pre-plan packages are not small files, and neither are the build artifacts, container images, ML models, and datasets a platform team pushes to the edge. The platform has to move hundreds of megabytes to gigabytes reliably across links that can degrade or vanish mid-transfer.
Peer-to-peer distribution for scale. When you’re pushing to thousands of nodes, vehicles, sites, or gateways, spread across a wide footprint, routing every transfer through a central server creates a bandwidth bottleneck and runs up egress costs. A peer-to-peer model lets nodes that already have a file serve it to nearby nodes directly, instead of sending every copy from the origin, so rollout time stops scaling with node count.
Two-way data flow: observability for the edge. Distribution is only half the picture. Operators also need to pull data from the edge, such as log files, metrics, telemetry, and usage statistics, to diagnose issues remotely and track performance over time. That return path is the observability layer for a distributed edge footprint: the same job-based system that pushes artifacts out also collects the operational data that tells you whether the edge is healthy.
How Chunk-Based, Peer-to-Peer Transfer Solves the Core Problem
Where traditional MDM and file distribution tools are built for managed, always-on endpoints, Resilio Active Everywhere was designed from the ground up for environments with unreliable connectivity and moving endpoints.
The platform breaks files into small, cryptographically verified chunks. Each chunk is transferred and confirmed independently. If a connection drops mid-transfer, only the undelivered chunks need to be retransmitted when the connection returns. There is no full restart, no manual intervention, and no dependency on the connection staying stable for the duration of a large transfer.
Resilio’s peer-to-peer architecture means vehicles don’t all have to pull from a central server. Once a subset of agents at a fire station has received a file, they can serve it to nearby units directly over local networks. For a department with hundreds or thousands of vehicles, that difference in distribution model translates directly into faster fleet-wide updates, less downtime waiting on transfers to complete, and lower infrastructure overhead.
“The way Resilio works, it uses peer-to-peer networking, where I deliver the file to one fire engine at a fire station. If there are three other engines around, they can deliver it to each other and share local networks, as opposed to requiring an expensive data center.”
— Petr Peterka, CTO, RadioMobile
Inside Resilio Active Everywhere: What the Admin Experience Looks Like
In the RadioMobile deployment, fleet operators manage distribution through a job-based interface built on Resilio’s management console. An admin selects the files to distribute, identifies the target group of vehicles, sets a delivery schedule if needed, and the system handles the rest.
The console provides end-to-end visibility into every step: how many agents are active, how many are offline, how much data has been transferred, and where individual vehicles are in the download process. Network instability is logged in real time, so if a fleet is in a low-coverage area, that context is visible rather than hidden.
For major updates, RadioMobile stages rollouts through a test group first. A small cohort of vehicles receives the update, operators confirm everything works as expected, and then the job extends to the full fleet.
Automating Fleet Distribution: REST API, Scheduled Jobs, and Pipeline Integration
Resilio exposes every distribution function through a REST API, so update workflows can run entirely programmatically, triggered automatically by a pipeline, scheduled in advance, or both. An operator can launch a job, target a group of nodes, stage a rollout, and check fleet-wide progress through API calls alone, or skip the manual trigger and let scheduled jobs run on their own.
For a DevOps or platform team, that means edge distribution lives in the same place as every other deployment. The native Linux agent, full CLI, and REST API let Resilio drop into existing CI/CD pipelines, infrastructure-as-code, and orchestration workflows with no GUI dependency and no human in the critical path. A new build, model, or config version can kick off a distribution job automatically, the same way it would trigger any other stage in the pipeline.
In the RadioMobile deployment, this is how major updates move at scale: jobs stage to a test cohort first, get validated, then extend to the full fleet, and the whole sequence can be scheduled and automated rather than run by hand. The console stays available for visibility and exceptions, but the day-to-day distribution path doesn’t depend on anyone sitting in front of it.
What Happens When a Vehicle Goes Offline Mid-Transfer?
When a vehicle loses connectivity, Resilio pauses the transfer job for that agent and holds the partial download on the device exactly as it was. When the vehicle reconnects, whether that is two minutes or two days later, the transfer resumes from where it stopped. No manual restart, no data loss, no IT involvement required.
The same behavior applies to vehicles that power down entirely. If a unit is out of service for a week, the job is put on hold. When the vehicle comes back online, it resumes the download, completes it, and notifies the operator that the update is ready to install at a convenient time.
Why Fleet Data Sync is Vital for Public Safety
Resilio’s first paying customer was a fire and rescue department in Australia. The need to move large, mission-critical data to mobile units over unreliable connections wasn’t an afterthought. It was the founding use case.
“Public safety is among the most difficult environments on the planet. Because of that, you want a solution that is undaunted by difficulties. That is the Resilio protocol. It’s what we were designed to do from the very foundations of the technology.”
— Eric Klinker, CEO, Resilio
That design intent shows up in how the platform handles the edge cases that break simpler tools: unexpected disconnections, bandwidth that swings from 5G to near-zero mid-transfer, and vehicles that go dark for extended periods and then need to catch up without human intervention.
For IT leaders supporting fire, EMS, or any fleet-based operation, the key question is whether your current distribution tool was built with this kind of environment in mind or designed for the stable, wired, always-on conditions of a corporate office.
Key Takeaways
The RadioMobile deployment illustrates what purpose-built fleet data distribution looks like when the underlying platform was designed for the environment from the start, not adapted for it after the fact.
Resilio Active Everywhere handles unreliable networks at the protocol level. Chunk-based, resumable transfer means a dropped connection pauses a job rather than resetting it. When a vehicle comes back online, the transfer picks up exactly where it left off, with no manual restart and no data loss.
Peer-to-peer architecture makes fleet-scale distribution economically and operationally viable. Rather than serving every firmware update, map file, and pre-plan from a central origin, Resilio allows vehicles that have already received a file to serve it to nearby agents directly. For departments with hundreds or thousands of vehicles spread across large coverage areas, that difference in architecture directly affects how quickly the entire fleet gets current.
Two-way data flow extends the platform’s value beyond delivery. The ability to pull metrics, telemetry, and log files back from vehicles gives IT and fleet operators the visibility needed to diagnose issues remotely, track performance over time, and act on data that would otherwise remain inaccessible on the vehicle itself.
Automation keeps the update process running without placing IT in the critical path. Through Resilio’s REST API and scheduled job functionality, distribution workflows run independently, with end-to-end visibility into fleet-wide progress available through the management console at any point.
For fleet operators and IT leaders managing mobile endpoints in demanding environments, the underlying question is always whether the platform can keep up with the operational reality in the field. The Resilio protocol was built with that reality as the starting point.
Watch the Full Webinar
The clips above cover the highlights, but the full session goes deeper, including a live product demo, a real-time look at a running distribution job, and a Q&A with Petr, Eric, and John. Watch the full webinar here.
Ready to See It in Your Environment?
If you’re managing data distribution for a fleet, an edge deployment, or a distributed set of sites, schedule a demo with the Resilio team to see how Active Everywhere handles your specific use case.
Frequently Asked Questions
When a vehicle loses connectivity, Resilio pauses the transfer job for that agent and holds the partial download on the device. As soon as the vehicle reconnects, the transfer resumes from where it stopped. No manual restart is needed, and no data that has already been transferred is lost.
Yes. Resilio’s peer-to-peer architecture is specifically designed for large-scale distribution. Rather than routing all transfers through a central server, vehicles that have already received a file can serve it to nearby agents directly. This reduces origin server load and significantly speeds up fleet-wide delivery.
Resilio Active Everywhere supports any file type. In the RadioMobile deployment, this includes software executables, GIS map layers, pre-plans, configuration files, and log files pulled back from vehicles for diagnostics.
Yes. Resilio is designed to perform over high-latency, low-bandwidth, and intermittent connections, including LTE, 4G, 5G, and satellite. The chunked transfer protocol means the platform adapts to available bandwidth rather than requiring a stable connection throughout a transfer.
Yes. Resilio supports both distribution jobs (pushing files out to agents) and consolidation jobs (pulling data back from agents). RadioMobile uses this to retrieve log files and vehicle telemetry for diagnostics and performance analysis.
Yes. Resilio delivers artifacts, models, and config files to edge nodes over intermittent, low-bandwidth, and high-latency links, and resumes automatically from the exact point of interruption when a node reconnects. Because files are broken into independently verified chunks, a dropped connection pauses the transfer rather than restarting it, so a node on a degraded link still converges to the correct state with no manual intervention and no central server in the path.
Peer-to-peer distribution removes the central server as a bottleneck. Once one edge node receives a file, it can serve that file to nearby nodes directly over the local network, so delivery time stops scaling with the number of targets. A central server or CDN model sends every copy from the origin, which raises egress costs and slows rollouts as node count grows; Resilio’s mesh keeps a thousand-node update much closer to the speed of a ten-node one.
