ArcGIS Enterprise is Esri’s self-hosted mapping platform that you run on your own infrastructure, whether on-premises or in your private cloud. It delivers the same web GIS capabilities as ArcGIS Online, with the difference that your organization controls the servers, the data, and the security. Most teams should start with ArcGIS Online and move to Enterprise only when a specific requirement demands it.
This guide explains what ArcGIS Enterprise is made of, how a base deployment fits together, and the concrete reasons an organization chooses to run it. If you are weighing the software-as-a-service option against the self-hosted one, the order of evaluation matters: confirm that ArcGIS Online cannot meet the requirement before you take on the responsibility of running Enterprise yourself.
Start with ArcGIS Online
ArcGIS Online is Esri’s cloud platform, hosted and maintained by Esri. You sign in, create content, and publish hosted feature services without managing any servers. For the majority of organizations, it covers mapping, analysis, dashboards, StoryMaps, and field apps with no infrastructure to patch or scale.
ArcGIS Pro is the professional desktop application most teams pair with Online for authoring, advanced analysis, and data management. Together, ArcGIS Online and ArcGIS Pro handle a large share of real-world GIS work. Enterprise enters the picture when control, data residency, or integration requirements push beyond what a shared cloud can offer. Our detailed comparison of ArcGIS Enterprise versus ArcGIS Online walks through that decision in depth.
The components of ArcGIS Enterprise
A base ArcGIS Enterprise deployment is built from four software components that work together. Understanding them helps you plan capacity and avoid surprises during setup.
- ArcGIS Server: the engine that hosts services. In a base deployment it acts as the hosting server, publishing hosted feature services and performing analysis.
- Portal for ArcGIS: the web front end where users sign in, create maps and apps, and share content. This is the part that feels like ArcGIS Online to your users.
- ArcGIS Data Store: the managed data storage that backs hosted feature services, including the relational store, the tile cache store, and the spatiotemporal store.
- ArcGIS Web Adaptor: the component that integrates the deployment with your web server and presents a clean, secure set of URLs.
These four together form what Esri calls the base ArcGIS Enterprise deployment. Beyond the base, you can add server roles such as the GeoAnalytics, Image, or GeoEvent capabilities, and you can federate additional ArcGIS Server sites for specialized workloads.
How a base deployment fits together
In a typical single-machine base deployment, Portal for ArcGIS provides the user experience, a federated ArcGIS Server is designated as the hosting server, and ArcGIS Data Store holds the hosted layers. The Web Adaptor ties everything to your web server so users reach the portal through a friendly address. Larger organizations split these roles across multiple machines and add high availability, but the logical pieces stay the same.
Because you own the deployment, you also own the operational work: installing updates, managing certificates, backing up the data stores, and monitoring performance. That responsibility is the trade you accept in exchange for control. Many teams underestimate it, which is one reason a planned, well-documented deployment matters so much.
When you actually need ArcGIS Enterprise
Enterprise is the right answer for specific, identifiable reasons. If none of these apply, ArcGIS Online is usually the simpler and cheaper choice.
- Data residency and sovereignty. Regulations or policy require that data and services stay inside your own network or a specific jurisdiction.
- Integration with internal systems. You need GIS services close to databases, asset management systems, or applications that live behind your firewall.
- Advanced server capabilities. Workloads such as large-scale raster analysis, real-time data with GeoEvent, or big-data analysis with GeoAnalytics call for dedicated server roles.
- Branched versioning for multi-user editing. Enterprise geodatabases support branched versioning, which lets many editors work concurrently without data conflicts.
- Custom security and authentication. You need to plug into your own identity provider or meet security controls that a shared cloud cannot accommodate.
The branched versioning case is worth highlighting, because concurrent editing is a frequent driver. If your need centers on that capability, our guide to branched versioning for multi-user editing explains how it works in practice.
ArcGIS Online vs ArcGIS Enterprise at a glance
| Consideration | ArcGIS Online | ArcGIS Enterprise |
|---|---|---|
| Hosting | Esri-managed cloud | Your infrastructure |
| Setup effort | Minimal, sign in and go | Significant, deploy and configure |
| Maintenance | Handled by Esri | Handled by your team |
| Data location | Esri cloud | Your network |
| Branched versioning | Not available | Available with enterprise geodatabase |
| Best first choice for | Most organizations | Specific control or integration needs |
Planning a deployment well
If you have confirmed that Enterprise is the right path, a few planning steps prevent the most common problems.
- Size for peak, not average. Account for concurrent users and the heaviest analysis you expect, then add headroom.
- Decide on high availability early. Adding redundancy after the fact is harder than designing for it up front.
- Plan backups and upgrades. Document how you will back up the data stores and how you will move through version upgrades.
- Map your security model. Settle authentication, certificates, and network access before users arrive.
- Right-size your licensing. Match user types and server roles to real needs so you do not pay for capacity you will not use.
Getting licensing right is a recurring source of waste. Our guide on how to optimize your Esri license investment covers practical ways to align spend with usage.
Licensing and user types in ArcGIS Enterprise
Licensing is where ArcGIS Enterprise budgets often drift, because the model has several moving parts. A clear understanding up front prevents paying for capacity you will not use.
Named users are assigned a user type that determines what they can do, from viewing content to creating and publishing it. Add-on app licenses and server-side capabilities, such as the Image or GeoAnalytics roles, are licensed separately. The practical guidance is to map real roles to user types before purchase: most organizations have many viewers, a smaller group of editors, and a handful of authors, and pricing the deployment around that shape avoids over-buying creator licenses for people who only need to view dashboards.
Capacity planning works the same way. Server roles you do not need add cost and maintenance, so add them only when a workload genuinely requires them. Reviewing usage on a regular cadence keeps the deployment aligned with actual demand rather than the demand you imagined at purchase time.
Migrating from ArcGIS Online to ArcGIS Enterprise
When an organization outgrows the shared cloud, the move to Enterprise is a planned project rather than a flip of a switch. The good news is that content built on web maps and feature services is portable.
- Inventory your content. Catalog the maps, layers, apps, and dashboards in use, and identify which ones must move.
- Stand up the deployment. Install and configure the base ArcGIS Enterprise components, then validate the portal and hosting server.
- Migrate data and content. Move hosted feature services and re-create or transfer maps and apps, verifying symbology and pop-ups along the way.
- Re-establish sharing and security. Recreate groups, roles, and sharing rules to match your new security model.
- Validate and cut over. Test thoroughly with real users before retiring the old workflow.
A staged migration, with both environments running in parallel for a period, lowers risk and gives users time to adjust. Rushing the cutover is the most common cause of disruption.
Getting expert help
An ArcGIS Enterprise deployment is a meaningful engineering project, and the cost of a misconfigured one shows up later as downtime and rework. GeoLever’s ArcGIS platform consulting (GeoConsult, $5,000 to $15,000 per project) covers deployment planning, configuration, and migration, delivered by a Certified ArcGIS Expert. You can scope the work through the GeoLever contact page.
Frequently Asked Questions
What is the difference between ArcGIS Enterprise and ArcGIS Online?
ArcGIS Online is Esri’s hosted cloud platform that requires no infrastructure from you. ArcGIS Enterprise is the same web GIS capability deployed on your own servers, giving you control over data location, security, and integration. Online is the better first choice for most organizations.
What are the components of ArcGIS Enterprise?
A base deployment has four components: ArcGIS Server (the hosting engine), Portal for ArcGIS (the web front end), ArcGIS Data Store (managed storage for hosted layers), and ArcGIS Web Adaptor (integration with your web server). Additional server roles can be added on top.
When should an organization choose ArcGIS Enterprise?
Choose Enterprise when you need data to stay inside your network, deep integration with internal systems, advanced server capabilities such as real-time or big-data analysis, branched versioning for concurrent editing, or custom security. If none of these apply, ArcGIS Online is usually simpler and more cost-effective.
Does ArcGIS Enterprise support multi-user editing?
Yes. With an enterprise geodatabase, ArcGIS Enterprise supports branched versioning, which lets many editors work on the same data concurrently without conflicts. This is one of the most common reasons organizations move from ArcGIS Online to Enterprise.
Is ArcGIS Enterprise hard to maintain?
It carries real operational work: updates, certificates, backups, and monitoring all fall to your team. The effort is manageable with planning and documentation, but it is the main trade-off against the simplicity of the Esri-hosted ArcGIS Online option.
