> 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/summary.md).

# Summary

In order to develop a web application in CARTO. These are the general steps to follow:

1. **Connect:** You need to [connect](/carto-user-manual/connections.md) your CARTO organization to your data warehouse: [BigQuery](https://cloud.google.com/bigquery), [Redshift](https://aws.amazon.com/redshift/), [Snowflake](https://www.snowflake.com/), [Databricks](https://www.databricks.com/), [Oracle](/carto-user-manual/connections/oracle.md), [PostgreSQL](/carto-user-manual/connections/postgresql.md), or using the ready-to-use [CARTO Data Warehouse](/carto-user-manual/connections/carto-data-warehouse.md).
2. **Authenticate:** The CARTO libraries and APIs will then require a valid [token](/carto-user-manual/developers/managing-credentials/api-access-tokens.md), obtained from any of the strategies explained in [Authentication Methods](/carto-for-developers/key-concepts/authentication-methods.md) section.
3. **Build:** The next step is to build a web application, using the any Javascript framework of your choice, such as [React](https://react.dev/), [Angular](https://angular.io/), [Vue.js](https://vuejs.org/), etc. Use the [CARTO Libraries and APIs](/carto-for-developers/key-concepts/apis.md) to accelerate your geospatial development.
   1. Use `@carto/api-client` to integrate your CARTO data sources
   2. Use `@deck.gl` and `@deck.gl/CARTO` to visualize your data in a map.
   3. Use the CARTO APIs for extra functionality: SQL API, Geocoding, etc.
   4. You can [embed or retrieve maps](/carto-for-developers/key-concepts/rapid-map-prototyping.md) and layer configurations from CARTO Builder.
4. **Charts, widgets, interactivity and filtering:** To create interactive charts and widgets that stay synchronized with your map, you should use [CARTO Widgets](/carto-for-developers/key-concepts/charts-and-widgets.md)
5. **AI-powered interaction (optional):** Add [natural language map control](/carto-for-developers/key-concepts/ai-powered-map-interaction.md) to your application using `@carto/agentic-deckgl`, so users can interact with the map through chat.
6. **Deployment:** Finally, you just need to choose where to deploy your CARTO application. Most applications built using CARTO do not need additional backend services, and therefore, can be deployed in a service that simply serves static files like [Firebase Hosting](https://firebase.google.com/docs/hosting) or [Heroku](https://www.heroku.com/).
   1. If the application is for people inside your CARTO organization, you can also [let CARTO host it](/carto-for-developers/key-concepts/hosting-your-application.md) with Hosted Apps, currently in Private Preview: deploy the built files with `carto app deploy`, and CARTO serves them behind your organization's login, with no hosting or login of your own to set up.


---

# 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/summary.md?ask=<question>&goal=<user_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.