Control panel features for everything your server hosts

• Static websites served straight from disk.
• PHP with a pool and account of its own for every website.
• Several PHP versions installed side by side and chosen per website.
• PHP settings and extensions per website, grouped by job.
• Node.js applications started, restarted and put behind Nginx with WebSockets.
• A reverse proxy to one approved upstream, or a restricted container.
• Additional domains, subdomains and a temporary address before DNS moves.
• A dedicated IP address for a website that needs one.
• CPU, memory and process limits, and storage quotas, per website.
• Scheduled tasks with their output kept.
• Website copies with their own database, for staging.
• Suspend a website and bring it back when you are ready.

• Let's Encrypt certificates requested and renewed automatically.
• A domain added later joins the certificate within the hour of its DNS pointing here.
• Your own certificate: a wildcard, one from your own authority, or one issued elsewhere.
• Checked before it is installed, so a mismatched key or a reversed chain is caught, not deployed.
• The names a certificate does not cover are shown, so no visitor meets a warning.
• Keys stored where only root can read them, and never shown again.

• Mailboxes at each customer's own domain, each with a size limit.
• Forwarding, and a copy kept of what a forwarding address sends.
• IMAP and SMTP over TLS on the standard ports.
• Roundcube webmail in the browser, with nothing to set up.
• DKIM signing for each domain, with the record published for you.
• Spam refused during delivery, and doubtful mail filed into Junk.
• mail. and smtp. of each domain, with certificates of their own.
• Automatic setup answered for Thunderbird and Outlook.
• MX, SPF and DMARC records shown, and published where Dashmox hosts the zone.
• Each mailbox sends only as itself, and sending is rate limited.

• A, AAAA, CNAME, MX, TXT, SRV, CAA and NS records.
• Your own nameservers with their own addresses, set from the panel.
• A zone created with each website, with its address and www record.
• Mail records added for you when a domain starts receiving mail.
• IP addresses added to and removed from the server in the panel.
• A zone can only be claimed by the website that owns the domain.

• Databases and accounts isolated per website.
• SQL import of dumps up to 64 MB from the browser.
• Up to ten backups per database, downloadable and restorable.
• Storage limits per database.
• phpMyAdmin for when you want to look inside.

• A file manager to upload, edit, rename and delete.
• SFTP per website, locked to that website's own files.
• Extra file transfer accounts for people who need only files.
• Nothing runs from a folder an application writes to, so an upload cannot become a script.

• File snapshots of a website, taken whenever you want one.
• Recovery points that capture every database, then the files, in that order.
• Daily or weekly schedules that keep up to seven.
• Off-site copies to S3-compatible storage or an SFTP server.
• Download or restore any of them from the panel.
• The panel itself backed up and restored from the command line.

• Installed into a website, or into a folder of one beside what is already there.
• The release the publisher has now, checked against the checksum they publish for it, or their signature where they sign instead.
• The administrator account created, with the password shown to you once.
• WordPress keeps itself updated, and the panel shows what it is waiting on.
• The rest are named, not guessed: the panel reads the version each runs and says which release it is behind.
• A copied website gets its own database and secrets, so staging never touches live.

• Customers with their contact details and a login of their own.
• Hosting packages that set what a customer may create.
• Allowances for websites, databases, mailboxes, backups and scheduled tasks.
• Roles: administrator, customer, developer and read-only.
• Access to one website granted without the rest of a customer's account.
• Sign in as a customer to see what they see, recorded as you.
• API access for scripts and billing systems, with Pro and Business.
• An activity record of who did what.

• Pull over SSH from any Linux server you can sign in to.
• Archives and account backups read and explained before anything is created.
• Whole servers from the most widely used hosting panel, one customer per account, queued one after another.
• WordPress and Joomla pointed at their new database.

Everything about migrating

• Two-factor sign-in with recovery codes.
• Password and sign-in rules for everybody on the server.
• Protection on every website against scanners, uploaded scripts and password guessing.
• A firewall that cannot lock you out of your own panel.
• A security overview that scores what is switched on.
• Signed updates that snapshot the panel before they start.

How Dashmox is secured

• A health page with a Fix it button wherever there is a fix.
• Alerts by email for the problems worth waking somebody for.
• Seven days of CPU, memory, load and disk, and each website's own usage.
• Services started, stopped and restarted from the panel.
• Server logs readable in the browser.
• Updates offered in the panel and installed with one button.
• Search the whole panel: a domain, a customer or a setting by name.
• A command line that checks, repairs and backs up the panel.
• Light on the machine: the panel and its agent use about 18 MB of memory between them. The readings.

• Light and dark, one button in the header, with every surface and state coloured for each.
• Four palettes: forest green, ocean blue, indigo and slate.
• Contrast measured in the browser, in both themes and every palette, against WCAG AA.
• Kept per person, so your choice changes nothing for your colleagues or your customers.
• Your phone follows it, painting its own bar to match the panel.
• On every plan, the free one included. See the themes.