MARKETPLACE / Hosting panels
Use Plesk to give your hosting work a consistent administration workflow. Plan websites, subscriptions, extensions and maintenance around the people who will use the panel and the services your cloud instance is expected to run.
01 / Plesk
Plesk provides an interface for organising websites and related hosting tasks. Its subscription and user model can help an internal team or an agency define how sites are managed. The selected edition, installed extensions and operating system determine the capabilities available in a particular deployment.
Before choosing the image, decide which services belong on the instance. Web applications, databases, DNS and mail each have their own capacity and recovery considerations. Confirm the panel license and any paid extensions, then build a maintenance process that covers both Plesk and the applications hosted through it.
Organise customer sites with clear administrative ownership and a repeatable handover. Review subscription permissions so a collaborator can maintain the intended project without receiving unnecessary server-wide access.
Give an internal team a familiar place to manage domains and hosting settings. Match the panel configuration to the actual application runtimes and services the business needs to operate.
Use separate subscriptions or hosting arrangements where appropriate for different projects. Validate isolation, resource use and backup scope rather than assuming that separate domains create separate failure boundaries.
02 / DEPLOYMENT DECISIONS
Confirm the current image, operating system, software versions and license requirements in the cloud configuration.
Scroll horizontally to view all columns.
| Decision | What to review | Why it matters |
|---|---|---|
| Edition and extensions | Check the Plesk edition and any extension licenses needed for your workflow. | A feature shown in vendor documentation may require a particular entitlement. |
| Runtime compatibility | Confirm the image operating system and available application runtimes against the sites you will host. | Applications and extensions can impose requirements beyond the panel itself. |
| Subscription boundaries | Define administrators, customers and collaborators before importing live projects. | Permissions and subscription settings influence how safely multiple projects share a host. |
| Backup scope | Include subscription data and the related databases, mail and configuration where applicable. | A restore should reproduce the service your users depend on, not only its directory structure. |
THE OPERATING VIEW
An example hosting structure. Subscription ownership, application runtime and recovery should be planned together.
FROM PLAN TO OPERATION
Validate the application and prepare its operating process before depending on it for daily work.
Review the Plesk image, current operating-system support, edition and licensing before configuring the cloud instance.
Set hostname, HTTPS and administrative access, then configure only the DNS, mail and runtime services the deployment requires.
Create or migrate a representative website, review its permissions and test application, database and scheduled-task behavior.
Document updates, extension ownership and backup retention; test a subscription restore before onboarding more sites.
PRACTICAL QUESTIONS
Clarify the application and operating requirements before choosing the deployment.
Discuss your requirementsExtension availability and licensing vary. Review the selected edition and the extensions your workflow requires, then confirm which costs and entitlements apply to the deployment.
Plesk offers WordPress-related tooling in supported configurations. Review the installed edition and extensions, then test the update and staging workflow you intend to use with your own themes and plugins.
That depends on your operating requirements and existing providers. Decide the responsibility for each service before deployment and test the corresponding records and delivery paths.
Check Plesk’s supported migration paths and source-system requirements. Test a representative subscription and its dependencies before scheduling the transfer of the full hosting portfolio.
KEEP EXPLORING
Web publishingPlan a WordPress cloud deployment with guidance on PHP, databases, media, backups and maintenance. Explore WordPress on FibaCloud Marketplace.
Explore deployment
Hosting panelsPlan cPanel and WHM on cloud infrastructure: account separation, DNS, mail, licenses and recovery. Explore the FibaCloud Marketplace deployment.
Explore deployment
Hosting panelsExplore DirectAdmin on FibaCloud and plan administrator, reseller and user access, hosting services, software licensing and account recovery.
Explore deploymentOFFICIAL DOCUMENTATION
Use the documentation for the product and version selected at deployment.
FIBACLOUD / Plesk
Review the available configuration and choose the resources for your project.
