The Future of StatusPal: Classic and Next

Over the past years, StatusPal has been the product teams rely on to communicate clearly during incidents and maintenance. It’s the product our customers use today, and it remains central to how we support critical communication.

We want to share how we’re thinking about the future of StatusPal, what this means for the product you’re using today, and how a newer version we’re building fits into the picture.

To keep things clear, we’ll refer to the current version — used by all paying customers today — as StatusPal Classic, and the newer version we’re building as StatusPal Next.

As we’ve built, operated, and supported StatusPal Classic, we’ve learned a lot about scale, reliability, and long-term maintainability. Some early architectural decisions now make it harder to introduce larger improvements cleanly and safely.

That’s why we’re building StatusPal Next. It’s designed around those learnings and gives us a much stronger foundation for the future. This new foundation lets us build and evolve the product in ways that aren’t feasible within Classic. Importantly, StatusPal Next is still under active development and does not yet have full feature parity with StatusPal Classic.

What this means for existing StatusPal customers

Nothing changes today.

StatusPal Classic remains fully supported, stable, and production-ready. There is no forced migration and no action required on your side.

Going forward, our focus will be split intentionally:

• StatusPal Classic will receive ongoing work around reliability, performance, security, and operational stability. We are continuing to invest in StatusPal Classic where it directly improves reliability and operational robustness. This includes ongoing work to strengthen our monitoring capabilities, such as improvements toward a more robust, multi-region setup.
• StatusPal Next is where new features and larger product improvements will be built.

This allows us to move faster on innovation without compromising the reliability of the product you depend on today.

StatusPal Next also enables us to expand beyond what was practical in Classic. This includes:

• Incident management (currently in beta)
• A standalone, fully featured monitoring service (in progress)
• On-call scheduling (planned)

These capabilities represent the direction we want StatusPal to grow into over time and are made possible by the new foundation Next is built on.

Our current plan is to bring StatusPal Next to feature parity with StatusPal Classic by late 2026 or early 2027, and to provide migration tooling ahead of that. When migration becomes available, existing customers will be able to move to StatusPal Next on the same pricing, with a largely equivalent feature set. Some workflows may look different, but these changes are intentional and aimed at making the product simpler, more consistent, and easier to use while achieving the same outcomes.

There is no mandatory migration timeline. While we expect many customers will choose to move to StatusPal Next over time, we’ll continue supporting StatusPal Classic indefinitely for those who prefer to stay on it.

We’ll share meaningful updates via our blog and email as development progresses. You can also follow new work on the StatusPal Next roadmap.

If you have questions, want to discuss how this affects your setup, or would like to learn more about StatusPal Next as it evolves, we’re always happy to talk — just reach out.

Thank you for building with us and for your continued trust.

— The StatusPal Team