> For the complete documentation index, see [llms.txt](https://www.csvpath.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.csvpath.org/topics/how-tos/storage-backends.md).

# 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).