> For the complete documentation index, see [llms.txt](https://docs.carto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carto.com/carto-for-developers/key-concepts/carto-for-deck.gl/basemaps.md). # Basemaps CARTO is basemap-agnostic and is compatible with MapLibre, Google Maps, Amazon Location and Mapbox GL. [deck.gl](https://deck.gl) allows you to visualize the data in your warehouse, but it doesn't provide a map with contextual information (like streets, roads, restaurants, cities, rivers, etc.) — This is usually called a **basemap.** As you can imagine, most of the use cases require to have a basemap to give more context to your visualizations. **CARTO layer with a basemap:** {% embed url="" %} **CARTO layer without a basemap:** {% embed url="" %} CARTO is basemap-agnostic and lets you decide which client technology they want to use. The following options are available: * [CARTO basemap](/carto-for-developers/key-concepts/carto-for-deck.gl/basemaps/carto-basemap.md). * [Google Maps](/carto-for-developers/key-concepts/carto-for-deck.gl/basemaps/carto-google-maps.md). * [Amazon Location](/carto-for-developers/key-concepts/carto-for-deck.gl/basemaps/carto-amazon-location.md). * [Mapbox](https://deck.gl/docs/get-started/using-with-map). If you don't have any specific requirements in your app, we recommend you use the CARTO basemap as it doesn't require extra configuration neither makes you incur in additional costs. ### Basemap client libraries and costs When using a basemap you will need two things: the library to render the basemap and a backend API service to provide the data of the basemaps. The CARTO basemap service is included by default, with no additional costs, for all CARTO organizations. However, if a different basemap provider is used, the user will need to input their own API credentials for that provider and cover the costs for said provider. The cost of using a basemap service provided by a third-party will vary on the provider. | Technology | Client Library | Cost | | --------------- | -------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- | | CARTO basemap | [MapLibre GL JS](https://deck.gl/docs/developer-guide/base-maps/using-with-maplibre) | Included | | Google Maps | [Google Maps Javascript API](https://developers.google.com/maps/documentation/javascript/overview) | A Google Maps API Key must be provided, considering their own API pricing | | Amazon Location | [MapLibre GL JS](https://deck.gl/docs/developer-guide/base-maps/using-with-maplibre) | Amazon Location credentials must be provided, considering their own pricing | | Mapbox | [Mapbox GL JS](https://docs.mapbox.com/mapbox-gl-js) | A Mapbox Access Token must be provided, considering their own pricing | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.carto.com/carto-for-developers/key-concepts/carto-for-deck.gl/basemaps.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.