# AirData

AirData is Airkit’s internal database. It allows you to conveniently structure and access data gathered from your Airkit apps and pulled from external systems. While it is technically capable of long-term storage, it is intended primarily to be used as a convenient interim database to keep track of data your applications need frequent access to, but not, ultimately, a source of truth.

Information in AirData is organized in the form of Objects, which can be created with any number of properties. The properties of each saved Object instance are displayed in tables:

![](https://3088276961-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC6qMwMGWBgxnN70QsDuH%2Fuploads%2Fgit-blob-badc9940317b327aa0e9e76f24de7a96b51caad8%2Fairdata-v182-0.png?alt=media)

Information saved to AirData is stored in [Org](../administration/airkit-organizations)-level collections called Datastores. Datastores cluster objects by [Profile](../building-apps/publishing/profiles-and-deployment-settings) rather than application, allowing the sharing of information between applications and the separation of information collected by different deployments of the same app. All applications within an Org have access to the same Datastores.

While AirData is technically stored as part of an Organization, it is accessed primarily in the Studio. [AirData Builder](../studio/builder-bar/airdata-builder) is where Objects associated with an app are created and managed, as well as where the associated data is displayed. To access AirData within the flow of an application, use AirData Queries to perform basic CRUD operations. Typically, this is done via the [AirData Request Data Operation](../data-operations/airdata-request-data-operation) in the [Connections Builder](../studio/builder-bar/connections-builder).
