MangoPanel powers isolated account stacks, audited jobs, live mail and database tooling, and total operational visibility — explore the real control plane interface below.
Client portal home view displaying disk, inodes, CPU and memory usage along with quick tool cards for File Manager, SFTP, Databases, and Backups.
Explore the architecture, zero-bloat efficiency, per-account isolation, and 5-step effortless migration that set MangoPanel apart.
These are the same kinds of feature states MangoPanel shows inside the client portal. The page is honest about what is live, read-only, or intentionally unavailable.
File manager, per-account credentials, and launch flow are live.
MySQL, PostgreSQL, and browser tools are wired into account stacks.
Mailbox management, MX routing setup, storage metadata, and plan-based mail limits.
Manual backups, restore flow, and downloadable archives.
Managed DNS records, certificate issuance, and HTTPS routing.
Traffic, visitors, errors, bandwidth, and resource views are surfaced from live data.
Not part of the current release, so the panel stays focused.
Every state change is queued, tracked, and visible to clients and admins.
The product spec is centered on real shared hosting operations: account provisioning, website management, mail, files, backups, DNS, and safe admin work.
The hosting brain stays small and observable: WAL-mode SQLite, scheduled backups, integrity checks, and logged operations.
Each customer gets isolated Docker services for the web stack, file manager, databases, mail relay, cron, SFTP, and tools.
Clients can manage websites without SSH, including version switching, HTTPS, document roots, and redirect rules.
Database creation, users, grants, remote allowlists, and browser access are built for ordinary hosting support work.
Routine maintenance is treated as first-class work: scheduled jobs, downloadable backups, deployments, and WordPress installs.
The panel keeps the public surface tight and refuses to perform sensitive actions without the right account and auth context.
Day-to-day file operations stay inside the account boundary, with the same access model the client sees in the dashboard.
Nothing important vanishes into the void; state changes become jobs, and the panel shows what happened after the fact.
The current product is for shared hosting accounts on one server or a small group of servers. VPS/KVM stays a later module.
The API records desired state in SQLite, then a local node agent executes the privileged work and writes back results.
Account provisioning, SSL issuance, mailboxes, backups, and site changes all leave a trace the operator can inspect later.
MangoPanel already acts like a real hosting product: clear limits, safe actions, and UI states that reflect the backend instead of pretending everything is instant.
MangoPanel is shaped around the realities of shared hosting: small control plane, isolated account stacks, auditable jobs, short-lived tool launches, and UI states that tell the truth about what is live, read-only, or intentionally unavailable.