ArcGIS Online vs self-hosted or managed Open GIS
Compare ArcGIS Online, self-hosted GIS and managed open services across sharing, credits, field workflows, operating responsibility and total cost.
Editorial review: 2026-09-23
ArcGIS Online, self-hosted open GIS and managed open GIS buy different operating arrangements. Compare the same user tasks and service expectations. A small team may prefer a managed product even when open software is technically capable; a public data platform may value deployment control and a portable service contract.
Separate software choice from operating choice
Self-hosting means your organization owns more deployment, security, backup and incident work. Managed open GIS transfers some of that work to a provider, but the contract must define exactly which tasks are included. ArcGIS Online supplies a managed platform whose administration, entitlements and consumption still need active management.
Esri's administration guide covers members, identity, sharing, applications and usage. The credit documentation distinguishes consumption categories. Do not reduce the platform to a per-user price or assume every request consumes credits.
| Decision | ArcGIS Online | Self-hosted open GIS | Managed open GIS |
|---|---|---|---|
| Infrastructure operation | Platform provider | Your team | Contracted provider |
| Users and sharing | Platform roles/items/groups | Selected identity/catalog design | Product and contract dependent |
| Applications | Included/purchased ecosystem | Select or build required apps | Included product plus integrations |
| Data location/control | Available service terms/options | Chosen infrastructure | Contractual hosting arrangement |
| Upgrades | Platform release model | Your release responsibility | Agreed maintenance policy |
| Cost drivers | Entitlements and relevant consumption | Infrastructure, labor and support | Subscription, usage and project scope |
| Exit | Export supported data/configuration | Preserve deployable system | Verify data, config and transition rights |
Inventory the content behind one web map
List each map's layer sources, hosted views, symbology, popups, forms, attachments, expressions, sharing groups and downstream applications. Check whether the organization owns the data or depends on another provider's service. An exported vector file may preserve geometry and attributes while losing the application behavior surrounding it.
Choose one representative public map and one restricted editing workflow. Rebuild them in the candidate operating model. Ask actual users to complete the tasks; compare editing validation, mobile behavior, accessibility, search and export. If a dashboard or form is essential, include it in the pilot rather than treating it as future polish.
Price a complete year before extrapolating
Use your actual subscription, member entitlements and observed consumption. Separate storage, analysis, premium services and other relevant categories according to current documentation. Seasonal projects can make one quiet month a poor annual baseline. Review a representative period and planned growth, including attachments and data retained for offline/sync workflows.
For the alternative include hosting, transfer, backups, monitoring, support, internal administration and application maintenance. Add migration, training and overlap as transition costs. If a managed provider advertises “unlimited users,” inspect limits on storage, requests, processing, environments and support hours before assuming unlimited capacity.
The TCO guide and calculator make those inputs explicit. Use one currency and a dated conversion assumption if contracts differ; the calculator does not fetch exchange rates.
Questions that reveal the operating model
| Ask | Evidence to request |
|---|---|
| Who restores a deleted or corrupted dataset? | Restore exercise and retention scope |
| Who patches server and application dependencies? | Version policy and maintenance responsibilities |
| What happens when usage grows? | Limits, alerts, upgrade path and quoted charges |
| Can another provider take over? | Data/configuration export and deployment handover |
| How are restricted users removed? | Revocation test through actual APIs and apps |
| What is excluded from support? | Written exclusions and escalation path |
Open-source licensing does not automatically grant ownership of all custom work, unrestricted use of basemap data or portability of a provider's managed environment. Read the actual agreements and data licenses; the technical pilot should demonstrate the export you expect to rely on.
When each option makes sense
Retain ArcGIS Online when the integrated applications fit, administrative capacity is limited and actual costs are acceptable. Consider self-hosting when control is required and operators are available. Consider managed open GIS when portability and component choice matter but internal operations should remain small. A hybrid can publish selected public data openly while retaining applications that have a clear business advantage.
The decision should name the workflows that move, those that remain, who operates each, and when the economics are reviewed. For field-dependent work, include QField versus Field Maps in the same assessment; replacing a web map does not automatically migrate offline crews.