Use this page to understand licensing requirements when you deploy applications that use ArcGIS Location Platform.
Commercial and revenue-generating apps
You can deploy commercial and revenue-generating applications with ArcGIS Location Platform.
To remain compliant:
- Use access tokens generated from your ArcGIS Location Platform subscription for all ArcGIS location service requests.
- Follow the ArcGIS Location Platform agreement.
- Ensure all service calls are authenticated.
There is no fixed limit to the number of revenue-generating applications you can deploy, provided each app follows the terms.
Open-source libraries
You can use ArcGIS location services with open-source libraries, including:
You must still follow licensing and attribution requirements for ArcGIS services and data.
ArcGIS Living Atlas access
Although the ArcGIS Living Atlas website is publicly accessible, use of ArcGIS Living Atlas layers in your own application with ArcGIS Location Platform requires a custom license agreement.
For licensing details, contact ArcGIS Location Platform Sales.
Runtime licensing for native apps
If you build native apps with ArcGIS Maps SDKs for Native Apps:
- An API key alone does not provide Runtime deployment licensing.
- You must use a Runtime license string or supported user authentication model.
- A Lite level license is available with your account.
- Higher license levels and extensions require additional licensing.
See platform-specific Runtime licensing documentation:
- ArcGIS Maps SDK for .NET
- ArcGIS Maps SDK for Kotlin
- ArcGIS Maps SDK for Swift
- ArcGIS Maps SDK for Flutter
- ArcGIS Maps SDK for Qt
Attribution requirements
Attribution is required when your app uses Esri basemaps, data, or services.
This includes:
- Keeping required "Powered by Esri" attribution.
- Displaying data source attribution when required.
You cannot remove required Esri attribution while continuing to use Esri resources.
For implementation guidance, see Attribution and Basemap attribution.