> For the complete documentation index, see [llms.txt](https://docs.zingg.ai/zingg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zingg.ai/zingg/zingg-concepts/platform-infrastructure-vs-data-platform.md).

# Platform Infrastructure vs Data Platform

Where Zingg runs, which data it resolves

Two things that are easy to conflate but mean different things in Zingg's context. Platform infrastructure is where computation happens, such as the Databricks/Fabric/EMR/Glue/Dataproc/Docker Spark service or Snowflake compute that processes your data. A data platform is where your data lives - Snowflake tables, Databricks Lakehouse and Unity Catalog, OneLake, BigQuery, Redshift, or a file store like S3.

These are independent: you can have your data in Snowflake but run Zingg's computation on Spark. Zingg connects to the data platform and runs computations on whichever engine you configure.

{% hint style="success" icon="right-long" %}
**Read more:** [Connect data](/zingg/connect-your-data/pipes-and-data-connections.md) | [Install Zingg](/zingg/running-zingg/install-zingg.md)
{% endhint %}


---

# 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.zingg.ai/zingg/zingg-concepts/platform-infrastructure-vs-data-platform.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.