Choose the guide for your task
Use search with a tool name, field, error, record type or API path. This reference covers the reviewed single-server Admin and Customer source. Installation and basic setup are in the original getting-started guides; the feature guides below explain the concrete forms, permissions and checks.
Hosting operations
- Accounts and Customer credentials
- Packages, features and resource limits
- Websites, domains and redirects
- PHP, INI and MIME types
- Files, uploads and transfers
- Database wizard and users
- DNS records, templates and DNSSEC
- Certificates and ACME
- Mailboxes and routing
- Forwarders, filters and autoresponders
- WordPress
- Node.js, Python and Git
- Scheduled tasks
- Backups and selective recovery
Installation administration and integrations
- Local security, MFA and sessions
- Server and service controls
- Firewall and SSH
- WAF and malware
- API tokens and billing inventory
- API request conventions
- Signed extensions and hooks
- Premium addons
Read menu availability correctly
The menu reference names every one of the 269 requested leaves across 32 groups. A destination means that the source connects the label to an existing workspace; it does not certify an installed service or completed public hosting journey. Entries explicitly marked unavailable remain unavailable. Search the exact label to find its group and linked operational guide.
Release and commercial boundaries
EmailaPanel remains a TEST ONLY release candidate for an isolated disposable Ubuntu VM. Native hosting, public DNS/mail/TLS and full recovery acceptance are separate from source interfaces. Panel has no customer billing suite, payment gateway or domain registrar driver. Purchases and main/addon licence management belong to Orbit Area. Domain delegation changes remain with your actual registrar. No plugin purchase grants local login or Linux root access.
Version scope of this expanded reference
The expanded technical reference was reviewed against source available on 21 October 2026, including newer API/CLI and internal lifecycle changes. Your installed kit can expose fewer capabilities. The retained released-candidate qualification is still blocked for an installed hosting pilot and commercial production. Use current capability/version responses and the matching approved kit before a procedure; do not upgrade or bypass a gate simply because a newer source feature appears here.