---
title: Selecting a deployment pattern for mobile operations and offline data management systems
source_url: "https://architecture.arcgis.com/en/framework/system-patterns/mobile-operations-and-offline-data-management/selecting-a-deployment-pattern.html"
md_url: "https://architecture.arcgis.com/en/framework/system-patterns/mobile-operations-and-offline-data-management/selecting-a-deployment-pattern.md"
---
# Selecting a deployment pattern for mobile operations and offline data management systems

Mobile operations and offline data management systems are typically deployed using one of three deployment patterns:

- [SaaS](/en/framework/system-patterns/mobile-operations-and-offline-data-management/deployment-patterns/as-saas.md)
- [Windows/Linux](/en/framework/system-patterns/mobile-operations-and-offline-data-management/deployment-patterns/as-server-software.md)
- [Kubernetes](/en/framework/system-patterns/mobile-operations-and-offline-data-management/deployment-patterns/as-kubernetes.md)

Selecting a [deployment pattern](/en/framework/system-patterns/anatomy-of-a-system-pattern.md) is one of the most important decisions to make in designing a GIS system for your organization.

Perhaps the most critical factor in this decision will be aligning with your organization's IT principles, guidelines, and comfort-level in supporting different deployment approaches. For example, some organizations may prefer to standardize on SaaS-based systems and solutions. Other organizations that are investing heavily into Kubernetes-based deployments, including hiring and training staff with operational Kubernetes experience and skills, may prefer Kubernetes-based deployment patterns. 

> [!NOTE]
> **Note**
> The capabilities as well as the considerations differ between deployment patterns. Review the comparisons below, along with the deployment pattern pages for additional information.
For general information and considerations around these deployment approaches see the [ArcGIS products and deployment options](/en/overview/introduction-to-arcgis/arcgis-capabilities.md) page of the ArcGIS overview.


# Capability comparison

In addition to aligning with your IT principles, guidelines, and comfort-level, it's also important to consider the capabilities of each deployment pattern in your decision-making process. The capabilities of a mobile operations and offline data management system differ between deployment patterns. The following matrix compares the specific capabilities supported by each of the deployment pattern. 

Capabilities used in a mobile operations and offline data management system, but typically provided by other systems, such as basemaps, geocoding, and other location services provided by a [location services system](/en/framework/system-patterns/location-services/overview.md) are not listed below. Learn more about [related system patterns](#related-system-patterns).

| **Capability** | **SaaS** | **Windows/Linux** | **Kubernetes**
| :------------------------------------- | :------: | :---------------: | :------------: |
| [Mapping and visualization](overview.md#mapping-visualization "Create as well as interact with 2D maps and 3D scenes on mobile devices") | ✓ | ✓ | ✓ |
| [Offline data and maps](overview.md#offline-data-maps "Take data and maps offline for use without a network connection") | ✓ | ✓ | ✓ |
| [Basemaps](overview.md#basemaps "Offline support for web-based layers that provide overall visual context for 2D maps and 3D scenes") | ✓ | ✓ | ✓ |
| [Geocoding](overview.md#geocoding "Offline support for converting text to an address and a location") | ✓ | ✓ | ✓ |
| [Route and directions](overview.md#route-directions "Offline support for finding the best path from an origin to a destination for an individual or single vehicle") | ✓ | ✓ | ✓ |
| [Work assignment and dispatching](overview.md#work-assignment "Ensure the right worker goes to the right place with the right tools") | ✓ | ✓ | ✓ |
| [Location sharing](overview.md#location-sharing "Record where mobile workers are and where they have been") | ✓ | ✓ | ✓ |
| [Data editing](overview.md#data-editing "Online and offline editing of spatial and attribute data on mobile devices") | ✓ | ✓ | ✓ |
| [Data import and export](overview.md#data-import-export "Import and export your data in bulk") | ✓ | ✓ | ✓ |
| [Data interoperability and transformation](overview.md#data-interop "Move data between hundreds of supported systems and apps")[^1] | ◐ | ✓ | |
| [Edit tracking and auditing](overview.md#tracking-auditing "Record and audit information about any data inserts or updates") | ✓ | ✓ | ✓ |
| [Short transaction management](overview.md#short-transactions "Support ACID transactions without managing multiple versions of your data") | ✓ | ✓ | ✓ |
| [Long transaction management](overview.md#long-transactions "Supports multiple concurrent states of the data along with conflict management") | | ✓[^2] | ✓[^2] |
| [Spatial and attribute rules](overview.md#spatial-attr-rules "Enhances the editing experience and improves geospatial data integrity") | | ✓[^3] | ✓[^3] |
| [Data distribution and replication](overview.md#data-distribution "Distribute data using replication and other mechanisms") | ◐ | ✓ | ✓ |
| [Data archiving and history](overview.md#data-archiving "Capture, manage, and analyze data changes over time") | | ✓ | ✓ |
| [Advanced data validation](overview.md#advanced-validation "Simplify, improve, and automate data quality control workflows") | | ✓ | |
| [Workflow management and automation](overview.md#workflow-management "Orchestrate and automate work across teams") | ◐ | ✓[^4] | ✓[^4]<sup> |
| [Hosted Python notebooks](overview.md#hosted-notebooks "Incorporate Python-based analysis, administration, and automation") | ✓ | ✓[^5] | ✓ |
| [Parcel management](overview.md#parcel-management "Manage 3D and 4D parcel data") | | ✓ | ✓[^6] |
| [Roads and highways](overview.md#roads-highways "Enable measure-based event data collection online and offline with mobile devices for the transportation industry") | | ✓ | ✓[^6] |
| [Pipeline referencing](overview.md#pipeline-referencing "Enable measure-based event data collection online and offline with mobile devices for the pipeline industry") | | ✓ | ✓[^6] |
| [Indoor GIS](overview.md#indoor-gis "Explore indoor spaces on mobile devices while viewing your real-time location inside buildings")[^7] | ✓ | ✓ | ✓ |
| [Indoor positioning](overview.md#indoor-positioning "Locate yourself and others inside a building in real time") | ✓ | ✓ | ✓ |
| [Other industry solutions](overview.md#industry-solutions "Rapidly deploy industry-specific apps and solutions")[^8] | ✓ | ◐ | ◐ |

✓_Full support_
◐_Partial support_

* This line is required for footnotes in order for them to appear in the page as opposed to the bottom of the page. 


[^1]: [ArcGIS Data Interoperability](https://www.esri.com/en-us/arcgis/products/arcgis-data-interoperability/overview) for ArcGIS Pro supported in all deployment patterns
[^2]: Supported in back office system, not on mobile devices
[^3]: Rules applied when data is synchronized with the back office system
[^4]: Requires [ArcGIS Workflow Manager](https://doc.esri.com/en/arcgis-workflow-manager/latest/)
[^5]: Requires [ArcGIS Notebook Server](https://enterprise.arcgis.com/en/notebook/)
[^6]: Requires some Windows/Linux infrastructure
[^7]: Full capability spans multiple system patterns 
[^8]: Some industry solutions only available on SaaS


See the mobile operations and offline data management [system capabilities](overview.md#capabilities) for more information on each row listed above. Additionally, each of the cells above is described in more detail in the mobile operations and offline data management system deployment pattern pages.

_The capabilities represented above reflect those available as of July, 2026._

# General considerations

The considerations below aim to help align your organization's business and IT needs with the appropriate mobile operations and offline data management system deployment pattern. The information presented here is not meant to be exhaustive, but rather highlights key considerations for mobile operations and offline data management systems.

- Scalability, reliability, service level agreements (SLA), security, and the balance of responsibility between your organization and Esri tend to be major factors in selecting a deployment pattern. Please see the [reliability](/en/framework/architecture-pillars/reliability/overview.md), [performance and scalability](/en/framework/architecture-pillars/performance-and-scalability/overview.md), and [security](/en/framework/architecture-pillars/security/overview.md) pillars for more information.
- Organizations with a moderate-to-large editor workforce or who have needs for long transactions, conflict detection and reconciliation, spatial and attribute rules, as well as archiving and advanced auditing or edit lineage tend to favor an [ArcGIS Enterprise](https://www.esri.com/en-us/arcgis/products/arcgis-enterprise/overview)-based deployment on [Windows, Linux](/en/framework/system-patterns/mobile-operations-and-offline-data-management/deployment-patterns/as-server-software.md), or [Kubernetes](/en/framework/system-patterns/mobile-operations-and-offline-data-management/deployment-patterns/as-kubernetes.md). These two deployment patterns offer the most robust data editing and management capabilities and allow for flexible alignment with workflows and governance needs.
- The [SaaS](/en/framework/system-patterns/mobile-operations-and-offline-data-management/deployment-patterns/as-saas.md) deployment pattern using [ArcGIS Online](https://www.esri.com/en-us/arcgis/products/arcgis-online/overview) features the quickest time to market. 
- Some of the more advanced, specialized, and/or industry-specific capabilities of mobile operations and offline data management systems only exist for a subset of deployment patterns. Please review and consider the [capability comparison](#capability-comparison) and deployment pattern pages thoroughly in your design and decision-making process.
- PaaS deployments of mobile operations and offline data management systems are not supported at this time, as PaaS and [ArcGIS Location Platform](https://www.esri.com/en-us/arcgis/products/arcgis-location-platform/overview) does not currently support taking data and maps offline. For mobile workflows that don't require offline support, and that can rely on a consistent network connection, explore other [ArcGIS system patterns](/en/framework/system-patterns/introduction.md). 
- Mobile operations and offline data management systems rely heavily on location services provided by a [location services systems](/en/framework/system-patterns/location-services/overview.md). The deployment of your location services system(s) should be taken into consideration when designing a mobile operations and offline data management system. Additionally, special consideration may be required for location services intended for use offline, such as basemaps, geocoding, and routing. Learn more about [offline maps](https://developers.arcgis.com/documentation/mapping-apis-and-services/offline/offline-maps/), [offline data](https://developers.arcgis.com/documentation/mapping-apis-and-services/offline/offline-data/), and [offline applications](https://developers.arcgis.com/documentation/mapping-apis-and-services/offline/) in general.

Selecting a deployment pattern is one of the most important decisions to make in designing a GIS system for your organization. However, it is not the only one. There are many additional factors to take into consideration when designing your system, including areas like security, reliability, and integration. As such, please don't consider the information provided here to be exhaustive. Please review the architecture [practices](/en/framework/architecture-practices/introduction.md) and [pillars](/en/framework/architecture-practices/introduction.md#architecture-pillars) of the ArcGIS Well-Architected Framework, as well as [product documentation](https://doc.arcgis.com/en/), in detail as part of your design process.