onshore
Products / Find and check

Every request accounted for, none of the data.

One page shows every connection and how much it caught. Usage shows values protected, shown and refused over any period, with response times per service. Service logs find any single request by the ID in an error message.

The problem

When an integration breaks, teams often turn on verbose logging to find out why, and the logs fill with the very data they were meant to keep in. Onshore's logs never hold a value.

How it works
01

See what's switched on

Every connection as a card, with its status, a 14-day trend and the values it caught.

02

Measure it

Pick a period and see operations by result, per day and per service, with typical and 95th-percentile response times.

03

Trace one request

Search service logs by request ID, service, result or date, and download what you find as CSV.

What's included

Usage over any period

Protected, shown in full, shown masked and refused, with a daily chart. Useful for sizing, budgeting and billing.

Response times per service

Typical and 95% figures for the vault, log protection, the AI gateway and the proxy.

Service logs by request ID

Every request with its service, result and time taken. Filter, page through and export.

Health at a glance

Whether each service is answering, and what the product did in the last hour.

Alerts where you work

Signed webhooks for reveals, policy changes and failures, with retries. Prometheus metrics for Grafana or Datadog.

No values, ever

Logs and metrics carry what happened and who did it, never a sensitive value.

Who uses this

Start with one leak.

Tell us which flow worries you most. We'll show you what it would take to keep it onshore.