Version 0.32.3

Fixed

• Certificates now include www.<domain> (it was left out, so https://www.<domain> showed a certificate warning). Existing certificates get it automatically within a day.
• A new alias (parked domain) is added to the website's certificate at once, not at its next renewal.

Version 0.32.2

Fixed

• Websites behind Cloudflare's proxy (orange cloud) get their certificate: the panel checks that the name reaches this server through Cloudflare, as Let's Encrypt does, instead of requiring the server's own address in DNS. Site Check shows such names as "Cloudflare proxy".

Version 0.32.1

Fixed

• The mail server no longer logs a warning about the order of its certificate settings at every start (each domain's certificate settings now load after the server's own).
• Site Check runs only when asked, not every time the page opens.

Version 0.32.0

Added

• PHP 7.4 and 8.0 for old websites, built by Sahaab for Ubuntu 24.04 (with the usual extensions) and installed from Sahaab's own signed package repository like the other versions (Server → PHP Versions). They no longer get security fixes from PHP itself; use them only where a site needs them.
• Five more languages: Italian, Dutch, Hindi, Urdu (right to left) and Simplified Chinese — 15 in all.
• Mail programs see each domain's own certificate: IMAP, POP3 and SMTP answer mail.<domain> (and <domain>) with the website's certificate, which now also covers mail.<domain>.
• Incoming mail is checked for viruses (ClamAV); a message carrying one is refused.
• Packages can limit the number of files and folders (inodes) of an account; customers see their count in Resource Usage and a warning near the limit.
• AI assistant (off until turned on; Anthropic or OpenAI, with your own API key or Sahaab credit): explains failed tasks and customers' PHP errors, and finds out why a website is down. Only the facts of each question are sent, with secrets hidden; monthly limit per account.
• Site Check for customers: where a website's name points, what it answers on the server and for visitors, its certificate, the account's limits and its latest errors, with problems marked.
• PHP profiles: ready-made PHP settings (WordPress, large shop, Laravel, large uploads, development) in one click.
• MariaDB upgrade to a newer long-term version (11.4 or 11.8) from Server → Database Server, with a full safety copy first.
• Custom web server configuration per website (administrator): extra OpenLiteSpeed settings for one site, applied with a check that puts the previous configuration back if the site breaks.
• Operating system updates in Server → Updates: the waiting packages (security fixes marked), installing them (all or security only) with the progress shown, and restarting the server when an update needs it.
• Backups can also be copied to Google Drive, Microsoft OneDrive or Dropbox (signed in once from the browser; on Google Drive the server sees only its own files).
• Support tickets: customers ask their reseller (or the administrator) for help from the control panel, resellers ask the administrator; both sides are told by email. Can be turned off, or left out of a feature list.
• Webhooks: the server tells a billing, monitoring or chat system about account, domain, mailbox, disk, bandwidth and failed-task events, as signed JSON messages with retries. Resellers get their own for their accounts.
• Move an addon domain (with its subdomains) to another account: website files, DNS zone, mailboxes, forwarders, mailing lists, installed applications and the chosen databases go along (Accounts → Manage).
• Check & repair for MySQL databases in the customer panel: every table is checked, damaged ones are repaired where possible, and the result is shown.
• API tokens can be limited: to some IP addresses or ranges, to an end date, and to reading only.
• Automatic mail setup: Outlook and Thunderbird need only the address and password; for iPhone, iPad and Mac a profile per mailbox sets up email, calendar and contacts in one step.

Fixed

• Mailboxes created since 0.30.0 could not receive mail (their folder, and for a new domain the domain's mail folder, stayed root's when the spam settings were written into it).

Version 0.31.0

Added

• Fix releases install themselves at night (e.g. 0.31.0 → 0.31.1), so a fixed problem reaches every server within a day. New versions with new features stay the administrator's choice. Can be turned off in Server Settings.
• Error reports: when the panel itself fails (a page, a task, the agent, an install or update), a short report reaches the panel's maker so it is fixed quickly. Before anything leaves the server, domains, email and IP addresses, account names, paths in customers' homes and secrets are replaced; expected situations (a domain not pointing here, a wrong password typed by a customer) are not reported. Can be turned off in Server Settings.

Version 0.30.0

Added

• PHP settings in a website's .htaccess (php_value / php_flag, e.g. memory or upload size) now apply: they become the site's PHP settings, also inside <IfModule mod_php…>. Only safe settings are taken (never e.g. auto_prepend_file); settings chosen in the panel win. Websites moved from other servers keep the PHP settings they relied on.
• Spam settings per mailbox: its own score threshold, senders always allowed, senders always treated as spam (to the Junk folder, never deleted).
• PostgreSQL tool in the customer panel: tables, their rows, running SQL and exporting a database, signed in with the account's own limited login (never the database superuser).
• API for customers: their own tokens (API tokens in the panel) to manage mailboxes, forwarders, databases, DNS records and cron jobs from scripts (/api/v1/me). Only the tools of the account's plan.
• Files for new accounts: everything in /etc/whm/skel is copied into every new account.
• Administrator packages can be shared with resellers: they create accounts on them but cannot change them.
• Malware Scanner in the reseller menu (with the privilege).
• Documentation on the website (/docs): installation, administrator, reseller and customer guides, moving accounts, API.

Faster

• Many accounts at once: tasks that bring the whole server in line (mail, FTP, DNS…) are no longer queued again while one is waiting; the web server restarts once at the end of a batch instead of once per account; only the changed DNS zone is reloaded. Measured with 300 new accounts: creating one took 6.4 s, now 1.5 s; the mail sync took up to 100 s, now 5 s.
• Idle websites give their memory back: a site's PHP processes now stop after 5 minutes without visitors (they stayed forever). With 300 sites the memory in use dropped from 6.1 GB to 2.8 GB.

Version 0.29.0

Added

• Email routing per domain: automatic (from the domain's MX record), local or remote. A domain whose email is with another service (e.g. a hosted business email) is no longer treated as this server's own, so mail from the websites and mailboxes here reaches the real mailboxes there. Checked every hour, also for MX records changed at other DNS providers.
• Change an account's main domain (its subdomains, DNS zone, email addresses, forwarders, FTP and Web Disk logins follow; certificates are issued again) or its username (system user, home folder, cron jobs, applications; the old home path keeps working through a link). Also through the billing-system API (modifyacct).
• Reseller privileges: choose per reseller what they may do (create, terminate, suspend and modify accounts, change passwords, log in as customers, packages, feature lists, DNS, backups, malware scanner, emailing customers, branding, API tokens, WordPress). Applied in the admin panel and the APIs; resellers made earlier keep every privilege.
• Certificate requests (CSR): create a private key and request to buy a certificate from a certificate authority. The key stays in the panel (encrypted) and is used automatically when the certificate is installed.
• Size of each mailbox next to its quota, and importing a mailbox from another mail server (secure IMAP, in the background; running it again only adds what is new).
• IPv6: websites answer on the server's IPv6 address, new DNS zones publish it (AAAA records and SPF), and one click adds it to existing zones. Outgoing email stays on IPv4, which mail providers accept without IPv6 reverse DNS.
• Extra disks: when the server's disk fills up, add another disk (e.g. /home2) and new accounts are placed on the disk with the most free space, with their disk quota on that disk. For the accounts nothing changes.

Version 0.28.1

Fixed

• Transferred websites could answer "403 Forbidden" when the archive brought folders that the web server cannot pass (e.g. a Laravel site's public/ folder). After a transfer such folders inside the websites are opened for passing (files are not changed).

Version 0.28.0

Added

• Hourly sending limit per account (per package, default 500): every email counts, from websites, scripts, cron jobs and mailboxes alike; above the limit mail is held back and retried later. The administrator sees each account's sending, the customer their own.
• Service watchdog: every minute, every service is checked for really answering (not only running); a service that hangs or stops is restarted, and the administrator is emailed. After three failed restarts in an hour it is left for a person to look at.
• Team members: an account owner gives a developer, designer or colleague their own login (their email address) with only the tools they need. Their actions are recorded under their own name; the owner's password, two-factor setting and team stay the owner's.
• Wildcard certificates (*.domain) for domains using this server's nameservers: one free certificate for the domain and all its subdomains, renewed automatically.
• Billing systems: the standard /json-api interface on port 2087, so the usual hosting-panel modules of Blesta, HostBill and other billing systems work without installing anything (create, suspend, unsuspend, remove, change package and password, usage, sign-in button).
• Web Disk: the account's files as a network drive in Windows, macOS, Linux and phone apps (WebDAV), with logins limited to one folder and optionally read-only.
• Calendars and contacts for every mailbox, synced with phones and computers (CalDAV/CardDAV), found automatically from the domain.
• Errors page for customers: the latest PHP errors of their websites.
• DNS zone template: the administrator sets the records every new zone starts with. Resellers can have their own nameservers (ns1.their-brand.com), used in their customers' zones; the nameservers' address records are added automatically when their domain is hosted here.
• Optional PHP extensions per version (APCu, Memcached, igbinary, IMAP, LDAP, ionCube Loader and more), added and removed from the PHP page.
• WordPress: push a staging copy to the live site (files, and the database if chosen), with the live site saved first and an "Undo" button. Daily check of plugins and themes against a public vulnerability database; the owner is emailed about new findings.
• Firewall: optional public lists of known attackers (Spamhaus DROP, blocklist.de, CINS, abuse.ch), updated every 6 hours. Addresses that signed in to the panel recently are never blocked.
• Leech protection for password-protected folders (a login used from too many addresses in an hour is turned off), and directory listing per folder.
• Ten more applications in the installer: Moodle, Akaunting, Mautic, osTicket, Backdrop CMS, FreshRSS, MyBB, DokuWiki, Piwigo and YOURLS. Moodle picks the newest release this server's database supports.
• Languages: German, Spanish, Persian, French, Indonesian, Portuguese (Brazil), Russian and Turkish, next to English and Arabic.

Security

• Any program on the server could send email to the world through the local mail server without signing in (uncounted spam from a hacked website). Every account now sends through its own internal login, and relaying without a login is refused.
• Applications that finish in their own setup page: the database password is shown once (it was never shown).
• Moodle's data folder is private to the account (Moodle's default would open it to every account on the server).

Fixed

• Websites in a nested folder (e.g. domains/example.com/public_html or sites/example.com) could not be reached and their owner could not write there: the folders in between belonged to root. They are created as the account, and earlier ones are handed to the account. This also made three transferred accounts fail to import.
• A staging copy refused because of the database limit still created its subdomain.

Version 0.27.2

Fixed

• Accounts suspended on the old server were imported as active by the Transfer Tool (a site suspended for non-payment came back online). They now stay suspended here.
• Archives pulled from another server stayed in /backup/import after a successful import; with many transfers they filled the disk. They are deleted once the account is imported.

Version 0.27.1

Fixed

• The daily snapshots counted against each customer's disk quota a second time (the copies kept the customer as owner), so customers reached their limit at about half of their package. Snapshot copies now belong to the system; existing ones are changed on update.
• Composer was not installed when the panel updated itself (needed by the Laravel installer).

Version 0.27.0

Added

• FTP accounts: customers sign in with their panel username and password, or create accounts name@domain limited to one folder, with an optional size limit. FTP with TLS (the server's certificate), passive ports opened in the firewall, repeated wrong passwords blocked. Transfers from cPanel bring the FTP accounts with their passwords.
• Feature lists: choose which tools a package includes (admin and resellers). A tool left out disappears from the customer's menu and home page and its pages are refused; leaving out FTP also stops FTP sign-in.
• Remote MySQL: customers allow addresses (an office, an application server) to reach their databases; every database user works from there with its own password. The database server listens on the network only while addresses are allowed, and the firewall lets only those addresses reach it.
• Disk usage: the size of every folder (with drill-down) and the 30 biggest files, measured in the background.
• Terminal in the browser: a root shell for the administrator; for customers with shell access, the same sandbox as SSH. One-time sign-in per connection, closed when the browser goes away or after 30 minutes without activity.
• PostgreSQL databases and users, with the same full rights for every user of a database. Included in backups, daily snapshots and their restores, and in the disk usage.
• Mailing lists: list@domain sends each post to all members, from the list's address (accepted by mail providers that check the sender), with a personal one-click unsubscribe link in every message. Who may post: members, moderators only (announcements) or anyone. Addresses that keep bouncing are stopped automatically.
• Application installer (our own): Joomla, Drupal, Grav, PrestaShop, OpenCart, phpBB, MediaWiki, Nextcloud, Matomo and Laravel, downloaded from each project's official site and checked against the checksum it publishes, installed with their own database. Removal deletes the files and, if chosen, the database.
• MIME types and handlers per website: extra file types, extensions run as PHP (e.g. .html), and CGI scripts in cgi-bin (Perl, Python, shell) run as the account.
• Ruby applications (Rack: Sinatra, Rails…) next to Node.js and Python; gems are installed in the application's own folder.
• Cloudflare: connect your own Cloudflare account, add domains, copy their DNS records, switch the proxy per record, purge the cache, set SSL to Full (strict). Visitors behind Cloudflare are seen with their real address (trusted from Cloudflare's addresses only).
• Site builder: a one-page website from six designs, the customer's texts and pictures, left-to-right or right-to-left, published as a static page.
• Servers: manage other servers running this panel from one place (status, accounts, create accounts, one-click sign-in to a customer's panel there). DNS cluster: servers copy each other's zones (signed transfers), so nameservers can be on different servers.

Security

• Customers now see only their own processes: before, a customer's code could read the command lines of every program on the server, which can carry passwords.
• Passwords that some applications only take as command-line options are hidden in the task log and in error messages.

Fixed

• Updates no longer take websites down: the web server is restarted gracefully on a running server (it was stopped and started, and an update could stop half way when it took more than 3 seconds to start).
• A new account sometimes got no certificate for 6 hours (it was tried before the account's folder existed and then held back).
• Virus scans failed with "Not a regular file" on every file, and the file watcher did not send files to the scanner. Folders such as .cache and .config, where malware hides, are checked too.
• Transfers remove lines in shell startup files and user services that start a program the way the cron guard refuses (seen with a cryptominer in a real transfer).

Version 0.26.0

Added

• License: the panel is activated with a license key (Admin → License, or --license=KEY at install). The license is checked once a day and keeps working for 7 days if the license server can't be reached. Without a license the panel runs as a trial.
• Cryptominer detection: mining programs, their launch scripts and their settings files (pools, wallets) are found by the scanner, including programs without a file extension hidden in dot-folders.
• Transfers no longer import cron jobs that look like malware (miners, scripts downloaded and run straight away, programs run from temporary folders or nested hidden folders). They are listed in the transfer's warnings instead.

Changed

• Error pages, the page for addresses with no website, and the server's response headers no longer name the web server software.

Fixed

• Security: programs the panel runs for a customer (WordPress updates, file operations, restores) could inherit the panel's own open database connection and files. Every program now starts with only its input and output.
• A transfer restore could stop for good when the archive produced many warnings.
• A transfer of an account larger than its package failed with "Disk quota exceeded". The quota is lifted during the import and put back afterwards, with a warning to choose a bigger package.
• Virus scans failed with "Not a regular file" on every file, and the file watcher didn't send new files to the scanner. Scans now also show how many files were checked.

Version 0.25.0

Added

• WHMCS module (admin panel → API Tokens → Download the WHMCS module): accounts are created, suspended, unsuspended, upgraded, have their password changed and are removed from WHMCS; a "Log in to Control Panel" button signs the customer in with a one-time link (single use, 60 seconds); disk and bandwidth usage are sent to WHMCS daily.
• API: POST /api/v1/accounts/{username}/login returns a one-time sign-in link; account data includes disk and bandwidth limits and this month's bandwidth.
• Emails to customers (disk and bandwidth warnings, website down and back up, malicious files) are written in the customer's language; the admin's copy in the admin's language.

Fixed

• Unblocking an address (Protection Shield, Firewall) was undone 90 seconds later unless "Keep these rules" was pressed. Lifting a block now applies for good.

Version 0.24.1

Changed

• The interface language is chosen in each user's settings ("Password & Language") instead of a menu at the top; the server's default language stays in Server Settings.

Version 0.24.0

Added

• Arabic interface, right to left: the admin panel, every customer panel, the login pages, messages and errors (about 1,500 texts). Each user picks a language from the menu at the top (saved on the account); the server's default language is set in Server Settings. Numbers, addresses and code stay left to right inside Arabic text.

Version 0.23.0

Added

• Page cache for WordPress sites, built into the server: visitors get ready-made pages (about 10× more pages per second, average wait 0.24 s instead of 3.2 s with 20 simultaneous visitors on one core). Signed-in users, shopping carts, the admin area and forms always get live pages; a response that sets a cookie is never stored. Our own small companion plugin clears the cache when content changes (posts, comments, menus, themes, stock). On by default for new WordPress installs; a switch and a "Clear cache" button on each site's card.

Fixed

• Sites could freeze for up to a minute when several visitors arrived at the same time: the web server's workers held every PHP process with idle connections. The number of PHP processes now matches what all workers may hold (computed from the server). All sites are rebuilt on update.

Version 0.22.0

Added

• Account isolation. Cron jobs, SSH sessions of accounts with shell access, and applications (Node, Python) run in a sandbox per account: they see only their own folder in /home, their own processes and their own entry in the user list, a private /tmp, and none of the server's configuration. They also count towards the account's resource limits.
• SFTP is confined to the account: no system files, no list of accounts; the usual paths (/home/<user>/public_html) keep working.

Changed

• The lists of every customer's email addresses and forwarders, the DNS zones and the list of accounts can no longer be read by customers.
• Cron jobs run from the server's schedule (one file per account) instead of each account's own crontab; nothing changes in the panel.

Fixed

• Applications of an account with resource limits could fail to start on their next deploy (0.21.0 put the account's processes where the system cannot start services).

Version 0.21.0

Added

• Resource limits per account, set in the package: processor (% of one core), memory and number of processes, enforced by the kernel. An account over its processor limit is slowed down; over its memory limit only its biggest process is stopped (the request fails at once instead of hanging); other accounts are never affected. PHP, cron jobs, SSH sessions and applications all count.
• Customers see their limits, memory and processes in use now, and on which days their sites reached a limit (with advice to move to a bigger plan); the admin's daily process log shows the same for every account.
• Existing packages stay unlimited until the admin sets limits; new packages start at 1 core, 1 GB and 100 processes.

Version 0.20.0

Fixed

• Disk quotas switched off after the first kernel update and restart (the new kernel lacked the quota module). Future kernels now bring it, and the agent turns quotas back on at start if they are off.
• Mail sent by customers who signed in (port 587) could be rejected as spam because of the name or address of the computer they send from. Those checks are skipped for signed-in senders; the content is still checked.
• WordPress in a language whose download package isn't published yet (e.g. Arabic right after a release) failed to install. WordPress is now installed and the language pack added after.
• A failed WordPress installation can be started again or removed from its card.
• The installer no longer creates a DNS zone for a domain that is served by other nameservers (e.g. the provider's name, or a company domain hosted elsewhere); it lists the records to add there instead.

Version 0.19.1

Fixed

• Installing on a brand-new server no longer stops when the system is still running its own first updates: the installer waits for them.

Version 0.19.0

Added

• Security headers on every website (content-type sniffing and framing by other sites blocked, referrer limited); customers can turn them off per site. HTTPS can be enforced in browsers (HSTS) per site with a valid certificate.

Fixed

• Access lines in .htaccess files (Deny from all, Require all denied, <Files>/<FilesMatch>, Allow from / Require ip exceptions) are now enforced. Before, folders closed this way on another server were open here. Changes, new and deleted .htaccess files apply within a minute.

Version 0.18.0

Added

• Web application firewall in the Protection Shield: recognises SQL injection, reading server files, command and script injection, attack tools and searches for secret files (.env, .git, configuration backups). Monitor mode (the default) records attacks; protect mode refuses them before they reach the website and blocks addresses that keep attacking. Sensitivity setting; customers can turn it off for a single site.
• File watcher: new and changed website files are checked every 2 minutes with the antivirus and our own signatures for web shells, obfuscated code and PHP hidden in images. The customer is emailed; files go to quarantine automatically when that is turned on.
• The scheduled malware scan also uses our own signatures.

Fixed

• Bounces of the panel's notices no longer loop back to the server (the server's own name is now a local mail destination).
• The update log now shows the version updated from.

Version 0.17.0

Added

• Protection Shield: watches every website's traffic about once a minute (reusing the bandwidth pass, no extra load). Addresses that guess passwords on WordPress, Joomla or Drupal across the server's sites are blocked in the firewall (60 minutes by default, 24 hours when they come back). The server, allow-listed addresses and anyone who signed in to the panel recently are never blocked.
• Upload-folder protection: scripts can no longer be run from upload folders (a common backdoor on hacked sites); customers can turn it off per site.
• Shield page for the admin (attacks stopped, blocked addresses with one-click unblock, most active attackers, recent events) and a Protection section for customers showing attacks on their sites.

Changed

• Directory listing is off on all websites.

Version 0.16.0

Added

• Security Advisor: checks the server's configuration (SSH root logins, firewall, brute-force protection, automatic security updates, pending updates, restart needed, database administrator, open ports, two-factor sign-in of admins, panel certificate, backups off the server, disk space, quotas) and explains each finding, with one-click fixes where safe.
• IP Addresses: detects the server's public addresses and dedicates one to an account; the account's DNS records follow.
• DNSSEC per zone (admins and customers): the DNS server signs the zone and rolls its keys; the DS record to add at the registrar is shown with a copy button.

Changed

• DNS zone files moved to /var/lib/bind/whm (needed for DNSSEC signing); existing zones move automatically.

Version 0.15.0

Added

• WordPress staging: one click copies a site (files and database) to a subdomain such as staging.example.com, rewrites its addresses and hides it from search engines; the live site is untouched.
• Uptime monitoring: every website is checked every 5 minutes; customers and the admin get an email when a site goes down and when it is back. Customers see uptime for 24 hours, 7 and 30 days and the response time; the admin dashboard lists sites that are down.
• Admins can move an account to a reseller (or back), with the reseller's limits checked.

Version 0.14.0

Added

• Daily snapshots (incremental): every night each account's files, email and databases are copied; unchanged files are shared with the previous day, so two weeks of snapshots take little more than one. Admins and customers browse any day and restore a file, folder, database or email — into a new folder or in place.
• Install your own SSL certificate (bought elsewhere): the certificate, key and CA bundle are checked (match, domain, expiry) before going live; automatic certificates never replace it while valid, and one click switches back.
• Access Control for customers: IP Blocker (addresses and ranges per website) and Hotlink Protection (images, video and PDFs only on your own sites), next to password-protected folders.
• Git Deployment: connect a GitHub, GitLab, Bitbucket or any Git repository, deploy a branch into a folder by button or automatically on every push (webhook), with a deploy key for private repositories and an optional build command (e.g. composer install).

Changed

• Admin menu regrouped (Accounts, Websites, Email, Security, Server); the Transfer Tool and backup import moved to "Move to this server" at the bottom.

Version 0.13.0

Added

• Node.js and Python applications: run an app (Express, Next.js, Flask, Django, FastAPI…) on a website or a path of it. Each app is a service of the account (restarted if it crashes and after a reboot, with memory and CPU limits), listens on an internal port only, and has buttons for start/stop/restart, installing dependencies (npm / pip in a virtualenv) and viewing logs. Node.js 22 LTS and Python 3.12 on new servers.
• SSH Access page: add public keys (ed25519, RSA ≥ 2048, ECDSA) to sign in without a password; accounts without shell access stay limited to SFTP.
• Time zone setting for the dates shown in the panels (dates are still stored in UTC).
• Transfers from cPanel keep each domain's DKIM signing key, so mail stays signed with the key already published in DNS.

Changed

• Applications of an account stop when it is suspended and are removed when it is terminated.

Version 0.12.0

Added

• Email autoresponder per mailbox (out of office), with optional start and end dates and one reply per sender per 1–7 days.
• Email filters per mailbox: when From, To/Cc or Subject contains a text, move to a folder, forward or delete.
• Catch-all per domain: deliver mail for unknown addresses to a chosen mailbox (off by default — unknown addresses are refused).
• Redirects: a page or a whole website to another address, permanent or temporary, optionally keeping the rest of the path.
• Directory Privacy: ask for a username and password before a folder (or a whole website) opens.
• Custom error pages (403, 404, 500, 503) per website.
• Visitors page: unique visitors, page views, requests and errors for the last 30 days, most visited pages, where visitors came from and pages not found. Bots are not counted.
• Raw access logs in each customer's logs/ folder, one file per website and month.
• Message Customers: email all customers, active ones, or those on a package (admins and resellers).

Fixed

• The mailbox rules file is kept outside the mail folder namespace, so the mail server no longer reports it as a broken folder.

Version 0.11.0

Added

• External backup storage: every backup is also copied to S3-compatible storage (Amazon S3, Backblaze B2, Wasabi, Cloudflare R2, MinIO), an SFTP server or an FTP server, with its own retention, and a connection test. Restores fetch the copy automatically when the local file is gone.
• Partial restore, for admins and customers: browse the files inside a backup and restore one file or folder, all files, chosen databases and/or email; files can go to a new restored-<date> folder instead of overwriting.
• 15-day trial from the installation date, shown on the admin pages. When it ends, only new accounts and new transfers pause; everything already hosted keeps working.