When you deploy an ArcGIS Location Platform application, your choices affect how you access services, manage costs, and meet attribution and data-use requirements. Use this guide to review supported deployment options, prepare for production billing, and understand the compliance requirements for your application.

In this topic, you will learn about:

Deployment support capabilities

Your ArcGIS Location Platform subscription supports the deployment options below.

ArcGIS Location Platform subscription
Build and deploy private applications
Build and deploy public applications
Build and deploy non-commercial applications
Build and deploy commercial applications
Build web and native applications with ArcGIS and open source APIs
Build and deploy applications that access private content in ArcGIS
Distribute applications through app stores
Build and deploy applications with offline capability1
Full supportPartial supportNo support
  • 1. Contact Esri sales.

Operational readiness

As you build and deploy your application, enable pay-as-you-go so your services keep running once a service exceeds its free tier. Every ArcGIS Location Platform account includes:

  • A free tier for select location services.
  • Pay-as-you-go disabled by default.

You can use API keys or OAuth 2.0 with the free tier. As part of your production readiness review, evaluate your expected service usage, authentication strategy, monitoring approach, and billing configuration.

Billing guidance

The table below shows what to expect in common deployment scenarios. For more detail, see the pricing documentation.

ScenarioFree tier enabledPay-as-you-go enabledExpected behavior
Testing or low usageYesNoPartial service access
Usage exceeds the free tierYesNoService access disabled
Production deploymentYesYesFull service access
High-volume or scaling applicationYesYesContinued access with usage-based billing

Location service transactions are charged in USD.

Production readiness checklist

Before you release, make sure you have:

  • Selected the correct deployment type.
  • Chosen an authentication method that matches your access requirements.
  • Enabled pay-as-you-go for production workloads.
  • Verified expected usage against service limits and costs.
  • Reviewed required attribution and data terms.

Compliance and attribution requirements

Basemap attribution

When you use basemap data in a mapping application, include the required provider attribution. This satisfies the applicable licensing and attribution requirements.

You need basemap attribution when you build and deploy a mapping application that uses the Basemap Styles service.

Data terms and attribution

Data terms explain how you can use data, while attribution requirements explain how to credit its providers. The requirements depend on the data type and source. ArcGIS Location Platform provides access to Esri and third-party data through ArcGIS Online, ArcGIS Hub, and ArcGIS Living Atlas.

Esri data

Esri data includes basemaps, reference layers, demographic data, and other content provided by Esri. If you use Esri data in your application, review the applicable terms of use and provide attribution when required.

Terms of use for Esri data stored in ArcGIS Living Atlas are defined on the item page for that data. In many cases, those terms reference the Esri Master Agreement. The item page also identifies data source providers in the Credits section.

Third-party data

Third-party data is data provided by someone other than Esri, such as a government agency, nonprofit organization, or commercial provider. These providers may host their content in ArcGIS and make it available through ArcGIS Online, ArcGIS Hub, or ArcGIS Living Atlas.

When you use third-party data in your application, review the provider's terms of use and provide attribution as required.

Before you use third-party data in your application:

  • Review the applicable terms of use.
  • Confirm whether attribution is required.
  • Follow any provider-specific requirements.