Blog

ColdBox: The Framework Powering Modern CFML Applications

Victor Campos February 05, 2026

Spread the word

Victor Campos

February 05, 2026

Spread the word


Share your thoughts

ColdBox: Building, Evolving, and Sustaining Modern CFML Applications for 20 years

A Modern Foundation for CFML Development

ColdBox is a powerful, conventions-based MVC framework designed to help developers build modern, scalable, and maintainable CFML applications. Maintained by Ortus Solutions, ColdBox is the foundation of the wider “BOX” ecosystem and has been shaping professional ColdFusion development for nearly two decades.

Whether you are building APIs, enterprise applications, or modular web platforms, ColdBox provides structure without sacrificing flexibility—making it a trusted choice for teams and individual developers alike.

👉 Official documentation: https://coldbox.ortusbooks.com/


Why ColdBox Matters

ColdBox is more than just a framework it’s a complete application platform. It promotes best practices through clear conventions, modular architecture, and deep integrations with complementary tools like WireBox (dependency injection), CacheBox (caching), LogBox (logging), and TestBox (testing).

At its core, ColdBox helps teams move faster while writing cleaner, more sustainable code that can grow with their applications over time.


Contributing to the ColdBox Ecosystem

ColdBox is open source and community-driven. Contributions are welcome across the entire platform, including ColdBox, CacheBox, LogBox, and WireBox.

Contributors are encouraged to follow a few core principles:

  • Be respectful and collaborative—maintainers and contributors donate their time and expertise.
  • Follow the Code of Conduct, which emphasizes professionalism, inclusivity, and good intentions.
  • Submit well-documented bug reports with clear reproduction steps.
  • Use the appropriate channels for support questions, such as the Ortus Community forums or Box Team Slack, instead of opening issues.

Development work is done in dedicated branches (never directly against master), with pull requests targeting development or LTS branches. All changes should include tests and follow Ortus coding standards, with automated formatting supported through CommandBox scripts.

Security issues are handled privately and should be reported directly to the Ortus security team.


Release Strategy and Long-Term Support

ColdBox follows Semantic Versioning using the format:

<major>.<minor>.<patch>
  • Major versions introduce breaking changes
  • Minor versions add features without breaking compatibility
  • Patch versions focus on bug fixes and small improvements

Each ColdBox release receives:

  • 12 months of updates
  • 2 years of security fixes after the next major release

Recent release history includes:

  • ColdBox 8.x (2025)
  • ColdBox 7.x (2023)
  • ColdBox 6.x (2022)

This clear LTS policy allows teams to plan upgrades confidently while maintaining production stability.


Upgrading to ColdBox 8

ColdBox 8 continues the platform’s evolution with a focus on modernization and cleanup. While upgrades from ColdBox 7 are largely smooth, several deprecated features have been fully removed.

Key changes include:

  • Dropping support for Adobe ColdFusion 2018–2021
  • Removal of long-deprecated APIs and utilities
  • Migration to newer router, interceptor, and environment patterns
  • Replacement of legacy components like BeanPopulator with modern alternatives

The ColdBox 8 upgrade guide provides detailed instructions, including AI-friendly inspection patterns and automated replacement rules to help teams migrate efficiently while minimizing risk.


The People Behind ColdBox

ColdBox is created and led by Luis Majano, founder and CEO of Ortus Solutions and the original author of the ColdBox Platform and the entire “BOX” ecosystem. With decades of experience in software engineering and open-source leadership, Luis has been a central figure in the CFML community since the early 2000s.

He is supported by a dedicated team of contributors, including Jorge Reyes, who plays a key role in documentation and project coordination, and Brad Wood, a core engineer deeply involved in CFML tooling and platform evolution. Together, they ensure ColdBox remains stable, innovative, and community-focused.


ColdBox is not just a framework you adopt once and forget. It’s a platform that grows with you, shaped by real-world usage, an active community, and years of deliberate evolution. Whether you’re maintaining a long-standing CFML application or exploring modern architectures for the first time, ColdBox invites you to go deeper at your own pace and discover how much control, clarity, and confidence a well-designed framework can bring to your work.

Join the Ortus Community

Be part of the movement shaping the future of web development. Stay connected and receive the latest updates on, product launches, tool updates, promo services and much more.

Subscribe to our newsletter for exclusive content.

Follow Us on Social media and don’t miss any news and updates:

Add Your Comment

Recent Entries

Your Development Team Is at Capacity. Here’s How to Keep Critical Work Moving!

Your Development Team Is at Capacity. Here’s How to Keep Critical Work Moving!

The problem is not that your team lacks priorities.It is that maintenance, delivery, and long-term improvement are competing for the same people.

For companies running business-critical CFML, ColdFusion, or BoxLang applications, that pressure can be especially difficult to solve. Experienced developers are not always easy to hire quickly, application knowledge may be concentrated in one or two people, and a generalist may need significant context before taking ownership of the work. A permanent hire can also require a significant investment in recruiting, compensation, onboarding, and long-term capacity even when the immediate need is a specific project, urgent maintenance, or a period of transition.

Maria Jose Herrera
Maria Jose Herrera
September 18, 2026
Copy of BoxLang AI 3.4 Blog Series Part 5 : Reasoning Without the Guesswork

Copy of BoxLang AI 3.4 Blog Series Part 5 : Reasoning Without the Guesswork

Reasoning-capable models have been usable in BoxLang AI for a while. params passes straight through to the provider body, so params: { thinking: { type: "enabled", budget_tokens: 10000 } } for Claude, or params: { reasoning_effort: "high" } for OpenAI, already reached the API. What never worked was reading the reasoning back. It was parsed out on arrival and silently dropped. In 3.4.0, that's fixed, and it's fixed the same way for every provider.

Luis Majano
Luis Majano
September 15, 2026