Introduction

Meet RawTree, the ClickHouse fork for raw data, and its Cloud and BYOC services.

RawTree

RawTree is an analytics (OLAP) database forked from ClickHouse®, designed for highly efficient raw / semi-structured data storage and processing, and with automatic optimizations for different workloads.

It builds on ClickHouse®'s SQL engine and database constructs, with changes to how it handles evolving fields, storage, and optimization.

You can insert JSON without defining a schema, then query its fields with SQL.

RawTree Cloud and RawTree BYOC are the services that deploy and operate RawTree. They add provisioning, service authentication, APIs, integrations, and operational tools. See Concepts for how these layers fit together.

The service relies heavily on the database and leverages (and the user can too) SQL to define resources and their behavior. Users, roles, grants, row policies, settings profiles as well as workloads control access and resource use. Supported SQL statements let you configure those objects directly.

What RawTree does

  • Stores raw events and telemetry in tables, without requiring a schema.
  • Manage evolving fields and columns by simply adapting to ingestion changes.
  • Queries, aggregates, and joins data through SQL.
  • Relies on database objects to enforce privileges, row policies, workload controls.
  • Adapts physical layouts through sorting keys, projections, and background work.

RawTree Cloud and RawTree BYOC

RawTree Cloud is the Tinybird hosted service. RawTree BYOC enables you to bring your own cloud: the service deploys the database infrastructure in your cloud account. In these docs, RawTree always means the database. The service means RawTree Cloud or RawTree BYOC, as applicable to your deployment.

The service accepts data through APIs and integrations, can create a table on first insert, and exposes query history, request logs and service observability through OpenTelemetry metrics, logs and traces to track the health of your RawTree clusters. The CLI, SDKs, UI, and MCP tools use service interfaces to work with RawTree.

The Query API accepts reads and selected write and management statements. Its restrictions describe that interface, not the full SQL capabilities of RawTree (Direct access to the database through HTTP and TCP is coming soon). See ClickHouse compatibility and API scope and Deployment for more details.

Start here

References

Resources