Everything involved in running NextaPanel as an agency - your servers, your clients, and the business side of it.
Last updated: October 17, 2026
Every agency gets a setup checklist. It opens automatically when you log in, and a notice stays at the top of every page until the required steps are done - click Open setup checklist on it any time. Progress updates by itself as you complete each step.
Required: billing address, branding and panel domain, Cloudflare, a server, a database server, a hosting plan, a payment method and your own SMTP. Optional: an email server, backup storage, an AI chat agent, GitHub apps and Google sign-in.
Go to My Servers in the sidebar, then click + New Server. The form has three short steps:
s1, so several servers can share one domain. The panel creates the DNS records for it.
Click Add Server. The panel checks the server is reachable and running Ubuntu 22.04 or newer, then provisions it automatically over SSH: Docker, Nginx with a self-signed certificate, a resource monitor, a container auto-heal script, and the ClamAV virus scanner (see Server Virus Scanning). This usually takes a few minutes, and you get an email when it finishes.
Once connected, a server's card on My Servers shows its live status and memory/storage usage over 1h, 5h, 10h and 24h windows. A storage bar shows the disk's real used and free space, alongside how much storage is allocated to the client packages placed on it - so you can see at a glance whether a server is filling up or over-sold. From there you can:
Every server gets ClamAV, installed alongside Docker during provisioning. A full scan runs every night and covers the whole server - including every Docker container, running or stopped, and every site on it. Virus signatures update automatically several times a day.
Open Virus Scan (ClamAV) from a server's card to see the last scan: when it ran, how many files were scanned, when signatures last updated, and any infected files found. If a scan finds infected files, you're emailed a report listing them. Servers connected before ClamAV was added get it installed automatically, or click Install ClamAV to do it now; if a setup looks broken, Repair ClamAV Setup fixes it.
Go to DB Servers in the sidebar, click + Add, and choose an engine (MySQL, PostgreSQL, or MongoDB). The form has two steps:
Click Add MySQL Server (or the equivalent for your chosen engine). From the resulting card you can rotate the password live, toggle remote access on or off, and open phpMyAdmin (MySQL) or Adminer (Postgres/Mongo) in one click - both include a built-in terminal straight into the container.
From Email Services, click Add Email Server, pick the server, and choose which services to expose - email sending, email receiving, SMTP submission (port 587) and IMAP (ports 143/993), each a simple toggle. Then pick the MySQL server that stores its domains, mailboxes and aliases (add one under Database Servers first). A TLS certificate for the mail server is generated automatically.
When installation finishes you're emailed the MX, A and SPF (TXT) records to add, laid out as a table - find them again any time under DNS Records on the server's card.
Your clients then manage their own mailboxes: inbox size limits, forwarding (with or without keeping a copy), mailing lists, email routing to an outside provider, and importing mail from their old host. Every mailbox's mail counts toward the client's package storage.
Webmail is a single RoundCube install per agency account; opening a mailbox from any of your mail servers signs the client into the right backend automatically.
Open Block Lists on an email server's card to stop spam and abuse across every domain on that server. Enter one entry per line:
Blocked mail is rejected and the sender gets a bounce. Click Save Block Lists to apply them; if the server isn't running, they're saved and applied once it is.
Connect a Cloudflare account once, with a Cloudflare API token - it never expires, so the connection never needs reconnecting. The exact permissions to grant are listed on the connect screen and in the setup guide. From there you can add a new domain or import a zone you already manage, add or edit any DNS record type (A, AAAA, CNAME, MX, TXT, NS, SRV, CAA), and set IP access rules to allow, block or challenge by IP, range or country.
A domain doesn't need a site ready for it right away - hold it in your domain pool and assign it whenever you are.
Any server with a gateway installed runs its own private Nginx reverse-proxy container. From Gateway, add a route sending a domain to a container, a local target, or a remote one, over HTTP, HTTPS, TCP or WebSocket - with a path prefix, custom headers, a host-header override, a redirect, or maintenance mode.
Traffic can be spread across more than one backend (round robin, least-connections, IP-hash, weighted, or random), with backups that only activate if the primary goes down. A migration tool moves a site still on its own published port over to gateway routing safely, with a reachability check and rollback.
Site backups are stored only in your cloud storage - never on the hosting server itself. From Cloud Storage, add a connection - SFTP, FTP, Backblaze B2, Hetzner Storage Box or Google Drive - and tick the servers backed up here: sites on those servers back up to that storage, on the schedule their plan defines (and whenever a client makes a manual backup).
From Firewall, add a rule scoped to a server: allow or block, one or more ports, one or more IPs. It's applied immediately as a real iptables rule over SSH and persisted so it survives a reboot.
Go to Users in the sidebar, then click + Add User. The form has three steps:
Tick one or more of your site plans, and set a Qty next to each - useful if a plan allows more than one unit per client.
Set the account to Active or another status. New accounts are created with the "user" role, a verification email goes out automatically, and the client must verify it before they can log in.
Click Add User. The panel places their sites on whichever of your servers currently has the most free capacity. You can resend their verification email or mark them verified yourself later from the same page. Removing a client is a soft delete - every real site, container and database they own is torn down properly, while their invoice history is kept for your own records.
Go to Site Plans in the sidebar, then click + Add Site Plan. The form has several short sections:
Email Sending Enable and Staging Site Allowed are simple checkboxes. Under Allowed Site Types, tick which of WordPress, Laravel, PHP Site and Node.js a client on this plan is allowed to create.
Click Add Site Plan. None of these limits are cosmetic - periodic checks lock a site's files or revoke database privileges the moment a client goes over what their plan allows. A plan needs an active database server before it can be created.
A plan's storage limit is enforced per package across everything the client runs on it: site files, each site's container system files, databases (staging sites included) and every mailbox's mail. Clients set each mailbox's own size limit when they create it, within the package total.
Every client site on PHP (WordPress, Laravel and PHP sites) is scanned automatically once a day for malware signatures and dangerous code. Scans run one at a time per server to keep the load light. Each report is emailed to the site's owner and to everyone with team access to that site, so clients hear about a problem straight away.
Clients can also run a scan any time from the site's Malware Scanner tab. On WordPress, core files are verified against official checksums so genuine core files aren't flagged.
From Billing > Payment Methods, connect a real way to collect payment from your clients instead of the honor-system default (where you mark invoices paid by hand). Three methods, each independent:
Turn a method on and its fields appear; save just that one card without affecting the others. Once saved, a credential is shown masked - click Change to replace it, or leave it alone to keep what's already saved.
With at least one method enabled, your clients get a real checkout - at signup, when subscribing to a new plan, and when paying an invoice - instead of the free/instant flow. PayPal and Stripe activate automatically the moment payment completes; an Offline submission needs your review first, from the Pending Approvals tab on the same page - approve it to activate the subscription or mark the invoice paid, or reject it with a reason the client will see.
Let your clients search for, buy and register new domains from their own Domains page, billed through your payment methods. Registration runs through your own DomainNameAPI reseller account.
com or co.uk, without the dot) and set your markup on it.Clients can also transfer a domain in from another registrar. Registered domains are added as zones under your existing Cloudflare connection, so connect Cloudflare first or registration will fail after payment.
From Invoices, generate invoices for a billing period across every active client plan at once, or handle one client's invoice from their own page. Mark invoices paid as payments arrive, and filter by paid, unpaid or overdue. Your own server costs are tracked as a separate set of invoices (Server Invoices), kept apart from client revenue.
Server Invoices are what you owe for hosting your own servers on the platform - billed to you the same way you bill your clients. If the platform has a payment method enabled, an unpaid Server Invoice gets a Pay Now button (on the invoice list, and again inside the invoice itself) offering whichever of PayPal, Stripe or Offline Payment are currently available.
PayPal and Stripe mark the invoice paid the moment payment completes. An Offline submission is reviewed by the platform before it's marked paid - you'll see its status update once that happens. Either way, a paid invoice shows exactly how it was paid and its transaction ID, right on the invoice itself.
From Revenues, see income by date, by client and by server - with each server's cost estimated from the monthly price you set when you added it, so you can see real profit per server, not just revenue. Defaults to the current month, with a custom range available.
From Agency Branding, make the panel your own: sidebar logo, favicon, panel name, login page background, home URL and brand colors (primary, secondary and sidebar), with a live preview as you change them. Your branding appears everywhere your clients look - the panel, the login page, invoices and every email.
Set a Panel Domain such as panel.yourcompany.com and add a CNAME record for it pointing to panel.nextapanel.com (DNS only, not proxied). You and your clients then use the panel entirely on your own domain. Reset to defaults removes your logo, favicon and colors.
From Email Settings, send every email you and your clients receive - invoices, tickets, team invites, account notices - through your own SMTP server instead of the platform default. Enter the SMTP host, port, encryption, username and password, and the From email and name clients will see. Save, then use Send test email to confirm it works. Clear returns you to the platform default.
Every email is a clean, mobile-friendly template in your own brand colors and logo, with a plain-text version for mail apps that need it.
Add a second step to your login: after your password, you enter a 6-digit code from an authenticator app on your phone - Google Authenticator, Microsoft Authenticator, Authy, 1Password or any other. Even if someone learns your password, they can't log in without your phone. It also applies when you log in with Google or GitHub.
You get an email whenever two-factor authentication is turned on or off, a recovery code is used, or new codes are generated.
From Login & GitHub Apps, add your own OAuth apps so your clients can:
The page shows the exact homepage and callback URLs to register for each app - they're on your own panel domain, so clients never leave your brand while signing in. Each app is optional: until one is configured, its buttons and menus simply don't appear for your clients. Step-by-step instructions are in the setup guide.
The free Wordfence Security plugin is installed and activated on every WordPress site you host, with its firewall switched on and security alerts going to the site owner. No license key is needed - if a client wants Wordfence Premium, they add their own license from Wordfence > Dashboard in their site's wp-admin.
Tickets gives you one inbox spanning both your own account's tickets and every ticket raised by your subscribers. Live Chat is a real-time queue shared between you and your support team for talking to clients directly.
Let an AI assistant answer live chats instantly, at any hour. In Live Chat, click Config AI Chat Agents, connect an AI provider with your own API key - Google Gemini, Anthropic Claude, OpenAI, OpenRouter or OpenCode Zen - choose a model, and turn on Enable AI Chat Bot.
It answers using your plans, your payment methods and, for logged-in clients, their own sites. When it can't help, it says so honestly. AI-handled chats are marked in your queue, and you or your team can take over any conversation at any time.
Put the same live chat on your own business website. In Live Chat, open Embed and copy the code snippet into your site's HTML. Visitors chat with you (or your AI agent) straight from your website, and their chats land in the same queue as your clients'.
Once you're past handling support yourself, add staff accounts from Support Team - scoped to tickets and chat, without full access to your servers or billing.
From API, generate a Bearer token - named, and optionally set to expire. Anything you'd normally do by hand (creating a subscriber, checking a site's status, triggering an SSO login) can be done through the same endpoints - this very site's own signup and login pages use exactly this API.
Get your own demo agency in a minute - virtual servers, clients and sites, ready to explore. We'll email your login details.