---
title: Selecting a deployment pattern for enterprise application hosting and management systems
source_url: "https://architecture.arcgis.com/en/framework/system-patterns/enterprise-app-hosting-and-management/selecting-a-deployment-pattern.html"
md_url: "https://architecture.arcgis.com/en/framework/system-patterns/enterprise-app-hosting-and-management/selecting-a-deployment-pattern.md"
---
# Selecting a deployment pattern for enterprise application hosting and management systems

Enterprise application hosting and management systems are typically deployed using one of four deployment patterns:

- [SaaS](/en/framework/system-patterns/enterprise-app-hosting-and-management/deployment-patterns/as-saas.md)
- [PaaS](/en/framework/system-patterns/enterprise-app-hosting-and-management/deployment-patterns/as-paas.md)
- [Windows/Linux](/en/framework/system-patterns/enterprise-app-hosting-and-management/deployment-patterns/as-server-software.md)
- [Kubernetes](/en/framework/system-patterns/enterprise-app-hosting-and-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. Whereas organizations that are building GIS capabilities into their existing applications may prefer a PaaS-based approach.

> [!NOTE]
> **Note**
> The capabilities as well as the considerations differ significantly 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 enterprise application hosting and management system differ between deployment patterns. The following matrix compares the specific capabilities supported by each of the deployment pattern. 

Capabilities used in an enterprise application hosting and 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** | **PaaS** | **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 "Create web applications with no-code or low-code") | ✓ | | ✓ | ✓ |
| [Site building](overview.md#site-building "Create hosted websites with no-code or low-code") | ✓ | | ✓ | ✓ |
| [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] | ◐ | | ✓ | |
| [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") | ✓ | ✓ | ✓[^4] | ✓[^4] |
| [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") | ✓ | | ✓ | ✓ |
| [Hosted Python notebooks](overview.md#applications "Incorporate Python-based analysis, administration, and automation") | ✓ | | ✓[^5] | ✓ |
| [Indoor GIS](overview.md#indoor-gis "Serve indoor maps and applications to broad groups of stakeholders")[^6] | ✓ | ◐ | ✓ | ✓ |
| [Mission management](overview.md#mission-management "Bring a geographic approach to command and control") | | | ✓[^7] | |
| [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]: Requires [ArcGIS Workflow Manager](https://doc.esri.com/en/arcgis-workflow-manager/latest/)
[^3]: Requires some Windows/Linux infrastructure
[^4]: 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)
[^5]: Requires [ArcGIS Notebook Server](https://enterprise.arcgis.com/en/notebook/)
[^6]: Full capability spans multiple system patterns 
[^7]: Requires [ArcGIS Mission Server](https://doc.arcgis.com/en/mission/latest/server/windows/server-welcome-what-is-mission-server.htm)
[^8]: Some industry solutions only available on SaaS


See the enterprise application hosting and 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 enterprise application hosting and 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 enterprise application hosting and management system deployment pattern. The information presented here is not meant to be exhaustive, but rather highlights key considerations for designing and implementing enterprise application hosting and management systems.

- Custom, full-code web applications require external web hosting capabilities (e.g., web server) for all deployment patterns.
- 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. 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/enterprise-app-hosting-and-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. 
- Organizations delivering apps to public stakeholders commonly use the [SaaS](/en/framework/system-patterns/enterprise-app-hosting-and-management/deployment-patterns/as-saas.md) or [PaaS](/en/framework/system-patterns/enterprise-app-hosting-and-management/deployment-patterns/as-paas.md) deployment patterns because of their built in scalability and internet accessibility. 
- The service level agreements (SLAs) for SaaS and PaaS differ. Review the [ArcGIS Online (SaaS) SLA](https://www.esri.com/content/dam/esrisites/en-us/media/legal/referenced-files/g-632-agol-service-level.pdf) and [ArcGIS Location Platform (PaaS) SLA](https://www.esri.com/content/dam/esrisites/en-us/media/legal/referenced-files/service-level-agmt-arcgis-platform.pdf) in more detail.
- Enterprise application hosting and management systems rely heavily on location services provided by a [location services systems](/en/framework/system-patterns/location-services/overview.md). These two system pattens are often combined, especially when deployed as SaaS or PaaS. The deployment of your location services system(s) should be taken into consideration when designing a enterprise application hosting and management system.
- In addition to some of the differences described above, some other extended capabilities differ notably between deployment patterns. Some differences to consider include:
 - Workflow management and automation is typically provided by [ArcGIS Workflow Manager](https://www.esri.com/en-us/arcgis/products/arcgis-workflow-manager/overview), which has both [ArcGIS Online](https://www.esri.com/en-us/arcgis/products/arcgis-workflow-manager/deployment/online) (SaaS) and [ArcGIS Enterprise](https://www.esri.com/en-us/arcgis/products/arcgis-workflow-manager/deployment/enterprise) deployment options. The capabilities of these two options differ, so review product documentation carefully in evaluating options.
 - Python-based analysis and automation is supported by all deployment patterns using the ArcGIS API for Python. The SaaS and Windows/Linux deployment pattens also support hosted Python notebooks managed within the GIS system, which provides additional capabilities and integration opportunities, such as the scheduling of notebooks. Please see [ArcGIS Notebooks](https://www.esri.com/en-us/arcgis/products/arcgis-notebooks/overview) for more information. Hosted Python notebooks are not currently supported for PaaS and Kubernetes deployment patterns.

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, consider that the information provided here is not exhaustive. 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.