The license and distribution requirements for deploying your application are determined by the type of application you develop and the API you use. This includes web, native, and service-based applications. This help topic covers the information you need to be aware of before you deploy your solution.
All ArcGIS Location Platform accounts have a subscription plan associated with them. Each subscription comes with a free tier of location services and with pay-as-you-go disabled. You can use this account to build applications that access location services with either API keys or OAuth 2.0, but it only provides access to the set of location services with a free tier of usage. To access all location services, you need to enable pay-as-you-go. See the table below for a list of the functionality that is available.
If your application uses more than the free tier in a given billing cycle, service access will be disabled unless you enable pay-as-you-go. Pay-as-you-go can be configured in your account subscription billing settings. Learn more about pay-as-you-go and billing.
All location service transactions are charged in USD. Learn about service transaction fees on Pricing.
Web applications
Web applications are built with ArcGIS Maps SDK for JavaScript, open source, or other APIs.
To build and deploy a web application, you need:
- An ArcGIS Location Platform account.
- Agree to the Terms of Use.
Example applications
- Client-side, static, and single web page applications
- Dynamic web applications using front-end and back-end technologies
- Progressive web apps (PWA)
- Rich Internet Apps (RIAs, desktop or mobile hybrid apps encapsulating web apps)
- Browser and IDE extensions
NOTE: There may be other types of web applications you can develop that are not listed here.
Native applications
A native application is built with one of the ArcGIS Maps SDKs for Native Apps and deployed to desktops, mobile devices, or embedded systems. Native applications may be deployed using a variety of installer technologies, such as Microsoft Windows Installer (.msi), or to the Google Play store, Apple App Store, Microsoft Store, or ArcGIS Marketplace.
To build and deploy a native application, you need:
- An ArcGIS Location Platform account.
- Agree to the Terms of Use.
- An ArcGIS Runtime license string or implement user authentication. This "unlocks" applications and removes the "Licensed for Developer use Only" watermark on maps and from the console log.
To learn how to get an ArcGIS Runtime license string, visit the Licensing and deployment sections below:
- ArcGIS Maps SDK for .NET
- ArcGIS Maps SDK for Swift
- ArcGIS Maps SDK for Kotlin
- ArcGIS Maps SDK for Java
- ArcGIS Maps SDK for Qt
Example applications
- Mobile apps for phones or tablets
- Desktop apps (Linux, macOS, or Windows)
- Smart devices (Smart watches, bands, Apple TV)
- Embedded (custom hardware devices, Arduino, Raspberry, ...)
NOTE: There may be other types of native applications you can develop that are not listed here.
Game engine applications
A game engine application is built with one of the ArcGIS Maps SDKs and deployed to any supported device, operating system, or embedded system.
To build and deploy a game engine application, you need:
- An ArcGIS Location Platform account.
- Agree to the Terms of Use.
- Review Deployment in the ArcGIS Maps SDK for Unity guide.
Example applications
- Apps for Android or iOS phones or tablets
- Stand alone Windows Platform or Universal Windows apps
- macOS applications
- AR/VR applications for XR platforms
NOTE: There may be other types of game engine applications you can develop that are not listed here.
Service-based applications
Service-based applications are those that use ArcGIS location services and may not have an end-user interface. They can consume location services, APIs, libraries, or other back-end functionality. A service-based application can be triggered by user interactions, such as services or processes built with non-Esri client-side APIs, webhooks, or other scheduled processes.
Typically these applications are built using REST API service endpoints, modules from ArcGIS REST JS or ArcGIS Maps SDK for JavaScript inside a Node.js app, or the ArcGIS API for Python.
To build and deploy a service-based application, you need:
- An ArcGIS Location Platform account.
- Agree to the Terms of Use.
Example applications
- Web Services
- REST applications
- Scripting applications
- Internal libraries
- Developer APIs
- Machine-to-machine
NOTE: There may be other types of service-based applications you can develop that are not listed here.
Basemap attribution
Basemap attribution is required when building and deploying mapping applications that use the Basemap styles service. Learn more on Basemap attribution.
Esri data
The Terms of Use for Esri data stored in ArcGIS Living Atlas of the World are defined in the Terms of Use section of an item page. In most cases, the terms reference the Esri Master Agreement. The Credits section contains the data source providers.
3rd party data
Many organizations host their own content and data in ArcGIS and make it available through ArcGIS Online, ArcGIS Hub or the ArcGIS Living Atlas of the World. Before using this data in your applications, you must comply with the Terms of Use and you may be required to display attribution if defined by the organization. The terms are typically unique from each data provider.
Deployment support capabilities
Reference the following table for a quick view of the types of deployment opportunities based on the ArcGIS services implemented in your application:
- 1. You need to contact Esri Sales.
- 2. You need to sign up as an Esri partner.