yelt
  • How it works
  • Policies
  • Audit
  • Pricing
  • Docs
Sign inGet started
§ Blog

Notes from building
the policy engine.

Architecture, principles, and the integration choices that shape how Yelt enforces policy on AI agents that touch money.

  1. May 4, 2026·3 min read·#launch
    Hello, Yelt.
    Why we built a policy engine and audit ledger for AI agents that touch money — and what we mean by 'tamper-evident' when it's a CFO asking.
  2. May 3, 2026·5 min read·#architecture#policy
    Belt and suspenders: policy as instruction and as enforcement.
    How Yelt compiles a CFO's English sentence into a typed runtime descriptor, drops it into the agent's SKILL.md, and enforces it at the gateway anyway.
  3. May 2, 2026·6 min read·#audit#cryptography
    What 'tamper-evident' actually means at audit time.
    SHA-256, append-only Postgres triggers, and an offline verify CLI. A regulator-grade audit pitch is a cryptographic claim; here's the substrate.
yelt

Policy and audit for AI agents that move money. Spend caps, vendor allowlists, and tamper-evident audit trails — enforced at the MCP gateway.

Product
  • How it works
  • Policies
  • Audit
  • Pricing
  • For developers
Resources
  • Blog
  • Contact sales
  • Support
Legal
  • Terms
  • Privacy
  • Security
Yelt · 2026Tamper-evident · policy-first · agent-host agnostic