# Storage Backends

[As described here](/topics/higher-level-topics/organizing-inbound-data/the-three-data-spaces.md), CsvPath Framework stores files in three protected spaces: 

* Source file staging (a.k.a. the named-files area)
* The csvpaths area (a.k.a. the named-paths area)
* The archive

Each of these areas can live in any of the five supported backends: 

* File system
* [SFTP](/topics/how-tos/storage-backends/s3-sftp-google-cloud-or-azure.md)
* [AWS S3](/topics/how-tos/storage-backends/aws-s3.md)
* [Azure](/topics/how-tos/storage-backends/azure.md)
* [Google Cloud Storage](/topics/how-tos/storage-backends/google-cloud-storage.md)

CsvPath Framework generates events during staging named-files, loading named-paths, and running named-paths groups against named-files to populate the archive. Events are stored in the file backends as `manifest.json` files. In addition to your main file backend options, you can also choose to store events in a [SQL database](/topics/how-tos/postgres-and-mysql.md) and/or send them to an observability system that supports [OpenTelemetry](/getting-started/dataops-integrations/opentelemetry.md) or [OpenLineage](/getting-started/dataops-integrations/openlineage.md). 


---

# 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://www.csvpath.org/topics/how-tos/storage-backends.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.