Itzal — Writing

Two pieces, both about constraints we chose.

Long-form writing on the engineering consequences of not collecting what we protect. Neither post is published yet — each needs a named author first.

Book a technical demo The architecture

The ones that never light are the ones we publish.

Both drafts are written and neither is published. A post needs a named human author with a real bio — “The Itzal Team” is worth nothing to a security reader and nothing to an answer engine. Authors to be named

01
Building a Detection Product That Can’t Learn From Your Data

Most ML products improve by collecting their mistakes. Itzal structurally cannot. Here is what replaces the feedback loop, and what it costs.
02
Why We Publish the Things Our Product Can’t See

Zero detections and perfect coverage look identical on a dashboard. Publishing our gaps is how a customer can tell the difference.

Two pieces, both about constraints we chose.

Building a Detection Product That Can’t Learn From Your Data

Why We Publish the Things Our Product Can’t See

The arguments are already on the site.