> 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/guides.md). # Guides After you've become familiar with the [key concepts](/carto-for-developers/key-concepts.md) of CARTO for Developers, and after your first experiments with [CARTO + deck.gl](https://github.com/CartoDB/gitbook-documentation/blob/master/carto-for-developers/key-concepts/carto-for-deck.gl) and our [APIs](/carto-for-developers/reference/carto-api.md), it's time to build complete solutions. To help you design your solution and understand how the different pieces work together, we've build these complete **guides,** based on real use cases:


Build a public application	Using CARTO to quickly build a simple and performant geospatial application that everyone in the internet can access	Build a public application	Public App.png
Build a private application	Design and develop an application that only users in your CARTO organization will be able to access, after they log in	Build a private application	Private App Guide Diagram.png
Build a private application using SSO	Leverage an external identity provider setup in CARTO to authenticate new and existing users in your private application		Frame 1 (7).png
Hosting your application in CARTO	Let CARTO host your application and sign in its users, so it is only accessible to people in your CARTO organization	Hosting your application in CARTO
Visualize massive datasets	Learn how to visualize massive geospatial datasets in a performance and cost-effective way (up to billions of rows)	Visualize massive datasets
Integrate CARTO into your existing application	Learn how to securely embed CARTO into your existing architecture providing fine-grained data access	Integrate CARTO in your existing application	Integrate CARTO in your existing application.png
Use Boundaries in your application	Create rapid aggregation of large data volumes within common or custom geographic boundaries such as zip codes	Use Boundaries in your application	Screenshot 2024-03-27 at 13.12.52.png
Avoid exposing SQL queries with Named Sources	With Named Sources, you can ensure your application does not expose the SQL used, maximizing compliance in some setups	Avoid exposing SQL queries with Named Sources	Named Sources.png
Managing cache in your CARTO applications	This guide covers how developers can adjust and manage the cache in their CARTO applications	Managing cache in your CARTO applications	cache.png
Build an AI-powered map application	Add natural language map interaction to your CARTO + deck.gl application using AI-powered tool calling	Build an AI-powered map application

--- # 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 dynamically 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/guides.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 `build a script that syncs our docs to a CMS` 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.