Datius Documentation

Datius is a business telemetry engine: send it typed, tagged signals from anywhere in your stack — a checkout event, a queue wait time, a sensor reading — and query them back as dashboards, live telemetry, and historical reports, all backed by embedded DuckDB over partitioned Parquet files. No external data warehouse required.

How it fits together

Every workspace is an isolated telemetry namespace within an organization. You define signals (a machine key, a data type, and an optional tag schema), ingest events against them via API key, and build dashboards or run ad-hoc reports over the result — the same signal definitions power the dashboard widgets, the Live Telemetry inspector, and the Reports view.

• Ingestion API — a single, high-throughput endpoint for sending one event or a batch, authenticated by a workspace-scoped API key. See Ingestion API.
• Signals — typed, tagged event definitions; see Signal Schemas & Tags.
• Dashboards & Reports — scorecards, charts, and historical breakdowns built directly on top of your signals, no separate modeling step.
• Alert Rules — get notified by webhook or email the moment a single ingested event crosses a threshold you define. See Alert Rules.

Where to start

• New to Datius? Start with the Quickstart to send your first event in a few minutes.
• New to the data model? Read Core Concepts first.
• Sending events from your own service? See the Ingestion API reference and the Authentication guide.
• Using Node.js or TypeScript? The SDKs & Code Examples page covers the official @datius-io/node package.
• Want to explore every endpoint, with live request/response shapes? Open the API Reference.
• Want to be notified when a signal crosses a threshold? See Alert Rules.