Your CFML application may be old, large, and business critical. That doesn't mean modernization has to start with a rewrite.

When organizations talk about modernizing a legacy ColdFusion application, the conversation can quickly become much bigger than it needs to be.

Do we need a new frontend?

Should we rebuild the APIs?

Do we need React or Vue?

Should we replace the application entirely?

How many developers will that require?

Azure joins the serverless family. Scheduled tasks become cluster-safe. And the whole platform gets documentation and skills built for developers and AI agents working side by side.

If you run a technology organization, you are being asked to do three things at once: ship faster, keep the estate you already have running, and make AI part of how your teams work. Most stacks make you choose. BoxLang 1.18 is another step toward not having to.

September 2026 Roundup: What's New in BoxLang, BoxLang AI, and the Ecosystem

September brought exciting developments across the BoxLang ecosystem! Fr...

We've been building AI into the core of ColdBox since 8.0, because the applications teams are asked to build have changed. They talk to models, stream answers, expose tools to other AI systems, and increasingly host agents that act on behalf of users. None of that should require bespoke plumbing in every project.

September 2026 Roundup: What's New Across the Ortus Solutions Ecosystem

September brought new releases, technical insights, and practical resources across the Or...

Ortus Solutions today announces the general availability of cbGenesis 1.0, a production-ready ColdBox HMVC starter template for BoxLang, and the first one designed from day one to be built with an AI coding agent, not just by one.

Part 2 was about sending as little as possible. Today is the opposite: keeping a connection open and pushing data the moment it exists.

A migration can address an infrastructure limitation and still create a delivery chal...

In Part 1 we moved security policy into the router. Today we do the same for caching, and we pick up one of the most underused performance wins on the web along the way.

A validation spec usually checks several fields at once: name is set, email looks right, total is positive, status is one of an allowed list. Written as separate it() assertions, TestBox stops at the first failure and you fix it, rerun, and find out about the second failure. Five fields, potentially five rounds of that.