> 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/architecture.md).
# Architecture
For developers starting with CARTO, this architecture diagram may help understand how their applications are going to interact with the platform.
The most important concepts about the architecture are:
* **CARTO always connects to your data warehouse**: by using live connections to your data warehouse, we can build performant and scalable applications without having to manage complex data migration processes, while respecting your company's governance and security policies.
* **To visualize data in a map you will be using deck.gl:** this visualization library is a requirement. If you're using other visualization libraries at the moment, there are strategies to [combine or overlay](https://deck.gl/docs/get-started/using-with-map) them.
{% hint style="success" %}
**Learn more**
In order to understand what each of these pieces do, the [Libraries and APIs section](/carto-for-developers/key-concepts/apis.md) will cover each component in detail.
{% endhint %}
## Where the frontend runs
In this diagram the frontend is yours to host, wherever you choose. CARTO can also host it for you: with [Hosted Apps](/carto-for-developers/key-concepts/hosting-your-application.md), currently in Private Preview, you deploy the built files and CARTO serves them behind your organization's login, running as the signed-in user. Everything else in the architecture stays the same, since the application still calls the CARTO APIs directly against your data warehouse connections.
## JavaScript frameworks
**CARTO is designed to work with any JavaScript-based application**: CARTO will help you accelerate your geospatial development regardless of the framework (eg: React, Vue, Angular...) or stack you're using, as long as your web application uses JavaScript.
## TypeScript support
We recommend using TypeScript when building your apps. You can find more info about this [here](https://deck.gl/docs/get-started/using-with-typescript).
---
# 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/architecture.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.
