Roadmap
What VaultPanel does today and what is planned next, by area: servers, websites, apps, data, backups, security, hosting, the assistant and integrations.
VaultPanel is built in phases. Phases 0 to 9 are done, and most of Phase 10: containers, API tokens, the CLI and SDK, plugins, and scaling an app on one server. This page lists what you can use today and what is planned. Planned items have no release dates.
In the panel, planned options are marked Coming later and cannot be selected, for example PostgreSQL and Redis on the Databases page.
Phases
| Phase | Scope | State |
|---|---|---|
| 0 | Architecture, database layer, CI | Done |
| 1 | Sign-in, two-factor, users, roles and permissions, audit log, dashboard, agent registration, jobs | Done, except custom roles |
| 2 | Server management and monitoring: metrics, services, processes, alerts | Done |
| 3 | Websites, domains, NGINX, PHP-FPM, SSL, file manager | Done, except the items below |
| 4 | Node.js and Python apps, databases, Git deployment, PM2 | Done, except the items below |
| 5 | Backups, cron jobs, automation, logs | Done, except the items below |
| 6 | Security hardening, isolation, firewall, auditing | Done, except the items below |
| 7 | Several servers: server groups, bulk actions, agent updates from the panel | Done, except the items below |
| 8 | Hosting plans, customers, quotas, a billing API | Done, except the items below |
| 9 | AI assistant: answers from the panel's own data, fixes proposed for approval | Done, except the items below |
| 10 | Containers, plugins, CLI, SDK, API tokens, scaling | Containers, API tokens, CLI, SDK, plugins and scaling on one server done; scaling across servers not started |
Available today
| Area | What you can use | Guide |
|---|---|---|
| Servers | Agents on every server, live and historical monitoring, alerts, server self-check, browser terminal with recordings, logs, server groups and bulk actions | Servers |
| Websites | Static, PHP (7.4, 8.0 to 8.5) and reverse-proxy sites, single-page apps, wildcard domains, Let's Encrypt, uploaded and wildcard certificates, custom NGINX rules, .htaccess through Apache, file manager, Git deploy, uptime monitoring, CMS installer | Websites |
| DNS and email | DNS zones on your own servers (BIND), Cloudflare and Namecheap for wildcard certificates, email hosting with mailboxes, forwarders and DKIM, panel email for invites, resets and alerts | DNS and email |
| Apps | Node.js, Python, Go and Ruby apps and PHP sites from Git, rollbacks, signed push-to-deploy webhooks, zero-downtime reloads for Node.js, several copies on one server, CPU and memory limits, Docker containers | Applications |
| Data | MariaDB databases and users, a SQL client in the panel, one-click phpMyAdmin | Databases |
| Backups and automation | Scheduled backups to the server, S3-compatible storage or SFTP, cron jobs, webhooks to JSON, Slack and Discord | Backups and automation |
| Security | Firewall with incoming and outgoing rules, SSH settings, port and keys, Fail2ban, security updates, two-factor sign-in, panel access by address, audit log, an agent that runs without root | Security |
| Hosting | Plans, customers, quotas, suspension, a billing API, a WHMCS module, a financial report | Hosting and billing |
| Assistant | Claude, OpenAI-compatible services, or a free model on the panel's own server | AI assistant |
| Extending | REST API with scoped tokens, JavaScript SDK, CLI, plugins and plugin directories | Developers |
Planned
Users and access
- Custom roles.
- Limiting staff users to some servers or groups. Today every staff user with a permission has it on every server; hosting customers only ever see their own account.
- Email alerts about sign-ins.
- Tokens that belong to the panel rather than to a person, and per-token IP allowlists.
Servers
- Repairing a failed self-check from the panel.
- Bulk actions for more operations (installing software, firewall rules, SSH keys on many servers), scheduled bulk actions, and webhooks when a bulk action finishes.
- Rolling back an agent update from the panel. The previous version is kept on the server as
/usr/local/bin/vaultpanel-agent.previous. - Private networking between servers.
- The terminal for admins and other roles, shells as a user other than root, and uploading files by dragging them onto the terminal.
- Other Linux distributions for the installer, a trusted certificate straight from the installer (a panel domain gives one today), and uninstalling with one command.
Monitoring
- Uptime checks from more than one location, custom paths, expected text or status codes per website, a public status page, and alerting customers about their own websites.
- Shipping logs to an outside service, and log files other than the journal, NGINX and app logs.
- Container metrics history and alerts (live CPU and memory already show on a container's page).
Websites
- Per-site resource limits (CPU, memory, disk quotas) and chroot isolation for PHP sites.
- Per-plan lists of allowed PHP versions, per-site
php.inisettings, and choosing extra PHP extensions. - Letting customers write their own NGINX rules,
php_valuelines in.htaccess, and Apache modules beyond rewrite, headers, expires and the basics. - Moving or copying a website, app or database to another server.
DNS and email
- Secondary name servers on a second panel server (zone transfers), DNSSEC, importing a zone file or from another provider, and customers managing their own zones.
- Other DNS providers (such as DigitalOcean and Route 53), managing a provider's records from the panel beyond the certificate check, and checking a provider's credentials when they are saved.
- Webmail, spam and virus filtering, autoresponders and filters, catch-all addresses, sending limits, customers managing their own email, mail backups, and plan quotas for mailboxes.
Apps and containers
- Running one app on several servers with a load balancer in front, and scaling automatically on load.
- Zero-downtime reloads for Python, Go and Ruby apps, and shared folders that survive deploys for PHP sites deployed from Git (such as uploads or Laravel's
storage/). - A per-plan limit on app copies for hosting customers (their plan's CPU and memory caps already cover all copies).
- Private registries (Docker Hub accounts, GHCR or your own), Docker Compose files and multi-container stacks, and building images from a Git repository.
- Mounting server folders into containers (bind mounts) and choosing other networks.
- Backups of container volumes, and moving containers between servers.
Databases
- PostgreSQL and Redis.
- MySQL 8.4 and 8.0 as the database server for websites and apps.
- Database import and export, and remote (non-local) database access.
- Separate database users for migrations and for runtime.
- Database replication.
Backups
- Restoring a backup into a new website, app or database, or onto another server. Restores go back in place today.
- Encrypting backups before they leave the server. Panel backups can already be encrypted; website, app and database backups cannot yet.
- Backups of the whole server or of mail.
- One backup holding a website's or app's files and its database together.
- Copying the panel's own backups to the storage set up in Backups > Storage (
VAULTPANEL_BACKUP_UPLOADruns any command instead). - Cron jobs as root or with shell features such as pipes and redirects. A wrapper script in the site's folder can do those as the site's user.
Security
- Narrower root helpers per kind of operation (packages, NGINX, users, systemd). The agent already runs as its own user; what the panel signs still runs as root in its helper.
- Firewall rules for routed traffic, editing rules added outside VaultPanel, and firewalld.
- Limiting SSH to some addresses. VaultPanel keeps SSH open to everyone so it can never lock you out.
- Viewing the packages a security update would install before installing it.
- Renewing the panel's self-signed certificate without updating each agent.
- A shared rate-limit store for several API instances.
Hosting and billing
- Taking payments, invoices and tax inside VaultPanel. A billing system charges customers and calls the billing API.
- A Blesta module.
- Welcome emails, and warnings when an account nears or passes a limit.
- Bandwidth limits, and mail and FTP accounts as plan limits.
- Hard disk quotas enforced by the file system. Today the disk limit stops new websites, apps and databases once reached, but a site can still grow past it until it is measured again (about every 15 minutes).
- Customers adding their own SSH keys, changing PHP versions server-wide, or seeing server logs and metrics; resellers.
- Moving a customer to another server with their sites.
AI assistant
- The assistant for hosting customers (staff only today).
- Answers that appear word by word.
- Per-user keys and spending limits beyond 60 questions an hour per person.
- Reading website files, database contents, firewall rules or backups, and proposing changes to files or settings.
Plugins and integrations
- A central VaultPanel marketplace with ratings, reviews and paid plugins.
- Plugins adding panels to existing pages (today they add pages of their own), settings forms the panel draws for a plugin, and more events (website and app changes, sign-ins).
- A Python SDK.
Plugins will not run inside the panel's process: they stay separate programs on purpose. See Plugins.