
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Moscarillo</title>
      <link>https://www.moscarillo.com/notes</link>
      <description></description>
      <language>en-us</language>
      <managingEditor>moscarillo@gmail.com (John Moscarillo)</managingEditor>
      <webMaster>moscarillo@gmail.com (John Moscarillo)</webMaster>
      <lastBuildDate>Thu, 03 Sep 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.moscarillo.com/tags/production/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.moscarillo.com/notes/how-to-get-workflows-off-desktops-and-into-production-using-n8n-openrouter-and-flyio</guid>
    <title>How to Get Workflows Off Desktops and Into Production Using n8n, OpenRouter, and Fly.io</title>
    <link>https://www.moscarillo.com/notes/how-to-get-workflows-off-desktops-and-into-production-using-n8n-openrouter-and-flyio</link>
    <description>The gap between a workflow that works in a chat window and one your business runs on isn&#39;t an AI model problem — it&#39;s infrastructure. Here&#39;s the three-legged stool; n8n for orchestration, OpenRouter for model routing, Fly.io for hosting and data, plus a private React Router v7 frontend.</description>
    <pubDate>Thu, 03 Sep 2026 00:00:00 GMT</pubDate>
    <author>moscarillo@gmail.com (John Moscarillo)</author>
    <category>n8n</category><category>openrouter</category><category>fly.io</category><category>ai-workflows</category><category>production</category>
  </item>

    </channel>
  </rss>
