How it works

From first request to signed audit trail

policy.check passed · 41ms · signed
run 4f21c9 2.4s total
  1. 1

    Point us at your endpoint

    One URL and a signing secret. No agent to install, nothing to run inside your VPC.

    POST /v1/sources

  2. 2

    Write the policy once

    Rules are plain expressions with autocomplete, versioned in the same repo as your code.

    allow if actor.role in ["admin"]

  3. 3

    Dry-run against real traffic

    Shadow mode replays yesterday so you see exactly what would have been blocked before anything is.

    mode: shadow · 1.2M decisions

  4. 4

    Ship it, keep the receipts

    Every decision is signed and exportable, which is the part your auditor actually asks for.

    GET /v1/audit?from=2026-01-01

    Read the integration guide
">

The prompt

Create a two-column "how it works" section with Tailwind CSS where the visual sticks while the copy scrolls. The left column is a sticky panel from lg up — top-24, self-start — holding a rounded-2xl neutral-900 card with a mock interface inside: a title bar of three dots, a stack of skeleton rows, and one highlighted row that reads like a log entry. The right column is a list of four numbered steps, each generously spaced with a numeral in a bordered circle, a medium-weight heading, a paragraph of relaxed grey prose and a small monospaced detail line. Give each step a left border that turns neutral-900 for the first one. Under the last step, a text link with an arrow. Collapse to one column below lg with the visual first and no stickiness.

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