Maps · head to head
ArcGIS Field Maps vs Ridecell

ArcGIS Field Maps
Maps
Esri field data collection that cannot be bought on its own, only with an ArcGIS user type
- From
- On request
- Free plan
- No

Ridecell
Fleet Management
Fleet automation that sits on top of the telematics you already run
- From
- On request
- Free plan
- No
The short version
- Each has a real cost: ArcGIS Field Maps field Maps has no price of its own, so a project budget built from the product page misses the Creator seats, the Mobile Worker seats and the ArcGIS Online credits or Enterprise infrastructure that actually cost money; Ridecell it requires an existing telematics or connected-vehicle data source, so it is always an additional line of spend rather than a consolidation, and its output is only as good as that underlying feed.
- They diverge on capability: ArcGIS Field Maps covers Offline map areas, Ridecell covers Telematics-agnostic ingestion.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which ArcGIS Field Maps and Ridecell actually diverge.
| Attribute | ArcGIS Field Maps | Ridecell |
|---|---|---|
| Pricing model | Included with an ArcGIS user type licence | quote |
| Platforms | iOS, Android, Web | Web, iOS, Android |
| Category | Maps | Fleet Management |
Identical on both: starting price (On request), free tier (No), user rating (Not yet rated).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in ArcGIS Field Maps
- Offline map areas
- Smart forms
- High-accuracy GNSS
- Location sharing
- Assignment dispatch
- Indoor positioning
- Direct editing of authoritative data
Only in Ridecell
- Telematics-agnostic ingestion
- Workflow automation
- Digital keys and access
- Damage and readiness detection
- Fleet recovery
- Mobility platform
What people use each for
The jobs each tool is most often brought in to do.
ArcGIS Field Maps
- A water utility whose inspectors update the same asset feature service the office GIS runs on, rather than filling in forms that someone re-keysnot Ridecell
- A county carrying out a sign inventory where crews work in areas without mobile coverage and need offline maps that sync laternot Ridecell
- An environmental team needing sub-metre positions from an external GNSS receiver recorded directly against the authoritative datasetnot Ridecell
- An organisation consolidating from Collector, Explorer, Tracker and Workforce onto a single app after Esri retired themnot Ridecell
Ridecell
- A rental or carsharing operator that needs keyless handover, damage detection and automated recovery across thousands of vehiclesnot ArcGIS Field Maps
- A large corporate fleet with several telematics vendors from past acquisitions that wants one automation layer rather than a device replacement programmenot ArcGIS Field Maps
- An OEM or dealer group launching a subscription or shared vehicle service without building the booking and access stack itselfnot ArcGIS Field Maps
- A fleet operations team spending significant staff time manually triaging telematics alerts into work ordersnot ArcGIS Field Maps
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
ArcGIS Field Maps
- Field Maps has no price of its own, so a project budget built from the product page misses the Creator seats, the Mobile Worker seats and the ArcGIS Online credits or Enterprise infrastructure that actually cost money
- It only works against Esri feature services, so an organisation whose data is in PostGIS or a database without an ArcGIS layer must publish through Esri first, which is a platform decision rather than an app choice
- Named user licensing means occasional or seasonal field staff still consume a full annual seat, and organisations with a large pool of infrequent collectors pay for capacity they use a few weeks a year
- As a forms tool alone it is more rigid and more expensive than dedicated mobile forms products, so its value collapses if you are not already committed to ArcGIS
- The consolidation of four apps into one changed established workflows, and organisations that had built processes around Collector or Workforce have had to rework them on Esri's timetable rather than their own
Ridecell
- It requires an existing telematics or connected-vehicle data source, so it is always an additional line of spend rather than a consolidation, and its output is only as good as that underlying feed.
- Pricing is enterprise and quoted, with implementation services attached, so the first-year cost is dominated by a project rather than a subscription and small fleets are effectively excluded.
- Much of the automation overlaps with rules and workflow features that Geotab and Samsara now include, so the business case depends on needing more than those platforms do natively.
- The company has repositioned from consumer mobility software to fleet automation, so reference customers from the carsharing era do not tell you much about how it performs for a utility or leasing fleet.
- It is a small vendor next to the telematics platforms it sits on, which means a thinner partner network for implementation and a real concentration risk if it is embedded in daily fleet operations.
Pricing, plan by plan
ArcGIS Field Maps
On request- Mobile Worker user type$undefined/year
- Field editing in Field Maps included with no additional purchase
- Cannot author maps; requires a Creator seat elsewhere in the organisation
- Priced per named user per year
- Creator user type$undefined/year
- Required to author and publish the maps that field workers use
- At least one Creator needed before Field Maps can be deployed
- Includes Field Maps editing as well as authoring
- ArcGIS Enterprise deployment$undefined/year
- Field Maps against self-hosted ArcGIS Enterprise instead of ArcGIS Online
- Server licensing and infrastructure priced separately
- Quoted through Esri or a distributor
Ridecell
On request- Ridecell$undefined/year
- Enterprise agreement priced by fleet size and modules
- Implementation and integration services quoted separately
- No hardware sold; existing telematics or OEM data feeds required
Which should you pick?
Choose ArcGIS Field Maps if
- You need offline map areas.
- You work on iOS, Android, Web.
- You also want smart forms.
Choose Ridecell if
- You need telematics-agnostic ingestion.
- You work on Web, iOS, Android.
- You also want workflow automation.
Questions people ask
- Is ArcGIS Field Maps or Ridecell better?
- Neither clearly leads. ArcGIS Field Maps starts at On request and Ridecell at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, ArcGIS Field Maps or Ridecell?
- ArcGIS Field Maps starts at On request and Ridecell at On request.
- Does ArcGIS Field Maps or Ridecell run on more platforms?
- ArcGIS Field Maps runs on iOS, Android, Web. Ridecell runs on Web, iOS, Android.
- What is ArcGIS Field Maps best used for?
- ArcGIS Field Maps is most often used for a water utility whose inspectors update the same asset feature service the office gis runs on, rather than filling in forms that someone re-keys, a county carrying out a sign inventory where crews work in areas without mobile coverage and need offline maps that sync later, an environmental team needing sub-metre positions from an external gnss receiver recorded directly against the authoritative dataset, an organisation consolidating from collector, explorer, tracker and workforce onto a single app after esri retired them. Of those, a water utility whose inspectors update the same asset feature service the office gis runs on, rather than filling in forms that someone re-keys and a county carrying out a sign inventory where crews work in areas without mobile coverage and need offline maps that sync later are not what Ridecell is typically brought in for.
- What can ArcGIS Field Maps do that Ridecell cannot?
- ArcGIS Field Maps covers Offline map areas, Smart forms, High-accuracy GNSS, Location sharing. Ridecell covers Telematics-agnostic ingestion, Workflow automation, Digital keys and access, Damage and readiness detection.
Answered from the vendors’ own pages
ArcGIS Field Maps: Can I buy Field Maps on its own?
No. It is included with the Mobile Worker, Creator and GIS Professional user types, and you need at least one Creator in the organisation to author maps.
Ridecell: Does Ridecell replace my telematics provider?
No. It sits above your existing devices or OEM data feed. Budget for both, and confirm your current provider exposes the data Ridecell needs before signing.
ArcGIS Field Maps: What replaced Collector and Workforce?
Field Maps. Esri merged Collector, Explorer, Tracker and Workforce into it and retired the separate apps.
Ridecell: Is this useful for a fleet of fifty vehicles?
Rarely. The value comes from automating high-volume repetitive coordination, and the pricing and implementation model assume a much larger operation.
ArcGIS Field Maps: Does it work offline?
Yes. Map areas are downloaded in advance and edits synchronise when connectivity returns.
Ridecell: Can it work with OEM data instead of aftermarket devices?
Yes, that is one of the reasons to consider it, though coverage depends on which manufacturers and model years are in your fleet and what their APIs expose.
ArcGIS Field Maps: Can it write to a non-Esri database?
Not directly. The data must be published as an ArcGIS feature service, which may sit over an enterprise geodatabase you already run.
Related pages
More on ArcGIS Field Maps
Other head to heads
- ArcGIS Field Maps vs QGIS
- ArcGIS Field Maps vs SW Maps
- ArcGIS Field Maps vs Felt
- ArcGIS Field Maps vs CARTO
- ArcGIS Field Maps vs Global Mapper
- ArcGIS Field Maps vs GRASS GIS
- ArcGIS Field Maps vs Foursquare Spatial Studio
- ArcGIS Field Maps vs Trailforks
- ArcGIS Field Maps vs onX Maps
- ArcGIS Field Maps vs Mapbox
- ArcGIS Field Maps vs Google Maps Platform
- ArcGIS Field Maps vs Leaflet
- ArcGIS Field Maps vs Bing Maps
- ArcGIS Field Maps vs Cesium ion
- ArcGIS Field Maps vs Citymapper
- ArcGIS Field Maps vs Gaia GPS
- ArcGIS Field Maps vs GraphHopper
- ArcGIS Field Maps vs Samsara
- ArcGIS Field Maps vs Geotab
- ArcGIS Field Maps vs Verizon Connect
- ArcGIS Field Maps vs Motive
- ArcGIS Field Maps vs AssetWorks
- ArcGIS Field Maps vs CalAmp
- ArcGIS Field Maps vs NexTraq
- ArcGIS Field Maps vs Whip Around
- ArcGIS Field Maps vs Azuga
- ArcGIS Field Maps vs Omnitracs
- ArcGIS Field Maps vs Teletrac Navman
- ArcGIS Field Maps vs Chevin FleetWave
- ArcGIS Field Maps vs GPS Trackit
- ArcGIS Field Maps vs Lytx
- ArcGIS Field Maps vs Quartix
- ArcGIS Field Maps vs Uptake
- ArcGIS Field Maps vs Webfleet
- Ridecell vs QGIS
- Ridecell vs SW Maps
- Ridecell vs Felt
- Ridecell vs CARTO
- Ridecell vs Global Mapper
- Ridecell vs GRASS GIS
- Ridecell vs Foursquare Spatial Studio
- Ridecell vs Trailforks
- Ridecell vs onX Maps
- Ridecell vs Mapbox
- Ridecell vs Google Maps Platform
- Ridecell vs Leaflet
- Ridecell vs Bing Maps
- Ridecell vs Cesium ion
- Ridecell vs Citymapper
- Ridecell vs Gaia GPS
- Ridecell vs GraphHopper
- Ridecell vs Samsara
- Ridecell vs Geotab
- Ridecell vs Verizon Connect
- Ridecell vs Motive
- Ridecell vs AssetWorks
- Ridecell vs CalAmp
- Ridecell vs NexTraq
- Ridecell vs Whip Around
- Ridecell vs Azuga
- Ridecell vs Omnitracs
- Ridecell vs Teletrac Navman
- Ridecell vs Chevin FleetWave
- Ridecell vs GPS Trackit
- Ridecell vs Lytx
- Ridecell vs Quartix
- Ridecell vs Uptake
- Ridecell vs Webfleet
