Resellers and plans
In preview
Four levels of people, each confined to their own subtree, and plans whose limits are enforced by every module rather than checked once at sign-up.
Built and lab-tested
- Administrator, reseller, user and sub-user. Each sees and manages only their own subtree.
- Roles built from the permissions each module declares, plus your own custom roles. Grants can be scoped to one site, domain or folder, and a deny wins everywhere it applies: lists, details and actions in DNS, websites, mail, databases, files and the rest, for administrators too.
- Plans with limits (domains, sites, mailboxes, databases, storage and more) reserved and released by each module as things are created and removed.
- Every hosting account is a real Linux user with its own systemd slice for CPU, memory, IO and process limits, and disk quotas where the filesystem supports them.
- Act as a customer with a reason, a visible banner, a time limit and an audit trail. Passwords, passkeys and tokens cannot be changed while acting as someone else.
- Suspending an account ends its sessions and API tokens in the same step.
- Team: an account owner invites sub-users scoped to chosen resources, with an expiry.
- Plans say which modules they include, and a call into a module the plan leaves out is refused.
- Install profiles, plan presets, overselling and a capacity planner. Sizing is applied: a 1 GB and a 4 GB server run different settings.
- White-label branding per host name, with reseller isolation and branded emails.
Not there yet
- Gateway and API keys scoped to a reseller.
Every action in this area is in the panel, one keystroke away in the command palette (Ctrl K), on the command line and in the API, and most changes can be previewed as a plan first. Built and tested in our lab; RespireCloud is not released yet.
