Where Reqad is headed

• Login page for the admin panel, with brute-force protection and automatic firewall bans
• Two-factor authentication with recovery codes, and passkeys
• Confirmation before sensitive changes, remembered devices, email codes for new devices and login alerts
• Firewall allowlist for the panel port, with automatic rollback if you lock yourself out
• Brute-force protection for webmail logins

• Hardened kernel settings and tighter file permissions between sites
• Accounts see only their own processes
• CPU, memory and process limits for SSH, cron and the browser terminal
• Shell access per account: full, jailed (own home only) or SFTP only
• MySQL connection limit per account
• Check and fix the owners and permissions of an account's files, with an undo script

Off by default; one switch turns on both.

• Git deployments from GitHub, GitLab, Gitea or Bitbucket, on every push by signed webhook, with build steps, atomic releases, a health check and one-click rollback
• Node.js and Python apps, run as the account's own user in their own sandboxed service and served through nginx with SSL and websockets
• Presets for PHP, Laravel, static sites, Node.js and Python, and managed Node.js and Python versions
• Deploy with git push to the server itself

Manage your server from your own AI assistant: Claude, Cursor and other MCP clients. Off by default.

• Connects over SSH, with nothing new opened to the internet; works from Linux, macOS and Windows (PuTTY / Pageant)
• Server status, what needs attention, logs, the mail queue, services, accounts, databases, mailboxes, deployments and apps
• WordPress: versions and available updates, core / plugin / theme updates with a database backup first and caches emptied after
• Tokens for the whole server or one account, read-only or not, expiring; deletes need your confirmation, and every call is logged
• Connections over HTTPS, for assistants that cannot use SSH