RemoAsset vs Fleet reads like a shortlist and is really a category question. One service moves hardware between your company and people’s homes. The other tells you what is happening on machines that are switched on.
TL;DR
- Fleet is device management. RemoAsset is logistics. Different failures.
- Management software cannot see a laptop that never powers on again.
- A logistics record is not a full IT asset management tool.
- Open source suits teams with capacity to run it.
- Buy against your actual failure, not the louder category.
- Two numbers decide it: day one readiness and recovered devices.
When you need neither yet
Four stages, and the first genuinely needs nothing.
Under about fifteen people in one place. You hand machines over in person and you can see every one of them. Buying either tool solves a problem you do not have.
Remote but low churn. A few joiners a year. Handle each individually and spend the budget elsewhere; the overhead of a platform is not yet earned.
Growing, machines unaccounted for. You can no longer say who holds what. This is the point where one of the two categories starts paying, and which one depends on the question you cannot answer.
Audited, regulated or distributed widely. You need both configuration evidence and recovery evidence, which is when teams stop treating this as an either or.
Why RemoAsset vs Fleet is a category confusion
Both appear in searches for managing laptops across a distributed team, so they end up on the same shortlist. The shortlist is where the trouble starts, because they answer different questions and a direct comparison flatters whichever one matches the evaluator’s current pain.
Fleet sits in device management. It is open source, built around visibility into what machines are running, and it suits teams who want to query their fleet and enforce configuration. Its pricing page returned no readable figure to a server-side fetch on 3 November 2026, so treat any number you see quoted elsewhere as unverified until you confirm it directly.
Disclosure: RemoAsset is owned by the same people who publish this site. It sits in logistics. Procurement, delivery to people’s homes, retrieval from leavers, storage, and certified wiping across 80 or more countries. It is an operation rather than software, and it is deliberately not an MDM.
Put plainly: one of them knows whether a laptop is encrypted, and the other knows how to get it back from a flat in Lisbon. A team that buys the first and assumes it covers the second ends up with excellent reporting on the devices it still has.
It is worth naming what the two layers are each being measured against, because the standards do not split the way the vendor categories do. Asset handling expectations in ISO/IEC 27001 cover both knowing the state of equipment and being able to return or dispose of it, and media sanitisation guidance in NIST SP 800-88 assumes the device is physically in hand before anything can be verified. An assessor asking you to evidence either will not care which of your two suppliers owns the answer.
What each actually does
- Fleet, best for: visibility and configuration across running machines, with an open source model that suits engineering-led teams who want to self host and extend it.
- Fleet, where it struggles: anything physical. It cannot ship a laptop, collect one, or report on a device that has stopped checking in, and self hosting is real operational work.
- RemoAsset, best for: getting equipment to people and back across many countries, with storage and per-device wipe records attached to the movement.
- RemoAsset, where it struggles: it is not device management. It will not enforce a setting, report patch status, or replace a full asset management tool with deep software inventory.
- The overlap: both touch the asset record, and that is the only place a genuine comparison exists.
So the comparison is narrow and the complement is wide, which is the opposite of how shortlists usually treat them.
Five questions that decide it
Did last quarter’s new starters have working kit on day one? If not, your gap is movement.
Can you tell which machines are encrypted right now? If not, your gap is visibility.
How many devices from last year’s leavers came back? This is the number management software cannot improve.
Do you have engineering capacity to self host? It changes the cost of an open source option substantially.
In how many countries do you employ people? Past three or four, logistics stops being something you arrange case by case.
The wider set, and the trade-offs
Open source device management. Best for control, extensibility and cost at scale when you have the people to run it. It struggles on the physical layer entirely and on teams with no platform engineering.
Commercial MDM. Best for enforcement and support, and the fastest route to configuration evidence. It struggles on anything offline and on devices nobody can physically reach.
IT asset management software. Best for records, reporting and audit trails across hardware and software. It struggles on input, because a tool only knows what something told it, and the movements are what nobody reports.
Regional logistics partners. Best where you have real density in a few markets. It struggles on the long tail of single-employee countries and on consistent records across providers.
A single lifecycle service. RemoAsset, with the ownership disclosure above, covers procurement through retrieval and wiping in one record. It struggles as a replacement for management software, and consolidation raises concentration risk, so the exit terms deserve the same scrutiny as the service.
The decision table
| Situation | Scale | Setup | Primary pain | Recommended starting point |
|---|---|---|---|---|
| One office, low churn | Under 15 | No IT owner | Nothing broken | Neither, revisit later |
| Cannot see device state | 50 plus | IT owner | No configuration evidence | Device management first |
| Engineering-led team | Any | Platform capacity | Wants to self host | Open source management |
| Kit late or missing | Any | Any | Day one failures | Logistics first |
| Leavers keep devices | Any | Any | No recovery route | Retrieval, then records |
| Audited and distributed | 100 plus | Security owner | Both kinds of evidence | Both layers, deliberately |
What buying the wrong half costs
The first cost is a dashboard that looks complete. Device management reports on machines that check in, so a fleet with twelve unrecovered laptops shows a clean screen and twelve devices simply are not on it. The absence is not flagged, because nothing is there to flag.
The second is the opposite error. A logistics arrangement with no management layer gets equipment to people reliably and tells you nothing about whether those machines are patched, encrypted or still in use. You know where everything is and not what state it is in.
The third is the budget conversation that follows. Having bought one, teams find it hard to ask for the other, because on paper the device problem was already solved last year. The second request looks like the first one failed.
The fourth is time lost in evaluation. Running a trial of a management tool against a logistics service produces a comparison nobody can act on, because the strongest features of each are invisible to the other’s use case.
So the question is not which of the two is better. It is which of your two numbers is worse: day one readiness, or devices recovered.
The blind spot both have to cover
There is one population neither layer handles well on its own, and it is the one that causes incidents: devices that have stopped reporting and have not been returned.
Management software cannot see them, because they are not checking in. A logistics service cannot move them until somebody initiates a collection. They exist only as a difference between two lists, and most organisations never compare those lists.
Three signals say you have a population like this. Your leaver count last year exceeds your recovered device count. Some machines have not checked in for months and nobody has asked why. And you cannot produce a wipe record for a meaningful share of departures.
It is worth measuring before you buy anything, since the answer tells you which half to fix first. Looking at how recovery closes out the devices that stop reporting shows what the logistics half of that gap involves.
Related reading
- Asset tracking against MDM
- RemoAsset against Workwize
- Endpoint lifecycle management
- MDM for remote teams
- Device lifecycle management, remotely
Frequently Asked Questions
Are RemoAsset and Fleet actually competitors?
Not really, and treating them as alternatives is the common mistake. Fleet is device management software that reports on and configures machines that are running. RemoAsset is a logistics service that moves hardware to people and recovers it. Most teams eventually need something from each category.
Which one should we buy first?
Whichever addresses your current failure. If devices arrive late or never come back, that is a logistics problem and software will not fix it. If you cannot tell which machines are patched or encrypted, that is a management problem and a courier will not fix it either.
Does device management tell you where a laptop is?
It tells you about machines that check in. A laptop sitting powered off in a former employee’s flat reports nothing, which is exactly the population you most want to account for. That blind spot is structural rather than a shortcoming of any particular product.
Does a logistics service replace an asset register?
It gives you an accurate record of the devices it has moved, which is usually better than a spreadsheet nobody updates. It does not replace a full IT asset management tool if you need deep reporting, software inventory and integrations across every system you run.
What does open source change here?
Fleet’s open source model suits teams with engineering capacity who want to self host and extend. That is a real advantage and a real cost: somebody has to own the deployment. Neither consideration applies to a logistics service, where you are buying an operation rather than software.
Can one vendor cover both?
Some platforms claim both, and the honest assessment is that most are stronger on one side. Combining them reduces the number of relationships to manage and raises concentration risk, so the exit terms matter more. Judge the claim on the weaker half rather than the marketing.
How do we decide without a trial of both?
Count two numbers from last year. How many new starters had working equipment on day one, and how many departures ended with a recovered and wiped device. If both numbers are good, your gap is visibility. If either is poor, your gap is movement.
