<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>dbexpertAI blog</title><description>Field notes from the engine room: database failure modes, detection-path engineering, and honest takes on AI for database operations.</description><link>https://dbexpert.ai</link><item><title>Why your first database is free — for life, not for fourteen days</title><link>https://dbexpert.ai/blog/first-database-free-for-life</link><guid isPermaLink="true">https://dbexpert.ai/blog/first-database-free-for-life</guid><description>dbexpertAI&apos;s launch offer explained: connect one database, get autonomous root-cause diagnostics on it forever, free. The business logic of an offer that only works if the product does.</description><pubDate>Mon, 13 Jul 2026 00:00:00 GMT</pubDate></item><item><title>Monitoring tells you what. Diagnosis tells you why.</title><link>https://dbexpert.ai/blog/monitoring-tells-you-what</link><guid isPermaLink="true">https://dbexpert.ai/blog/monitoring-tells-you-what</guid><description>The observability industry has spent a decade perfecting the rendering of symptoms. The investigation between the alert and the fix is still manual labor — and for databases, it doesn&apos;t have to be.</description><pubDate>Mon, 13 Jul 2026 00:00:00 GMT</pubDate></item><item><title>The OtterTune post-mortem: what ML-driven database tuning taught us by dying</title><link>https://dbexpert.ai/blog/ottertune-post-mortem</link><guid isPermaLink="true">https://dbexpert.ai/blog/ottertune-post-mortem</guid><description>OtterTune had CMU pedigree, real funding, and genuine ML innovation — and shut down in 2024. What its death says about probabilistic vs deterministic approaches to database operations, and why dbexpertAI took the other road.</description><pubDate>Mon, 13 Jul 2026 00:00:00 GMT</pubDate></item></channel></rss>