<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Analytics Engine on Jamie Ede</title>
    <link>https://www.jamieede.com/tags/analytics-engine/</link>
    <description>Recent content in Analytics Engine on Jamie Ede</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 23 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.jamieede.com/tags/analytics-engine/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Rebuilding the document analyzer on Cloudflare&#39;s full stack</title>
      <link>https://www.jamieede.com/posts/rebuilding-the-document-analyzer-on-cloudflares-full-stack/</link>
      <pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.jamieede.com/posts/rebuilding-the-document-analyzer-on-cloudflares-full-stack/</guid>
      <description>&lt;p&gt;Earlier this year I wrote about &lt;a href=&#34;https://www.jamieede.com/posts/ai-ollama-document-analysis/&#34; &gt;building a document analyzer using Ollama and Llama2&lt;/a&gt;&#xA; running on my NAS at home. It worked. But I was already running the rest of the project on Cloudflare Workers, and having the AI piece live on a home server felt increasingly out of place. If the NAS was slow, the tool was slow. If it was off, the tool was off.&lt;/p&gt;&#xA;&lt;p&gt;The obvious move was to go full Cloudflare. This post is about what that looks like now and, specifically, what happens behind the scenes when you press Analyze.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
