Where We Stand and What’s Coming?
ColdBox 19th Anniversary, 7.4 Highlights, and 8.x Preview
As we celebrate 19 years of ColdBox, it's a great time to look at where we are today and what exciting updates are ahead. From major enhancements in the 7.x series to the upcoming ColdBox 8 and deeper BoxLang integration, we’re building the future of modern web development.
Please note: ColdBox remains compatible with CFML. The latest updates ensure it also runs smoothly on BoxLang without requiring the CFML module for core features. Existing CFML apps will continue to work with new ColdBox versions, while new projects can take full advantage of BoxLang smoothly.
19 Years of ColdBox
Quick Updates
6.x
LTS has ended7.x
is the current LTS version8.x
series is coming this May
Ecosystem Stats
- 700+ ColdBox modules
- 4,000+ pull requests
- 300,000+ installs in the last 12 months
ColdBox 3-Year Roadmap
This roadmap gives our community clear visibility and confidence in long-term planning, stay tuned to our Social accounts and Email News to get updates on ColdBox and other Modern BoxLang and CFML Tools

ColdBox 7 Series Recap
Versions 7.0
to 7.3
brought powerful improvements
WireBox Delegates
- Hierarchical and module injectors
- Lazy properties and property observers
- Transient performance caching
- Enhanced error handling with
Whoops
- Smarter
coldbox-cli
scaffolding - Scheduled task enhancements
- 100+ total improvements and fixes
ColdBox 7.4
Has Landed
Full BoxLang Compatibility
You can now write your entire application in BoxLang, CFML, or both. ColdBox handles it seamlessly.
What’s new
- New
bx-default
starter template - Automatic language detection
- WireBox builds and composes BoxLang-native objects
- Updated
coldbox-cli
for BoxLang scaffolding
CacheBox Upgrades
More performant and distributed-system ready
- New
DiskStore
with better indexing - Memory indexer removed
- Optimized
JDBCStore
- Rewritten object indexing layer
- New providers:
BoxLangProvider
, BoxLangColdBoxProvider
Scheduler and Task Enhancements
Smarter and more dynamic
scheduler.restart(force = true, timeout = 30)
scheduler.startupTask(task)
You can now programmatically restart the scheduler, register tasks dynamically, and benefit from dozens of internal fixes.
Flow Delegate Functions
Cleaner logic with new chainable methods:
when()
peek()
unless()
throwIf()
throwUnless()
ifNull()
ifPresent()
What’s Coming: ColdBox 8
Powered by BoxLang
ColdBox 8 will be built for a BoxLang-first experience
Highlights
- New compiled engine:
bx-coldbox
- BoxLang Primary Engine
- No CFML compatibility module
- Modules use the same names but live in different structures
- Async constructs and scheduled tasks enhancements
- Better IDE tooling
- Module assets publish to the core
- New CLI support for
coldbox modules publish
Join Us in the Next Chapter
We’re proud of how far ColdBox has come and even more excited about where it's going. Whether you’re a seasoned user or new to the ecosystem, we’re building this for you.
Let’s shape the future of modern development together.
Join the BoxLang Community
Be part of the movement shaping the future of web development. Stay connected and receive the latest updates on surrounding anything BoxLang
Subscribe to our newsletter for exclusive content.
Follow Us on Social media and don’t miss any news and updates:
Add Your Comment
(2)
Jun 17, 2025 20:53:52 UTC
by Will B.
These two things: • BoxLang Primary Engine • No CFML compatibility module ...sound like the end of true CFML support by Coldbox? Should we 100% stop our use of Coldbox for our Coldfusion code past v7? Like v8 is just out?
Jun 17, 2025 21:21:23 UTC
by Brad Wood
Will, no not all. ColdBox still not only supports CFML, it's still 100% written in CFML! The only thing that's changed is we've made the core framework smart enough work in a manner which supports both CF compat AND Boxlang runtime behaviors. Stuff like full null support, metadata variations, etc. This was done so people could write ColdBox apps in BoxLang without having a hard requirement on the CFML compat module-- at least not for the core framework any longer. ColdBox should work like it always has on all the other CFML engines still and in the future.