PanelAlpha Engine 2.1.2: Protect more, control more, monitor better

Building an Engine people can safely rely on in production takes more than making sure their applications run well. It also means protecting important projects from unwanted actions, giving users more control over who or what can access their projects, and making it easier to see how server resources are being used. PanelAlpha Engine 2.1.2 is the latest result of that work.

What’s better with 2.1.2

The main changes in this release address three practical needs: keeping important projects safe, deciding exactly which projects a token can access, and getting a clearer view of storage use. They work in different parts of Engine, but each one addresses a process that matters when you’re responsible for running your own projects.

Some projects need extra protection, especially when you use an API or AI agent to manage them. With version 2.1.2, protected projects cannot be deleted, stopped or redeployed through a token. Engine simply refuses these requests and returns a 409 response. This gives you an extra layer of protection against accidental or unwanted changes to important projects.

You now have more say in what each token can access too. API and MCP tokens can be limited to specific projects, so an integration or AI agent can only see the ones you give it access to. These tokens also can’t change project limits or remove a suspension, as those decisions are yours alone. And if you don’t set any project restrictions, your tokens will continue to work just as they did before.

Keeping track of storage is getting easier as well. Engine now measures disk usage automatically every 15 minutes, giving you regularly updated information without having to run a separate check each time. It’s also a useful starting point for monitoring how much space your projects need as they grow.

These are the main highlights, but they are not the whole release. Engine 2.1.2 includes 55 changes in total, with further improvements and fixes across different parts of the system. Some are less visible than others, but they all contribute to making daily use more dependable and keeping Engine moving toward production readiness.

Following Engine’s progress?

Every bit of interest helps the project reach more people. If you like where it’s going, give the repo a hug (I mean, a ★ will do too). And if you have ideas for Engine, want to report an issue, or feel like contributing to the code, we’d love to have you involved.

Explore Engine on GitHub

What we build from here

One of the best things about building Engine in the open is that we can learn from real use and act on it while the project is still moving fast. A request, an edge case or a detail that affect everyday work can become part of the next release.

And there is still a bigger ambition behind all of this: to make running projects on your own VPS simpler than people have come to expect, without putting another platform in charge. We are moving toward that, and bringing the new Engine together with our Control Panel remains an inseparable part of the plan.

If you are trying Engine, tell us what you’re building and what could be easier. We’d love for our next improvements to come from conversations with you too.

View full changelog