Multi-tenancy on a data platform is usually a ticket and a week of console clicking. We made it a Terraform apply: a workspace, its catalog, its groups, its grants, and its dbt project — isolated by construction, reviewed in a pull request.
ReadA Terraform provider for the platform's own resources — warehouses, namespaces, grants, dbt projects, contracts, ontologies — managed in HCL, in a repo, in a pull request, with a plan you can read before you apply.
ReadEvery managed data platform asks you to put your data, identities, and queries in the vendor's plane. This one doesn't. Data, identity, catalog, compute, and policy — all five in infrastructure you control, by construction.
ReadAn honest read of where this platform sits against Databricks, Snowflake, and iomete — on the one axis that decides the choice: how much control you keep versus how much operation you hand off. Including where we lose.
ReadThe map of the platform: an assembly of open-source parts behind a Backend-for-Frontend that holds your token and enforces your identity at every hop. What each surface does, how a request flows, and where the cliffs are.
Read