<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: LeonXx</title>
    <description>The latest articles on DEV Community by LeonXx (@gabriel030811).</description>
    <link>https://dev.to/gabriel030811</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3964691%2Ff74a9b2c-71f8-42a4-96e1-1eca81c44124.jpg</url>
      <title>DEV Community: LeonXx</title>
      <link>https://dev.to/gabriel030811</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/gabriel030811"/>
    <language>en</language>
    <item>
      <title>Self-Hosted AI Risk Gate in 10 Minutes: Meet ITTE – Your Pre-Deploy Risk Brain with Self-Evolving Memory</title>
      <dc:creator>LeonXx</dc:creator>
      <pubDate>Tue, 02 Jun 2026 13:18:14 +0000</pubDate>
      <link>https://dev.to/gabriel030811/self-hosted-ai-risk-gate-in-10-minutes-meet-itte-your-pre-deploy-risk-brain-with-self-evolving-22pm</link>
      <guid>https://dev.to/gabriel030811/self-hosted-ai-risk-gate-in-10-minutes-meet-itte-your-pre-deploy-risk-brain-with-self-evolving-22pm</guid>
      <description>&lt;p&gt;Every AI team knows the pain: you ship a new prompt, RAG pipeline, or agent change… and suddenly production breaks in unexpected ways. Compliance teams scream about OWASP LLM Top 10, SOC2, HIPAA, or EU AI Act. Security reviews take forever.&lt;/p&gt;

&lt;p&gt;What if you had a &lt;strong&gt;self-evolving risk brain&lt;/strong&gt; that sits right in your CI/CD, scores every change before merge, and &lt;strong&gt;actually gets smarter&lt;/strong&gt; from your own incidents and senior engineers’ judgments?&lt;/p&gt;

&lt;p&gt;That’s exactly what &lt;strong&gt;ITTE&lt;/strong&gt; (Iterative Threat &amp;amp; Trust Evaluator) MVP is.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why ITTE exists
&lt;/h2&gt;

&lt;p&gt;Traditional guardrails are either:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Cloud-only (your code leaves the VPC → privacy nightmare)&lt;/li&gt;
&lt;li&gt;Static rules (can’t learn from new failure modes)&lt;/li&gt;
&lt;li&gt;No memory (every PR is judged in isolation)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;ITTE solves all three with a &lt;strong&gt;completely local, self-hosted&lt;/strong&gt; design:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Persistent FAISS vector memory + exponential decay&lt;/li&gt;
&lt;li&gt;Optional local LLM judge (Qwen2.5-Coder-1.5B or any Hugging Face model)&lt;/li&gt;
&lt;li&gt;Public cold-start seed + private incident distillation&lt;/li&gt;
&lt;li&gt;Built-in compliance templates (OWASP LLM Top 10, SOC2, HIPAA, EU AI Act)&lt;/li&gt;
&lt;li&gt;Native GitHub PR Gate via GitHub Actions&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;And yes — it’s 100% open source (Apache 2.0).&lt;/p&gt;

&lt;h2&gt;
  
  
  10-minute local setup (no cloud, no Docker yet)
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
bash
# 1. Clone
git clone https://github.com/xxx0438/itte-mvp.git
cd itte-mvp

# 2. Environment
python -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt

# 3. Config
cp env.example .env
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

</description>
      <category>ai</category>
      <category>cicd</category>
      <category>llm</category>
      <category>security</category>
    </item>
  </channel>
</rss>
