SECURITY & ARCHITECTURE
Read-only by architecture, not by promise.
telemetria connects with read scopes, pulls metadata and metrics — never row-level data — and every action in the apply tier executes through your approval, in your change window.
YOUR ENVIRONMENT
Databricks / Spark on K8ssystem tables · event logs · cluster metrics
Cloud billingCUR / cost exports · read-only bucket
Kubernetesevents API · read-only service account
TELEMETRIA PLANE
Correlation graphstages ↔ pods ↔ dollars ↔ datasets
Metadata storepinned to your region · [NEEDS INPUT: regions at launch]
Actions engineproposes → you approve → applies → verifies
What we never read
Row-level data, table contents, query results. The plane runs on metadata, metrics, and logs — attribution doesn’t need your data.
What leaves your cloud
Job names, stage metrics, cost lines, quality check results. Full inventory in the connector docs, per source.
Compliance
[NEEDS INPUT: SOC 2 status — state “in progress” only if true]. SSO/SAML, audit log of every approved action.