<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Lucee on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/lucee/</link>
    <description>Recent content in Lucee on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 01 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/lucee/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Lucee vs BoxLang vs Adobe ColdFusion in 2026: Self-Host CFML Without the Licensing Bill</title>
      <link>https://www.pistack.xyz/posts/2026-10-01-lucee-vs-boxlang-vs-adobe-coldfusion-self-hosted-cfml/</link>
      <pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-10-01-lucee-vs-boxlang-vs-adobe-coldfusion-self-hosted-cfml/</guid>
      <description>&lt;p&gt;ColdFusion shops have the same conversation every renewal cycle: the application works, the team knows it, and the licensing invoice does not care. Adobe ColdFusion is priced per instance with tiers that punish exactly the deployment models people actually want — containers, autoscaling, per-tenant isolation. Meanwhile the CFML ecosystem quietly built two credible open alternatives on the JVM: &lt;strong&gt;Lucee&lt;/strong&gt;, a straight CFML engine, and &lt;strong&gt;BoxLang&lt;/strong&gt;, a new dynamic JVM language that keeps CFML compatibility as a design goal.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
