Create a client mailbox in seconds — not in cPanel.

Yes — that is how it is meant to run. It is a PHP application, so it goes on the cPanel hosting you already have: upload two folders, point a domain at them, and it is live. Nothing gets installed into cPanel itself.

We use it on a laptop during development, which is convenient for testing but not the real thing — your staff need it somewhere they can reach.

Yes. Everyone signs in with their own account over HTTPS, from any network — different offices, home, a phone on mobile data. There is no office-IP restriction to maintain and no VPN involved. This mattered enough that it is the reason we replaced the original single shared key with per-person logins.

Ordinary cPanel hosting with PHP 8.0 or newer — set per domain in cPanel's MultiPHP Manager — and HTTPS, because the console sends a session token and shows mailbox passwords. No database, no Node, no build step, no cron job.

No. It runs comfortably on shared hosting, and neither your staff nor the server needs a static address.

No. It talks to cPanel's API from the outside — it is a client of cPanel, not a plugin inside it. Your mail server, DNS, and every existing setting are left exactly as they are.

It works on the same account, and for a single account that is the simplest option.

If you manage several cPanel accounts from one console, hosting the console somewhere separate keeps its fate separate from theirs. We will recommend based on your setup.

Rare, but it happens: some hosts block outbound connections to the cPanel ports, or a server calling its own public hostname.

The usual fix is to point the configuration at the server's hostname rather than the domain. If the host blocks it outright, the console can be deployed on a different server — it only needs to reach the API over HTTPS.

No. It uses a scoped API token that you create in cPanel and can revoke whenever you like. The token stays on your server and is never sent to a browser.

Yes, and most people end up doing that. There is a box at the top of the screen that takes a name, a pasted address, or a short command — /new, /open, /find, /pass, /del. Typing /help lists them, and the slash is optional.

Those commands are handled inside the browser: no API key, no network call and no cost. There is also an optional AI mode for full sentences, which is off by default — it needs your own provider key and it sends the text you type to that provider, so it is a deliberate choice rather than something that happens quietly.

Yes. Paste a list of names, or bring a CSV, JSON or plain text file, and it works out the whole batch before it starts: what will be created, what already exists on the server, what is duplicated inside your own list, and what needs fixing first. A list longer than your hourly allowance is flagged before it runs rather than stopping halfway through.

One honest limit: creation is bulk, reading is not. The codes still have to be read one inbox at a time.

No. It opens the mailbox in webmail, already signed in and pointed at the inbox. Reading the activation mail or the OTP is done there, by a person, exactly as it is today.

No — and we would not claim otherwise. It removes every step before and after the code. Reading the code is the part that stays human.

No. They keep their passwords, their mail and their settings. This creates ordinary cPanel mailboxes, and it can open or reset the ones you already have.

The form tells you while you are still typing, and cPanel refuses a genuine duplicate outright — so you cannot end up with two mailboxes that nobody can tell apart six months later.

It is a policy you choose, per account: a standard password for throwaway mailboxes, a fresh random one each time, or one you type yourself. Many teams use the standard password for temporary inboxes and random ones for anything long-lived.

Worth knowing: cPanel never reveals a mailbox's password through any API, so a random password has to be copied at the moment the mailbox is created.

In the browser that created the mailbox, not in a server-side vault. That is a deliberate trade: there is no central store of client credentials to steal, but a password does not follow a staff member to another machine.

A shared, encrypted vault is something we can build into your deployment if you need one.

Each staff member has their own login, and you decide which cPanel accounts each one can reach. Removing someone's access takes effect on their next click, not at the next restart.

Yes: who created or deleted what, when, and from which address. Passwords are deliberately left out of it — a record of what happened should not become a second place to leak from.

It starts rejecting mail silently, and that includes the OTP you were waiting for. The list shows how full each mailbox is and warns as it approaches the limit, so set a larger quota for the mailboxes you plan to keep.

Never. Deleting is manual, one mailbox at a time, behind a confirmation. A timer that deletes an inbox somebody was still using cannot be undone.

Yes. Each cPanel account is configured separately with its own token, and a staff member can be given access to one, some or all of them. One account having a problem does not affect the others.

Yes. Everyone signs in with their own account, so there is no office-IP restriction to maintain — which is one of the reasons we moved away from a single shared key.

cPanel hosting on PHP 8 or newer; a scoped API token from your cPanel account; the domains or subdomains you want to create mailboxes on; and how many staff need logins.

Very little — and we would rather under-promise here. The tool is deliberately small: one box to type in, one list, and a handful of buttons. There is a searchable help page built into the console, one click from the header, covering the everyday tasks, the shortcuts, and what to do when something looks wrong.

We walk your team through it at handover, and the help page is the part that stays with them afterwards. It is a page, not a support desk — anything structural is a call to us.

Per deployment — tell us how many cPanel accounts and staff logins you need, and we will quote. The contact buttons below reach us directly, and WhatsApp is usually the fastest.