Key concepts

There are a few interconnected concepts within tap:

Files

Files are the source for data. They can be uploaded individually or as part of folders.

tap currently supports the following file formats:

  • CSV
  • JSONL (optionally gzipped)
  • JSON (array)
  • Parquet
  • XLSX
  • ODS

Data

Data represents files that form a single dataset with a consistent schema. They are used by models and will ultimately be exposed via APIs.

Models

Models are SQL SELECT queries that allow cleaning, enriching and joining data and other models. The results can be downloaded or served via APIs.

See the SQL reference for supported functions and syntax.

APIs

APIs allow serving models on chosen domains and paths. Available query parameters are configured via API filters. API keys grant access to all API endpoints within a domain.

See the Filter reference for supported filters.

Domains

Domains define the hostname for your APIs.

Each tenent comes with a unique hostname (a tap subdomain), but get in touch if you'd like to bring your own.

API keys

API keys grant access to all APIs within a domain. They form a username:password key pair that allows you to control access and track usage of your APIs.

Storage

Storage represents the location of your files. They are also where optimised copies (materialisations) of your data and APIs.

Each tenant comes with dedicated, isolated storage, but get in touch if you'd like to bring your own. This will ensure your data is never stored at rest in tap infrastructure.

Looks good? Missing something you need? We need your feedback.

Let us know if you need to get your data and applications talking, or you want to save money on complex, inefficient data platforms and integration tooling. We'd love to discuss and see how tap could help.

tap is built by DigitalSociety – we build bespoke digital tools for complex requirements in web applications, data engineering and cloud.