NovaPanel

Roadmap

We ship continuously — small things land in the changelog the moment they're live. This page is a higher-level view: what's coming next, what we're considering, and what we've decided not to build.

Recently shipped

Not everything we ship is listed here — see the full changelog for every release.

In progress

Actively being worked on. Will land in the next 1-3 minor releases.

Migration tooling (cPanel & Plesk import)

Headline feature for the next minor release. Bulk import of accounts, sites, databases, mail. Likely starts as a CLI before it lands in the panel UI.

Onboarding wizard for first-time installs

Replaces the install-then-figure-it-out flow with a guided tour: hostname, admin user, first site, first customer. Cuts the 'I installed it, now what?' drop-off.

Operator-facing API + CLI reference docs

The panel already has a REST API powering both UIs; we just haven't documented it externally yet. Same for the novapanel CLI shipped alongside the binary.

Considering

Ideas with merit. No commitment to ship — these need either user demand or product clarity before they leave this list.

Docker / container hosting

First-class Docker support — deploy an image, expose a port, get a domain. Plesk has it; we don't yet. Tradeoff is scope creep — we'd build it carefully, not as a swiss-army-knife.

Multi-server fleet view

Operators running NovaPanel on 5+ boxes manage them individually today. A meta-panel that shows fleet-wide health + lets you push config across servers would be a Developer-tier feature.

Extension / plugin API

Letting third parties add functionality (e.g., Imunify-style malware scanners, custom site builders). Risky — extensions are a security surface. Would only ship behind a strict signing policy.

Windows host support

Honest answer: probably never. The work is huge and the audience for 'Windows hosting via a control panel' has been declining for a decade. Plesk handles this case well.

Want something that's not here?

Drop into our Discord and tell us. The roadmap shifts based on what real users actually need — features asked for once usually stay in "considering" forever; features asked for repeatedly get pulled in.