How we build JSOPanel.
A few things we hold to on every change, not just the big ones.
Security first, not security later
Every change is checked against the same questions before it ships: who can reach this, what does it return to a customer, and what does it cost at real scale. Security review isn't a phase at the end, it's part of what "finished" means.
Built for real scale
A server running JSOPanel is expected to host thousands of websites, not a handful. Every feature is designed and measured against that number, not just checked on a handful of test accounts.
Written in Rust
No interpreter, no garbage collector, and whole classes of memory-safety bugs caught before the code ever runs. That's not a technical detail for its own sake. It's why the panel itself can run alongside the sites it hosts using a small fraction of the memory a traditional panel needs.
Nothing ships untested
Every change is checked against real behaviour, not assumed to work because it compiled. A feature that hasn't been proven working is treated as unfinished, however complete it looks.
One platform, done properly
JSOPanel runs on Debian 13, and only Debian 13. Supporting one platform thoroughly beats spreading the same effort across several and testing none of them as well.
Reversible by design
A backup is taken before a restore overwrites anything. A repair moves files aside instead of deleting them. Destructive actions default to the safer outcome, every time.