---
title: Selecting a deployment pattern for self-service mapping and sharing systems
source_url: "https://architecture.arcgis.com/en/framework/system-patterns/self-service-mapping-and-sharing/selecting-a-deployment-pattern.html"
md_url: "https://architecture.arcgis.com/en/framework/system-patterns/self-service-mapping-and-sharing/selecting-a-deployment-pattern.md"
---
# Selecting a deployment pattern for self-service mapping, analysis, and sharing systems

Self-service mapping, analysis, and sharing systems are typically deployed using one of three deployment patterns:

- [SaaS](/en/framework/system-patterns/self-service-mapping-and-sharing/deployment-patterns/as-saas.md)
- [Windows/Linux](/en/framework/system-patterns/self-service-mapping-and-sharing/deployment-patterns/as-server-software.md)
- [Kubernetes](/en/framework/system-patterns/self-service-mapping-and-sharing/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. Please 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 data editing and management system differ between deployment patterns. The following matrix compares the specific capabilities supported by each of the deployment pattern. 

Capabilities used in a self-service mapping, analysis, and sharing 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") | ✓ | ✓ | ✓ |
| [App building](overview.md#app-building "Empower content creators to create web applications") | ✓ | ✓ | ✓ |
| [Site building](overview.md#site-building "Enable content creators to create hosted websites") | ✓ | ✓ | ✓|
| [Sharing and collaboration](overview.md#sharing-collaboration "Enable users within an organization to share data, maps, and other content") | ✓ | ✓ | ✓ |
| [Data publishing and hosting](overview.md#data-publishing-hosting "Securely publish, store, manage, and access of data as a service") | ✓ | ✓ | ✓ |
| [Data editing](overview.md#data-editing "Services-based editing of spatial and attribute data") | ✓ | ✓ | ✓ |
| [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] | ◐ | ✓ | |
| [Data distribution and replication](overview.md#data-distribution "Distribute data using replication and other mechanisms") | ◐ | ✓ | ✓ |
| [Workflow management and automation](overview.md#workflow-management "Orchestrate and automate work across teams") | ◐ | ✓[^2] | ✓[^2]<sup> |
| [Spatial joins and relationships](overview.md#spatial-joins-relationships "Combine rows from two datasets based on a spatial relationship") | ✓ | ✓ | ✓ |
| [Network analysis](overview.md#network-analysis "Solve complex network problems (typically on street networks) like finding the closest facility") | ✓ | ✓[^3] | ✓[^3] |
| [Pattern analysis](overview.md#pattern-analysis "Identify spatial and temporal patterns in data") | ✓ | ✓ | ✓ |
| [Proximity analysis](overview.md#proximity-analysis "Look at the proximity of spatial data to other spatial data") | ✓ | ✓ | ✓ |
| [Summarization analysis](overview.md#summarization-analysis "Aggregate or summarize data into higher order data structures") | ✓ | ✓ | ✓ |
| [Geometry analysis](overview.md#geometry-analysis "Use client-side API to solve geometry problems") | ✓ | ✓ | ✓ |
| [3D visual analysis](overview.md#3d-visual-analysis "Calculate and display spatial information derived from the terrain, buildings, and other 3D objects") | ✓ | ✓ | ✓ |
| [Graph and link analysis](overview.md#graph-link-analysis "Model entities and relationships to find hidden patterns") | | ✓[^5] | |
| [Hosted Python notebooks](overview.md#hosted-notebooks "Incorporate Python-based analysis, administration, and automation") | ✓ | ✓[^6] |✓ |
| [Advanced exploratory analytics](overview.md#exploratory-analytics "Empower analysts of all skill levels to directly connect data, perform advanced analytics, and take results into third-party systems") | ✓ | ✓ | |
| [Community engagement](overview.md#community-engagement "Organize people, data, and tools through information-driven initiatives") | ✓ | | |
| [Indoor GIS](overview.md#indoor-gis "Combine source CAD, BIM, and reality capture data into a single geospatial system of record")[^7] | ✓ | ✓ | ✓ |
| [Topographic mapping](overview.md#topographic-mapping "Optimizes specification-driven topographic data and map production")[^7] | | ✓ | |
| [Market intelligence](overview.md#market-intelligence "Enable smarter decision-making for market planning, site selection, and customer segmentation") | ✓ | ✓[^8] | |
| [Urban planning and design](overview.md#urban-planning "Enable the digital transformation of city and regional planning") | ✓ | ✓ | |
| [Project delivery and coordination](overview.md#project-delivery-coordination "Enable architecture, engineering, construction (AEC) and operations teams to easily work with linked data and documentation") | ✓ | ✓ | ✓ |
| [Other industry solutions](overview.md#industry-solutions "Rapidly deploy industry-specific apps and solutions")[^9] | ✓ | ◐ | ◐ |

✓_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]: Requires [ArcGIS Workflow Manager](https://doc.esri.com/en/arcgis-workflow-manager/latest/)
[^3]: Requires integration with a [location services system](/en/framework/system-patterns/location-services/overview.md) or additional data, such as [ArcGIS Street Map Premium](https://www.esri.com/en-us/arcgis/products/arcgis-streetmap-premium/overview)
[^4]: Requires some Windows/Linux infrastructure
[^5]: Requires [ArcGIS Knowledge Server](https://enterprise.arcgis.com/en/knowledge/)
[^6]: Requires [ArcGIS Notebook Server](https://enterprise.arcgis.com/en/notebook/)
[^7]: Full capability spans multiple system patterns
[^8]: Requires [ArcGIS Business Analyst Enterprise](https://www.esri.com/en-us/arcgis/products/arcgis-business-analyst/applications/enterprise)
[^9]: Some industry solutions only available on SaaS


See the self-service mapping, analysis, and sharing [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 self-service mapping, analysis, and sharing 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 self-service mapping, analysis, and sharing system deployment pattern. The information presented here is not meant to be exhaustive, but rather highlights key considerations for designing and implementing self-service mapping, analysis, and sharing 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.
- The [SaaS](/en/framework/system-patterns/self-service-mapping-and-sharing/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 self-service mapping, analysis, and sharing 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.
- It is common for organizations to deploy more than one self-service mapping, analysis, and sharing system within their organization. Common drivers for this include, but are not limited to:
 - Separate systems for internal and external use, with the former commonly deploying on Windows, Linux, or Kubernetes and the latter commonly deploying via SaaS.
 - Domain or workflow-specific systems, for example deploying separate systems for urban planning, analysis, and general purpose self-service mapping and sharing.
 - Regional or departmental systems that establish strong boundaries and governance control across geographic or organizational units. 
- Self-service mapping, analysis, and sharing systems rely heavily on location services provided by a [location services system](/en/framework/system-patterns/location-services/overview.md). These two system pattens are often combined, especially when deployed as SaaS. The deployment of your location services system(s) should be taken into consideration when designing a self-service mapping, analysis, and sharing system.

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.