StrataBI overview

StrataBI is an owned business-intelligence runtime for technical analytics teams. You describe a dashboard as a small JSON document; the runtime owns everything else — query execution, dependency ordering, async status, artifact loading, and module resolution. It runs entirely inside your own AWS account.

The core is deliberately small and explicit, which keeps the dashboard contract stable enough to generate against — by hand, or with an AI agent.

How it fits together

A dashboard is a list of tiles. Each tile declares three things: where it sits (layout), how it gets data (execution), and how it renders (a block).

text

dashboard.json ──> tiles ──> exec (Athena | cache | Lambda) ──> block (Plotly | table | ...)
                                     │
                                     └─> async results land in S3 as artifacts

Dashboards are declarative JSON. No imperative UI code.
Tiles bind layout, execution, and rendering for one panel.
Blocks render a result, or raise a clear error.
Exec types control how a tile gets data: Athena SQL, a cached S3 object, or a module Lambda.
Artifacts are first-class outputs, written to your S3 and optionally downloadable.
Modules are customer-owned Lambdas that extend compute, resolved through a registry.

Who it's for

Note

StrataBI assumes a technical operator. You bring an AWS account, an Athena/Glue catalog, and data in S3; StrataBI brings the runtime, the dashboard contract, and the deployment module.

Analysts author dashboards in JSON and read results.
Data engineers wire queries, source macros, and custom module Lambdas.
Operators deploy and maintain the runtime in their account.
Autonomous agents generate dashboards directly against the published schema.

Where to go next

New to StrataBI? Start with the Quickstart.
Want the full contract? Read Dashboard JSON.
Integrating an agent? See Agent integration.