<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Notes from the control plane on Ampbase Blog</title><link>https://ampbase.io/blog/</link><description>Recent content in Notes from the control plane on Ampbase Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 25 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ampbase.io/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Why We Built Ampbase</title><link>https://ampbase.io/blog/posts/why-we-built-ampbase/</link><pubDate>Sat, 25 Jul 2026 00:00:00 +0000</pubDate><guid>https://ampbase.io/blog/posts/why-we-built-ampbase/</guid><description>Your log shipper, your coding agents, your security agents: all running config nobody can canary or roll back. What changes when you treat a config rollout as a feature flag problem.</description></item></channel></rss>