# Data Architecture

The following graph showcases our data archicture:

<figure><img src="/files/FjYExaxMAVwAv0YicyHD" alt=""><figcaption><p>Aterio's Data Architecture</p></figcaption></figure>

### Data Sources

Our data pipeline begins by aggregating a wide range of structured and semi-structured data from multiple sources, including:

* APIs
* External and Internal Databases
* Files (e.g. csv, json, parquet)
* RSS Feeds

We standardize these inputs to keep traceability and consistency.

### Data Processing (ETL)

The data flows into our GCP environment where we run ETL processes orchaestred to transform and  structure data inside our Data Warehouse and Data Marts.

### Data Delivery

After the data is processed and validated, it's distributed through multiple delivery mechanisms to meet diverse client needs, including:

* Databricks
* Snowflake
* AWS S3
* GCP (Biquery & Cloud Storage)
* Aterio's Marketplace
* Aterio's API


---

# Agent Instructions: 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 current page URL with the `ask` query parameter:

```
GET https://knowledge.aterio.io/how-we-build-the-data/data-architecture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.