Last reviewed August 2026. Version facts checked against lucee.org and adobe.com; the CFML landscape moves, so check release notes before you commit.
The short version
Most CFML applications are better off on Lucee: it is free, open source, actively developed, and runs the language faithfully. Adobe ColdFusion remains the right choice when your application depends on Adobe-only features, when a vendor or contract mandates it, or when your organisation needs Adobe's commercial support behind the engine. The rest of this page is the detail behind that sentence.
Licensing and cost: the structural difference
This is where the two engines genuinely diverge. Lucee is open source under the LGPL: you can run it on one server or fifty, in containers, on staging copies and developer laptops, without counting licences or asking anyone. Its development is funded by the Lucee Association's member organisations, and paid support is available from consultancies in the ecosystem if you want a contract behind it.
Adobe ColdFusion moved to a subscription-only model with the 2025 release: perpetual licences are no longer sold, and Adobe publishes no list prices; every purchase route ends at a sales conversation. It is sold in Standard and Enterprise editions (plus a free Developer edition for non-production use), and several Standard-edition features, including HTML-to-PDF, run in restricted, throttled form. Containerised deployments need a licence per instance. None of this makes Adobe CF wrong, but it makes its cost a procurement exercise, and that cost recurs for as long as the application lives.
| Aspect | Lucee | Adobe ColdFusion |
|---|---|---|
| Licence | Free, open source (LGPL) | Commercial subscription only (since the 2025 release) |
| Pricing | £0 per server, forever | Not published; quoted through Adobe sales and resellers |
| Current version | Lucee 7.0 (stable since Nov 2025); Lucee 6.2 is the LTS line | ColdFusion 2025 (GA Feb 2025) |
| Older versions | Lucee 5.4 reached end of life 31 Dec 2025 | CF2021 left core support Nov 2025 (no further security patches); CF2023 supported to May 2028; CF2025 to Feb 2030 |
| Java | Java 21 recommended | Pinned per release: CF2025 runs JDK 21 only, CF2023 JDK 17 only |
| Support | Community, plus paid support from ecosystem consultancies | Adobe commercial support included in subscription |
Version and support facts as published by lucee.org and adobe.com at the time of review.
Compatibility: what ports cleanly, and what doesn't
The CFML language itself is highly compatible: tags, functions, components, application lifecycles and the major frameworks (ColdBox, CFWheels, FW/1) all run well on both engines, and recent Lucee releases have deliberately aligned several behaviours with Adobe's. Where migrations need real work is the Adobe-only feature set. Lucee publishes an official list of unsupported Adobe tags and functions; these are the ones that matter in practice:
| Adobe feature | On Lucee |
|---|---|
cfhtmltopdf (WebKit PDF engine) |
Not supported. Lucee generates PDFs via cfdocument with the Flying Saucer engine; simpler CSS, so PDF templates usually need re-testing and some rework. |
cfspreadsheet and spreadsheet* functions |
Not supported. The community-standard replacement is the actively maintained spreadsheet-cfml library; it has its own API, so spreadsheet code is rewritten rather than ported. |
Solr search (cfindex/cfsearch) |
Same tags, different engine: Lucee's Lucene extension. Collections are re-indexed, not copied over. |
| ORM (Hibernate) | Supported via the Ortus ORM extension (the maintained fork of Lucee's Hibernate extension). Adobe's ORM search functions don't exist. |
cfexchange, cfsharepoint, .NET integration, cfreport, cfwebsocket, cfclient |
Not supported. If your application genuinely depends on these, that is a strong signal to stay on Adobe CF. |
Legacy UI tags (cfgrid, cftree, cfmenu…) |
Not supported, and long deprecated on Adobe's side too; migrating away from them is overdue on either engine. |
The subtle behavioural differences
Beyond missing features, a handful of behaviours differ and are worth testing deliberately: Lucee passes arrays by reference where Adobe copies them; booleans serialise as true/false rather than Yes/No, and Lucee preserves literal types in JSON where Adobe stringifies them; query-of-query string comparisons are case-insensitive on Lucee and case-sensitive on Adobe; Lucee will not implicitly parse locale-formatted date strings; and both engines must be set to the same null-support mode or database NULLs will behave differently. None of these are hard to fix. All of them are annoying to discover in production, which is why the migration below is test-first.
Performance and footprint
Lucee is a lighter engine: smaller distribution, faster startup, and modest memory needs, which is why it suits containers and many-sites-per-server hosting so well. Recent releases have pushed hard on speed, with Lucee 6.2 up to 50% faster than 5.4 for some operations by the project's own measurements. Adobe CF is by no means slow, but you pay its licence per instance, which discourages exactly the horizontal scaling that CFML apps often want.
When Adobe ColdFusion is the right answer
Honest list: when a vendor application is only certified on Adobe CF; when a contract or compliance regime names it; when you depend on cfhtmltopdf fidelity, Exchange/SharePoint integration or the API Manager; or when your organisation requires a commercial vendor standing behind the engine. In those cases run Adobe CF, keep it patched, and we will happily host it for you.
How to actually decide
You don't have to decide from a comparison table, ours included. Lucee costs nothing to try: stand up your application on a test copy with CommandBox (which runs both engines side by side), pre-scan the codebase for compile-time incompatibilities, and let your own regression tests give you the answer. Most teams find the port smaller than they feared; the ones who find otherwise usually hit one of the Adobe-only features above, and then they know exactly what staying on Adobe buys them.
If you would rather not do that alone: we run CFML for a living, deeply enough that when an upstream Lucee security fix stalled, we patched and now maintain our own build. Migrations are free on every plan, and we will tell you plainly if your application is one that should stay on Adobe CF. See also our Lucee 5 to 6 migration guide if you are already on Lucee and behind on versions.
Host it with people who speak CFML.
UK-based Lucee and ColdFusion hosting with engine-level support, free migration, and CFManager, our own CFML control panel plugin.
