<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Ravioli Docs Blog</title>
        <link>https://AI-Passione.github.io/ravioli/blog</link>
        <description>Ravioli Docs Blog</description>
        <lastBuildDate>Tue, 26 May 2026 00:00:00 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <item>
            <title><![CDATA[We Need to Talk More About Vibe Analytics—And Why We Built Ravioli]]></title>
            <link>https://AI-Passione.github.io/ravioli/blog/introducing-ravioli-and-vibe-analytics</link>
            <guid>https://AI-Passione.github.io/ravioli/blog/introducing-ravioli-and-vibe-analytics</guid>
            <pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[We are wasting six figures a year on dashboard maintenance. In the average data team, 30% to 40% of analyst time is spent fixing broken SQL, adjusting dashboard filters, and maintaining "dashboard graveyards" that nobody looks at after two weeks.]]></description>
            <content:encoded><![CDATA[<p>We are wasting six figures a year on dashboard maintenance. In the average data team, 30% to 40% of analyst time is spent fixing broken SQL, adjusting dashboard filters, and maintaining "dashboard graveyards" that nobody looks at after two weeks.</p>
<p>We need to talk more about <a href="https://jimmypang.substack.com/p/we-need-to-talk-more-about-vibe-analytics" target="_blank" rel="noopener noreferrer" class="">Vibe Analytics</a>—and how Ravioli was built to serve it.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-is-vibe-analytics">What is Vibe Analytics?<a href="https://ai-passione.github.io/ravioli/blog/introducing-ravioli-and-vibe-analytics#what-is-vibe-analytics" class="hash-link" aria-label="Direct link to What is Vibe Analytics?" title="Direct link to What is Vibe Analytics?" translate="no">​</a></h2>
<p>Vibe analytics is conversational data analysis powered by AI. Instead of waiting in ticket queues for pixel-perfect dashboards, you ask questions in plain English, explore data in real time, and only keep the results that are worth turning into permanent artifacts.</p>
<p>As highlighted in our recent article on <a href="https://jimmypang.substack.com/p/we-need-to-talk-more-about-vibe-analytics" target="_blank" rel="noopener noreferrer" class="">Vibe Analytics</a>, the core philosophy is simple: <strong>Analysis first, artifact second. The default output should be disposable.</strong></p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-technical-unlock-why-now">The Technical Unlock: Why Now?<a href="https://ai-passione.github.io/ravioli/blog/introducing-ravioli-and-vibe-analytics#the-technical-unlock-why-now" class="hash-link" aria-label="Direct link to The Technical Unlock: Why Now?" title="Direct link to The Technical Unlock: Why Now?" translate="no">​</a></h2>
<p>Historically, Natural Language Query (NLQ) tools failed because they translated text directly into raw SQL. The AI guessed joins, hallucinated metrics, and returned subtly wrong numbers. Trust cratered.</p>
<p>Vibe Analytics in 2026 works because of a critical technical unlock: <strong>The Semantic Layer</strong>. By constraining the AI to pre-defined metrics (like those in dbt MetricFlow or Cube), the query generation is deterministic. The LLM only translates your question into a metric and a dimension; the query engine handles the SQL.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-ravioli-fits-in">Where Ravioli Fits In<a href="https://ai-passione.github.io/ravioli/blog/introducing-ravioli-and-vibe-analytics#where-ravioli-fits-in" class="hash-link" aria-label="Direct link to Where Ravioli Fits In" title="Direct link to Where Ravioli Fits In" translate="no">​</a></h2>
<p>To make Vibe Analytics successful, you need two things: <strong>speed</strong> and <strong>modular definitions</strong>. That is exactly why we built <strong>Ravioli</strong>:</p>
<ol>
<li class="">⚡ <strong>Local execution speeds at the speed of thought</strong>: Powered by DuckDB, Ravioli queries massive Parquet, CSV, and database files in milliseconds. You can't have a conversational "vibe" if you are waiting 30 seconds for a query to run.</li>
<li class="">🥞 <strong>Modular, version-controlled definitions</strong>: Ravioli allows you to declare clean schemas and constraints. This clean relational mapping acts as the perfect structural foundation for semantic engines to translate questions without hallucinating joins.</li>
<li class="">💸 <strong>BI without the BS</strong>: By moving from heavy BI licenses to lightweight, local-first analytics layers, teams compress decision cycles from weeks down to hours while saving €200K+ in maintenance overhead.</li>
</ol>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="promoting-what-matters">Promoting What Matters<a href="https://ai-passione.github.io/ravioli/blog/introducing-ravioli-and-vibe-analytics#promoting-what-matters" class="hash-link" aria-label="Direct link to Promoting What Matters" title="Direct link to Promoting What Matters" translate="no">​</a></h2>
<p>Not everything should be ephemeral. Executive dashboards, regulatory reporting, and core KPIs deserve a permanent home. Everything else should be run, explored, and discarded.</p>
<p>With Ravioli, you get a lightweight data warehouse setup that runs locally, deploys instantly, and gives your analysts the power to build semantic definitions rather than pushing pixels on dashboards.</p>
<p>To get started with Ravioli, check out the <a class="" href="https://ai-passione.github.io/ravioli/docs/intro">Quick Start Guide</a>.</p>]]></content:encoded>
            <category>ravioli</category>
            <category>vibe-analytics</category>
            <category>duckdb</category>
            <category>semantic-layer</category>
        </item>
    </channel>
</rss>