ArcGIS Online vs ArcGIS Enterprise: a decision guide

Every ArcGIS licensing conversation eventually arrives at the same fork: ArcGIS Online, Esri's software-as-a-service, or ArcGIS Enterprise, the same capabilities installed on infrastructure you control. The web maps, Field Maps projects, Dashboards and Experience Builder apps look identical on both. What differs is the contract you sign with reality: where data sits, who can reach it, what happens when the network is gone, and how the bill arrives.

Same platform, different contract

ArcGIS Online is an Esri-operated organisation in an Esri-chosen cloud region. You get hosted feature layers, tile and scene layers, the full set of app builders, and Esri handles upgrades, scaling and availability. You pay per named user (user types) and, for storage, analysis, geocoding and some premium content, in credits.

ArcGIS Enterprise is the same portal experience installed on your servers or cloud accounts: Portal for ArcGIS, ArcGIS Server, ArcGIS Data Store and the Web Adaptor as a base deployment, extended with Image Server, GeoEvent Server, Notebook Server and others as needed. You choose the database (PostgreSQL, SQL Server, Oracle, SAP HANA), the identity store, the network boundary and the upgrade cadence — and you own all of it.

Interactive decision flow

Answer the four questions below. The recommendation updates as you go; the sections that follow explain why each factor weighs what it does.

Data residency and network boundary

This is the factor most likely to settle the question on its own. If a regulation, a contract or an information-security policy names a jurisdiction or a network your data may not leave, ArcGIS Online is ruled out for that data unless Esri's region options satisfy the clause and your reviewers accept a SaaS tenancy. Government, defence, utilities and healthcare clients routinely have such clauses; most commercial and public-facing use cases do not.

Enterprise lets you put the whole stack behind your own boundary — an on-premises data centre, a sovereign cloud region, or an AWS/Azure account under your own controls. It also lets you keep the enterprise geodatabase inside the same boundary and register it with ArcGIS Server, so authoritative data is never copied into a hosted store at all.

Identity and access

Both platforms sign users in through your identity provider with SAML 2.0 or OpenID Connect, so “we use Entra ID / Okta” does not decide anything. Two situations do:

• Windows-domain users on a network with no internet path. Enterprise supports Integrated Windows Authentication against Active Directory and can be installed entirely disconnected. Online cannot be reached at all.
• Mostly anonymous public access with a small editing team. Online's sharing model, CDN-backed tiles and zero-maintenance hosting fit this well; standing up Enterprise for a public map is usually over-engineering.

Either way, plan the group and role model before you create content. Migrating items between portals later is possible with the ArcGIS API for Python, but ownership, sharing and item IDs are the parts that hurt.

Offline and disconnected operation

Field crews taking map areas offline and syncing in the evening is a solved problem on both platforms: enable sync on the feature layer, define preplanned offline areas, and Field Maps or a Maps SDK app does the rest. That requirement alone does not push you to Enterprise.

Whole sites running disconnected for days does. A vessel, a remote plant, a training exercise or a tactical unit needs the portal itself to be reachable without the internet — a disconnected Enterprise deployment, often a small one, sometimes on a ruggedised laptop or a portable server. If the site later reconnects, distributed collaboration can push its edits to a central Enterprise or to ArcGIS Online.

1{
2  "capabilities": "Query,Editing,Create,Update,Delete,Sync,Extract",
3  "syncEnabled": true,
4  "syncCapabilities": {
5    "supportsAsync": true,
6    "supportsRegisteringExistingData": true,
7    "supportsSyncDirectionControl": true,
8    "supportsPerLayerSync": true,
9    "supportsPerReplicaSync": false,
10    "supportsRollbackOnFailure": true,
11    "supportsAttachmentsSyncDirection": true
12  },
13  "editorTrackingInfo": {
14    "enableEditorTracking": true,
15    "enableOwnershipAccessControl": false,
16    "allowOthersToUpdate": true,
17    "allowOthersToDelete": false
18  }
19}

Cost model

Online is a subscription: user types per named user, plus credits consumed by hosted storage, spatial analysis tools, geocoding, routing and a few premium services. Predictable for viewing and editing workloads; surprising for organisations that run large analysis jobs or store many gigabytes of hosted data. The operational cost is close to zero — no servers, no patching, no upgrade projects.

Enterprise is licences plus everything underneath them: virtual machines or a Kubernetes cluster, a database, backups, TLS certificates, monitoring, and the people who run upgrades roughly once a year. There are no credits: analysis, imagery and geoprocessing scale with the hardware you give them, which is why imagery- and analysis-heavy programmes tend to land on Enterprise even without a residency constraint.

Side by side

When the answer is both

Many organisations we work with end up with an Enterprise deployment for authoritative and restricted content and an ArcGIS Online organisation for public maps, partner collaboration and quick prototypes. The glue is distributed collaboration: a trust between portals in which chosen groups are shared as copies or references and kept in sync on a schedule. The pattern works when three rules are written down and enforced:

1. One authoritative home per dataset. Edits happen in one portal; the other receives them. Two-way editing of the same layer is possible but a governance headache.
2. A publishing checklist. Who may share a group into collaboration, what metadata is mandatory, and which layers are never eligible.
3. Named-user hygiene. Decide whether staff have accounts in one portal or both, and automate provisioning so nobody keeps a spreadsheet.

Takeaways