Understand the difference between Reseller, Master, and Alpha accounts, how the hierarchy works, and which portal features are available as you grow.
Best for launching your own VPS brand, selling servers within your allocated pool, and managing your own customers without creating sub-resellers.
Best for agencies and providers that need to create and manage reseller accounts underneath them while keeping resource use controlled.
Best for established providers that need the deepest reseller structure, larger resource pools, and oversight across multiple reseller brands.
Every level can sell VPS services under their brand. The main difference is how much hierarchy and resource capacity you need beneath your account.
Create customer VPS services
Reseller:Yes
Master:Yes
Alpha:Yes
Create standard reseller users
Reseller:No
Master:Yes
Alpha:Yes
Create master reseller users
Reseller:No
Master:No
Alpha:Yes
Manage users below account
Reseller:Own account only
Master:Reseller users
Alpha:Master and reseller users
White-label app branding
Reseller:Yes
Master:Yes
Alpha:Yes
Scoped API key access
Reseller:Self-service
Master:Self-service and managed users
Alpha:Self-service and managed users
Best fit
Reseller:New VPS reseller brands
Master:Providers with sub-resellers
Alpha:Large multi-tier reseller networks
Focused answers for this reseller level, including who it suits and how it behaves in the portal hierarchy.
A reseller account is designed for selling VPS services directly to your own customers. You can manage your own account, branding, API keys, addons, and VPS lifecycle actions inside the portal.
No. Standard reseller accounts sit at the customer-facing level of the hierarchy. If you need to create reseller users below you, choose a Master or Alpha reseller plan.
Yes. Reseller, Master, and Alpha roles are brandable in the portal, so your customers can see your app name and branded experience rather than a generic control area.
Yes for direct VPS selling. The platform includes API access and WHMCS-ready provisioning workflows. Master or Alpha becomes more useful when you also want to sell reseller accounts beneath your own brand.
Focused answers for this reseller level, including who it suits and how it behaves in the portal hierarchy.
A Master reseller can create and manage reseller users below their account, while a standard reseller cannot. Master is the better fit when you want to operate multiple reseller customers or brands from one parent account.
No. Master resellers can create reseller-level users underneath them. Alpha accounts sit above Master in the hierarchy and are created by the platform administrator.
The portal uses package-driven pooled resource enforcement. Child accounts can only be assigned packages that are visible and allowed within the parent reseller tree, helping keep CPU, RAM, storage, IP, and server usage under control.
Yes. Higher reseller roles can manage API access for users beneath them, including creating and revoking keys where needed.
Focused answers for this reseller level, including who it suits and how it behaves in the portal hierarchy.
Alpha reseller is for established hosting providers, multi-brand operators, and businesses that need the largest resource pools and the deepest reseller structure available in the LiquidServers lineup.
Alpha resellers can create Master reseller and standard reseller accounts below them, giving them the most flexible hierarchy for building a larger reseller network.
Yes. Alpha accounts have the same white-label, API, package, addon, user, and VPS lifecycle tooling, with higher-tier hierarchy control and larger plan allocations.
Yes. Alpha is the best fit when you need to manage multiple reseller brands or business units while keeping provisioning, customer accounts, and resource allocation under a central structure.
These apply across the reseller levels and reflect how the LiquidServers portal handles daily operations.
The portal supports provider-backed VPS creation, boot, reboot, shutdown, suspend, unsuspend, reinstall, terminate, archive, and sync workflows. Reinstall actions include extra confirmation because they are destructive.
No. Terminated VPS records are archived, hidden from the default fleet view, excluded from active usage totals, and no longer manageable.
Yes. Resellers can create and revoke scoped API keys, and higher reseller roles can manage keys for supported users beneath them. The portal includes API documentation for packages, VPS services, user actions, and lifecycle workflows.
Yes. VPS provisioning and lifecycle actions are backed by provider-integrated workflows, including plan and location resolution, provider sync, normalized statuses, and provider-error visibility.
Yes. You can start with a standard reseller plan and move into Master or Alpha as your reseller structure, resource requirements, or customer base grows.
Tell us how many customers, resellers, or brands you expect to manage, and we can help match the right VPS reseller level to your launch plan.
