<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nemo-Guardrails on Nitin Kumar Singh</title><link>https://nitinksingh.com/tags/nemo-guardrails/</link><description>Recent content in Nemo-Guardrails on Nitin Kumar Singh</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Nitin Kumar Singh. All rights reserved.</copyright><lastBuildDate>Wed, 05 Aug 2026 08:00:00 +0530</lastBuildDate><atom:link href="https://nitinksingh.com/tags/nemo-guardrails/index.xml" rel="self" type="application/rss+xml"/><item><title>The Production Guardrail Stack: Presidio + Azure Content Safety + NeMo Guardrails Around a MAF Agent</title><link>https://nitinksingh.com/posts/production-guardrail-stack-presidio-content-safety-nemo/</link><pubDate>Wed, 05 Aug 2026 08:00:00 +0530</pubDate><guid>https://nitinksingh.com/posts/production-guardrail-stack-presidio-content-safety-nemo/</guid><description>Microsoft ships real code for every guardrail layer, but no sample wires them together around one agent. Here&amp;rsquo;s the reference stack — Presidio for PII, Content Safety for harm categories, NeMo Guardrails for programmable rails, FIDES for deterministic flow control — where each fits in the MAF middleware pipeline, and the licenses.</description></item></channel></rss>