See what we tokenize.

Paste an alert payload on the left. The tokenizer runs in your browser — no payload leaves this page. Production tokenization is deterministic + per-tenant (the values become real encrypted tokens in your tenant's vault); this sandbox uses placeholder shapes so you can see what the LLM, your logs, and Slack would see.

Paste alert payload

Nothing leaves your browser. The detector runs locally.

After tokenization

{
  "alert": "Database connection failures",
  "host": "<TOKEN_FQDN_INTERNAL_db0p>p>",
  "user": "<TOKEN_EMAIL_alic>",
  "client_ip": "<TOKEN_IPV4_2030>",
  "trace_id": "<TOKEN_HEX_32_f0c1>",
  "request_id": "<TOKEN_UUID_DASHED_550e>",
  "aws_key": "<TOKEN_AWS_ACCESS_KEY_akia>",
  "card_seen_in_log": "<TOKEN_CREDIT_CARD_4111>"
}

8 matches detected: fqdn_internal, fqdn_general, email, ipv4, hex_32, uuid_dashed, aws_access_key, credit_card

Production tokens are opaque HMAC-derived hex (<TOKEN_a1b2c3d4e5f6>); the type-tagged tokens shown here are for visual clarity in this demo.

build b46460aupdated 2026-05-13no trackersno analyticsno third-party scripts