<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Pocketbase on 4sh.dev</title>
    <link>https://4sh.dev/tags/pocketbase/</link>
    <description>Recent content in Pocketbase on 4sh.dev</description>
    <image>
      <title>4sh.dev</title>
      <url>https://4sh.dev/images/Ash-Drawing.jpg</url>
      <link>https://4sh.dev/images/Ash-Drawing.jpg</link>
    </image>
    <generator>Hugo -- 0.147.9</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 09 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://4sh.dev/tags/pocketbase/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building Kiln: A Self-Hosted App Builder That Never Leaves Your Infrastructure</title>
      <link>https://4sh.dev/posts/2026/building-kiln/</link>
      <pubDate>Thu, 09 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://4sh.dev/posts/2026/building-kiln/</guid>
      <description>&lt;p&gt;Lovable, v0, Bolt: they all nailed the same loop. You describe an app in chat, an agent writes the code, and a live preview updates while you watch. It feels like magic the first time. Then you try to use it for something real at work and hit the wall: your prompts, your source, and your data all live on someone else&amp;rsquo;s cloud.&lt;/p&gt;
&lt;p&gt;For a lot of internal tools that&amp;rsquo;s a non-starter. The prototype a PM wants to spin up touches customer records. The dashboard someone needs by Friday runs against a production-adjacent database. You can&amp;rsquo;t paste that into a SaaS build tool and hope for the best.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
