A guided tour of the panel

The first screen is a map of the server, not a list of menus. Tools sit in categories with a line that says what each one does, and a search box finds them by the word you would use: cron, php.ini, mx.

1. 1 Find a tool by what it does. The slash key jumps here from anywhere.
2. 2 Or ask in plain words. The question goes to the assistant.
3. 3 Categories: websites, files, databases, email, software, security, monitoring, customers, the server and the panel.
4. 4 What you used recently and what you pinned lead the page, on every device you sign in from.
5. 5 Every server this panel manages, and changes by you or your team as they happen.

The palette searches pages and actions together. Type a word and it offers the page to open and every action that matches, with the area it belongs to. Destructive actions are marked before you pick them.

1. 1 One box for pages and actions. It opens with Ctrl K on every screen.
2. 2 Go to: the page that matches.
3. 3 Run an action: everything you may run that matches, with its area on the right. The one that removes something is in red.

A request in plain words becomes a plan. The assistant looks things up, previews each change through the same dry run a person would get, and waits. Nothing has changed until you approve.

1. 1 The request, as typed, and what it was about.
2. 2 What it looked up and what it previewed, by action name. Each proposed step says it is waiting for your approval.
3. 3 The plan: its steps, its risk, and when the approval expires. Nothing has changed yet.
4. 4 Values that came from text the assistant read, not from you, are flagged.
5. 5 The exact change, as a diff.

After you approve, each step runs and is marked. The plan stays on the page with what was changed, and an undo remains available for a week.

1. 1 The plan and every step are marked Done once they have run.
2. 2 The change that was applied, the same diff you approved.

A hosting customer gets the same Home, cut down to their own account. The sidebar carries the same categories, and only the tools their plan includes.

1. 1 The same categories as the administrator, limited to this account.
2. 2 Recently used: webmail, the assistant, files, websites, sign-in security, backups.
3. 3 Search or run with Ctrl K, and the activity bell for jobs.

Nothing is a separate mobile site. The Home, the search, the Ask box and every tool work at phone width.

1. 1 The tool search, first on the screen.
2. 2 Ask the assistant from the Home.
3. 3 Recently used tools, one tap away.

A customer opens any of their mailboxes from the panel with one click, no second password. Folders, labels, search and a compose window sit in one page that works at phone width too.

1. 1 Folders, contacts, the calendar, your own folders and labels.
2. 2 Search every folder. The slash key jumps here.
3. 3 Conversations, newest first, with unread marks, stars and attachment clips.
4. 4 Write opens a compose window over the list.

A site opens in place, with its own tabs for domains, PHP, cache, protection and settings. Each tab shows the change before it goes live, and a change that stops the site answering is undone for you.

1. 1 The site's own tabs: Overview, Domains, PHP, Cache, Protection and Config.
2. 2 The firewall: off, detect only or block, with its strictness.
3. 3 A request limit per visitor, so one bot cannot flood the site.
4. 4 Every change is checked before it goes live.

A zone shows its health and DNSSEC state first, then its records. Click a value to change it; the changes wait in a bar until you review and apply them.

1. 1 Health, DNSSEC and the nameservers at a glance.
2. 2 Import, export, history, a zone check and ready-made service records.
3. 3 Add a record in one row.
4. 4 Every record is editable in place.

Each database has its connection details in the language you use, its users, import and export, backups, a query box and a database tool.

1. 1 Connect, users and access, import and export, backups, a query box and a database tool.
2. 2 A connection string per language. The password is a placeholder, shown once when a user is created.
3. 3 Host, port, charset and the number of tables.

Every backup, check and test restore is listed with its target, its result, the size it added and how long it took. Finished runs are kept in the history.

1. 1 Overview, targets, schedules, runs and restore.
2. 2 Checks and test restores run beside the backups, so a backup you cannot restore does not go unnoticed.
3. 3 The result, the size added and the time taken for every run.

Search what your servers and sites wrote, filter by time range, site and source, or follow it live. Lines an error produced offer an explanation from the assistant.

1. 1 A search, a time range, a site and a source. Live tail follows the log as it is written.
2. 2 The site's own access lines, each one attributed to its account.
3. 3 Error lines offer Explain this error.

A reseller signs in to the same panel and sees only the accounts that belong to them, with the same tools to create, edit and suspend them, plus their own branding.

1. 1 Accounts, active, suspended, needing attention.
2. 2 Only this reseller's own customers are listed.
3. 3 Create an account for a new customer.

One list for all servers. Each account shows its state, its server, whether SSH is on and when it was made, and a row opens to edit it in place.

1. 1 How many accounts there are, and how many need attention.
2. 2 Each account is a real Linux user, with its home folder shown under the name.
3. 3 Create account, and re-apply every account's settings to the servers.

Plans are limits per module: disk, memory, CPU, sites, mailboxes. The same page has a capacity planner, overselling and the server's own sizing profile.

1. 1 Plans, the capacity planner, overselling and the server profile.
2. 2 Edit a plan in place and see the effect before it applies.
3. 3 Generate presets for this server's hardware, or export and import plans.

An import goes through five stages: the source, a report, the mapping, a dry run and the commit. The page says what each format carries and what it does not, before you start.

1. 1 From a backup file, or live from another server.
2. 2 Source, report, mapping, dry run, commit.
3. 3 Checking unpacks the backup into a staging area and reports. Nothing is created yet.
4. 4 What each format carries, and what is skipped.

Every capability is a signed module. The Store installs, upgrades and removes them on a running panel, and each of those shows its plan first.

1. 1 The update channel: stable, beta or long-term.
2. 2 Side-load a signed bundle on a server that cannot reach the Store.
3. 3 Free modules and the add-ons your licence unlocks.

A small server does not have to carry everything. Each module can be switched off and on again; switching one off keeps all of its data.

1. 1 Search, or show only what is on or off.
2. 2 Needed by: what depends on a module, so nothing is switched off from under another.
3. 3 Switch off. A small install can switch on what it left out without running the installer again.

Present the panel as your own product: name, accent colour, support addresses and footer, with a preview in light and dark before you publish. Host names, nameservers, email templates and customer pages have their own tabs.

1. 1 Brand, host names, nameservers, email templates and customer pages.
2. 2 The accent colour is adjusted so text on it stays readable in both themes.
3. 3 A preview of your sign-in card, in light and dark.
4. 4 Published versions are kept, and reverting publishes that version again.