Where your data actually goes

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

Your infrastructure

Source database

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

read-only your VPC

→

Sync agent

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

TLS 1.3 5 min

→

Processing

Validation, deduplication and metric computation in your chosen region.

eu-central stateless

→

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.

The prompt

Build an architecture explainer with Tailwind CSS that draws a data flow without images. Above the diagram, a heading and a muted line. The diagram is a horizontal row of four stages on lg screens, stacking vertically on small ones: each stage is a bordered rounded-xl card with a small numbered label, a glyph tile, a title, a one-line description and two tiny monospaced tags; between stages, an arrow glyph centred in a narrow column that rotates to point downward when stacked. Above the row, a dashed-border band labelled "Your infrastructure" enclosing the first stage only, to show the boundary. Under the diagram, three footnote cards explaining what never leaves the customer network, where encryption is applied, and what is retained, each with a glyph and two lines. Keep everything monochrome except one green accent on the encryption note.

Paste it into Claude, Cursor, v0 or any AI coding tool. Prefer the finished markup? .

Where your data actually goes

The prompt

More features / bento prompts