Where your data actually goes

Four hops, one of which never leaves your own network.

Your infrastructure

01

Source database

A read-only role we connect through, scoped to the tables you name.

read-only your VPC
→

02

Sync agent

Pulls changed rows on a schedule, batches them, and signs the payload.

TLS 1.3 5 min
→

03

Processing

Validation, deduplication and metric computation in your chosen region.

eu-central stateless
→

04

Serving layer

Dashboards, the API and scheduled exports read from one materialised store.

cached row-level ACL

Credentials stay put

Database passwords never leave your network — the agent holds them locally.

Encrypted at both ends

TLS 1.3 in flight, AES-256 at rest, with customer-managed keys on Enterprise.

Retention you set

Raw payloads are dropped after 7 days by default; aggregates follow your policy.