Core concepts

A short glossary of the moving parts. Each links to its full reference.

Dashboard

A JSON document with a name, optional settings, and a layout array of tiles. See Dashboard JSON.

Tile

One panel. A tile binds a position, an optional execution (exec + query), and a block. Tiles also declare relationships: depends_on (ordering) and triggered_by (what re-runs them). See Tiles.

Block

The renderer for a tile's result — plotly, table, markdown, image, raw_html, input_select, or input_range. A block renders valid content or raises a clear error. See Blocks.

Load mode

When a tile executes: always, load_once, manual, interval, or input. See Tiles.

Exec type

How a tile gets data: athena (a SQL query), cache (a precomputed S3 object), or lambda (a module function). See Execution types.

Source macro

A SQL-time reference to raw S3 data — !parquet('s3://...') or !csv('s3://...') — that StrataBI compiles into a Glue external table. See Source macros.

Artifact

A result written to your S3 by an async run. Artifacts back tiles and can be exposed for download. See Async & artifacts.

Module

A customer-owned Lambda registered with StrataBI and invoked by exec.type: lambda. See Modules.