Skip to content
Draft — this is a structural skeleton, not documentation. Most pages are empty stubs listing what they will cover. Nothing here is finished, and some of it describes parts of Baseout that are not built yet.

Glossary

The terms below are taken from the project’s own naming specification. This is the subset that is settled; it is not the whole vocabulary yet.

TermMeans
OrganizationThe top-level customer entity. Billing lives here.
SpaceA container inside an Organization, bound to exactly one platform. Has its own backups, destination and settings.
PlatformA supported source system. Airtable in V1.
SourceA connection between your account and a platform — for Airtable, OAuth or a personal access token.
DestinationWhere backup files are written. File storage is required; a database is optional.
BaseAn Airtable base visible through a Source.
Table / Field / Record / ViewAirtable’s own terms, used unchanged.
AttachmentA file on an attachment-type field.
Automation / InterfaceAirtable’s own terms. Neither can be exported by Airtable’s API.
Backup runOne execution of the backup process. An immutable log entry.
SnapshotThe output of a backup run — what you restore from.
RestoreWriting a snapshot back into Airtable. Always into new tables, never over the original.
Health scoreA per-base 0–100 grade over schema cleanliness, data quality and configuration.
ChangelogA time-ordered diff between backups — one for schema, one for data.
PresetA saved base + table + filter + field selection on the Data section.

Airtable already uses “Workspace” for its own concept. Using the same word for ours would be ambiguous the moment someone has several Airtable workspaces inside one Baseout Space.

Terms deliberately left out because their meaning is not settled: the plan and tier names, the credit and usage vocabulary, and the backup-mode names (static, dynamic, instant) which appear in the specifications but not in any shipped screen.