INGESTION
Already collecting events? Skip the SDK rollout.
Most analytics tools force you to instrument from scratch and ship every event to their cloud. Klaritics meets your data where it is - inside your warehouse, inside your infrastructure.
4 modes
for modern data pipelines
<10 min
to map existing warehouse schemas
0 lock-in
to vendor-hosted event storage
1 platform
for PM and data team workflows
Two ingestion paths, one Klaritics core
Use warehouse-native ingestion when event tables already exist. Use direct ingestion (SDK, HTTP API, Streaming) when Klaritics should receive events first. Both routes can run in one deployment.
Ingestion modes by source
Match ingestion mode to where events originate today, then combine paths as your stack evolves.
Data warehouses
One integration surface for tables you already curate in the warehouse — no duplicate event pipeline.
Warehouse-native ingestion
Read existing event tables from Snowflake, BigQuery, Redshift, Postgres, ClickHouse, or Databricks. Klaritics maps schema quickly and queries in-place with read-only access.
"Zero re-instrumentation. Zero event re-shipping."
Direct ingestion
When events should land in Klaritics first — clients, backends, or message buses.
SDK
Instrument client or backend events directly with Klaritics SDKs.
- Web, iOS, Android
- Python, Go, Node
- React Native, Flutter, Java, Ruby, .NET
HTTP API
Single REST endpoint with batch support for server events and webhooks.
Streaming
Connect Kafka, Kinesis, or Pub/Sub for real-time ingestion.
Mode selection guide
Use this quick matrix to choose a default path. You can combine modes in the same deployment as your architecture evolves.
| Need | Recommended mode |
|---|---|
| Greenfield product, no analytics yet | SDK |
| Existing event tables in your warehouse | Warehouse-native |
| Backend-only events / webhooks | API |
| Real-time, sub-second pipelines | Streaming |