// ╔═══════════════════════════════════════════════════════════╗ // ║ KENSAI WEB · Narrative arc ║ // ║ Customer-led story sections (rephrased SB7) ║ // ╚═══════════════════════════════════════════════════════════╝ // ── 1. Tension · "What's getting in the way" ─────────────── const TensionSection = () => (
§ 02 The drag What's between you and the work that matters
You didn't get into security
to triage duplicates.
Yet most teams spend Monday-through-Friday in dashboards built for the 2018 attack surface, arguing with vendors about severity, and chasing alerts that resolve to "intentional design." Meanwhile real exploit chains sit in plain sight — half-discovered, half-reported, never fixed.
The cost shows up everywhere: your engineers stop reading findings. Your board reads breach headlines. Your researchers go quiet. Your auditors ask why three of last quarter's criticals are still open.
{[ { label: 'External · the surface', t: 'Slop tools', d: 'Generic scanners produce more noise than context.' }, { label: 'External · the surface', t: 'Shadow assets', d: 'Parts of the perimeter often outlive the team that created them.' }, { label: 'Internal · the team', t: 'Alert fatigue', d: 'Too much analyst time gets burned on duplicate or low-value work.' }, { label: 'Internal · the team', t: 'Slow-to-fix', d: 'Even obvious issues stall when evidence, ownership, and remediation are split across tools.' }, { label: 'Strategic · the room', t: 'Board pressure', d: "You're asked monthly to prove last quarter wasn't breached. You can't." }, { label: 'Strategic · the room', t: 'Insurer math', d: 'Your premium just doubled. They want evidence, not adjectives.' }, ].map((row, i) => (
{row.label}
{row.t}
{row.d}
))}
); // ── 2. Guide · "How we ride with you" ────────────────────── const GuideSection = () => (
§ 03 Why us We've stood where you stand · we built the tools we wished we'd had
"We were the security team that had to explain why the scanner missed it. So we built the scanner that doesn't."
KENSAI
EARLY SECURITY PRODUCT
Kensai is built by people who carried the pager. Our team has shipped offensive with a sharp bias toward reducing noise, tightening evidence, and making security work easier to act on.
We're not here to sell another dashboard. We're here to take the work off your team that doesn't need a human, and make sure the work that does shows up with the proof, the patch, and the path already drafted.
The receipts
{[ ['347,593', 'CVEs in the database'], ['1.85M', 'Lines of code counted'], ['7', 'Open-source security tools integrated'], ['10', 'Companies already using Kensai'], ['One shell', 'CVE, findings, assets, reports, workflows'], ['Early', 'Public copy kept intentionally grounded'], ].map(([n, l], i) => (
{n}
{l}
))}
); Object.assign(window, { TensionSection, GuideSection });