In the Werx | 003: Payload 4 What It Means for ThunderBolt and Stormfront

Payload 4 was released earlier this year. For most people using Payload, it’s a meaningful but not revolutionary update. For us, it matters because ThunderBolt CMS and Stormfront are built directly on top of it.

The biggest improvements in Payload 4 sit in three areas: developer experience, performance, and long-term maintainability. The admin interface is noticeably faster and more stable. TypeScript support has improved, which makes building and maintaining custom blocks and collections less painful over time. There are also better tools for handling plugins and extensions, which is relevant for how we structure Stormfront.

For ThunderBolt CMS, these changes are mostly positive. The core remains the same one place to manage content that can be used across websites, apps, or other systems. What Payload 4 gives us is a stronger foundation underneath. This means fewer workarounds, better performance out of the box, and a codebase that should be easier to maintain as we continue developing ThunderBolt over the next few years.

Stormfront benefits more directly. Because it’s built as a modular layer on top of Payload, some of the improvements in how Payload handles plugins and custom collections make it easier for us to keep Stormfront clean and focused. We’re not rebuilding Stormfront from scratch for Payload 4, but we are gradually aligning it with the new patterns. The goal remains the same: an e-commerce system you can turn on when you need it, without forcing unnecessary complexity into every site.

It’s worth being clear about what this doesn’t change. Payload 4 doesn’t suddenly make ThunderBolt or Stormfront dramatically easier for non-technical users. It doesn’t remove the need for proper setup and configuration. And it doesn’t change our core philosophy we still believe in building tools that clients can own and control, rather than renting access to a platform indefinitely.

What Payload 4 does give us is a more solid base to keep improving both ThunderBolt and Stormfront over time. We’ll be migrating ThunderBolt to Payload 4 gradually, and Stormfront will follow. Existing sites won’t be forced to upgrade immediately, but new projects will be built on the newer version.

For most clients, this won’t feel like a big change in the short term. The real value will show up over time in stability, performance, and how quickly we can build and maintain the features people actually need.

We’ll continue updating ThunderBolt and Stormfront as Payload evolves, but always with the same focus: building systems that are useful, ownable, and don’t create unnecessary long-term dependency.