How it’s different

How this model is put together.

A description of the product. No other vendor is named on this page, and nothing here says another suite lacks a feature.

One agent

The same agent covers the host, the container, and the cluster. The install is the script, the chart, or the playbook in the repository.

Journeys from spans

A correlation or a session is enough. Traces that share one become an ordered path. There is no journey file to draw first.

The layer first

Checkout opens as a stack. The hop outside its baseline is marked there, and the trace is where you go next.

External hops, named

A call to a host you do not run is named. When that hop causes the wait, it is flagged. In the demo that hop is Stripe EU.

The network, both ways

Inbound runs through the CDN, the firewall, and the load balancer. Outbound leaves through NAT to the system you call. Both are on the same picture.

Hosted, or on your machine

The public demo is a hosted app. The same app runs with docker compose, or on Fly. The data directory is yours when you run it. Secrets in the built-in vault stay masked. A reveal is limited to the Owner and is audited.