...

Plesk Service Plans: Standardizing Hosting Plans and Customer Resources

With Plesk Service Plans, you can create recurring hosting plans as shared templates for customer subscriptions. This allows you to set resources, services, and permissions uniformly; subsequent changes will generally apply to the assigned subscriptions that are not locked for synchronization. The key factors here are Customer Rights and Synchronization Limits: Some values remain individual even though a subscription is considered synchronized. Additionally, a plan does not reserve server capacity. Therefore, check available services and resources, as well as the impact of changes, on a test subscription.

Distinguishing Between Service Plans and Subscriptions

A Service Plan is a common template in Plesk for hosting resources, services, and permissions. The Subscription In contrast, this refers to the provision assigned to a customer. A plan can serve as the basis for multiple subscriptions, so the same rate specifications do not have to be maintained individually for each customer.

Suppose you create a pricing plan that includes a website, a set amount of storage, and a specific number of email accounts. Multiple customers can each receive their own subscription based on this plan. Their content and actual usage remain separate; the plan specifies the features included in the pricing plan.

If you later change a relevant plan setting, Plesk can generally pass it on to associated subscriptions that are not locked for synchronization. This simplifies consistent management but does not replace the need to monitor exceptions and customer permissions. Also, not all properties are synchronized equally between the plan and the subscription.

A plan does not automatically reserve the offered server capacity and does not guarantee a specific level of performance. When a plan is created, Plesk does not fully verify whether all intended services and resources are actually available. Therefore, before deployment, check both the installed components and the available capacity, and monitor usage during operation.

The following explanations apply to Plesk Obsidian; for older versions, you should check the features and user interface separately. Even within Obsidian, the range of features depends on components and updates. To understand these levels, refer to the overview of Updates and Components for Plesk Obsidian.

Add-ons, Special Cases, and Reseller Plans

For recurring hosting plans, the shared plan serves as the foundation. Variations can be added depending on the scope or managed entirely on an individual basis. This choice determines whether future changes to the shared plan will still affect the respective customer’s subscription.

Plesk Modules by Purpose and Limitations
Building blockPurposeSignificant Limit
Service PlanShared Template for Customer SubscriptionsDoes not fully verify actual availability
SubscriptionProvides resources and services to a customerMay differ from the plan or be locked for synchronization
Add-onComplements a plan-based subscriptionOnly one copy of the same add-on per subscription
Custom SubscriptionCustomized configuration without being tied to a specific planNo add-on plans available
Reseller PlanEstablishes a framework for the reseller's resources and rightsNot to be confused with a hosting plan for its customers

A Add-on This is a good option, for example, if a customer needs additional storage but is otherwise satisfied with their current plan. You can assign several different add-ons to a subscription; however, you cannot assign the same add-on more than once. Therefore, if you have another similar need, you must select a different suitable configuration.

A Custom Subscription It is suitable for custom combinations but is not linked to a service plan. As a result, it does not receive any central changes to that plan and cannot use add-on plans. The freedom this provides comes with the responsibility of maintaining the equipment independently.

A reseller plan establishes a different framework: Among other things, it defines the resources and permissions of the reseller, who uses it to create their own customer offers. A customer plan cannot grant a customer a right that the reseller itself does not have. For customer subscriptions, the reseller also needs at least one assigned IP address. Therefore, check your own framework first before setting up pricing plans.

What Plans Actually Drive

Plesk groups plan settings by categories such as resources, permissions, hosting, PHP, mail, DNS, and performance. This structure helps when designing a plan, but it does not mean that every setting will be applied equally to existing customer objects if a change is made later. For operational planning, the scope of each setting is crucial.

Particularly important are Customer Permissions: Not only do you specify what customers are allowed to change on their own, but you can also opt out of central synchronization for those settings. If a customer is allowed to manage their DNS zone, their own settings can remain in place instead of being overwritten by a later central configuration. The subscription can still be considered synchronized.

For PHP, you should make two separate decisions. Permissions for managing general PHP settings apply to these values and their synchronization. Selecting the PHP version and handler is a separate permission. A plan can therefore offer different levels of self-management; at the same time, check which versions and handlers are available on the server.

If you want a plan to have PHP settings that are as consistent as possible, take the relevant permissions into account right from the planning stage. If customers are allowed to manage these settings themselves, you should factor in potential issues with support and changes, rather than treating them as errors across the board. Conversely, a centralized policy limits the customer’s ability to make their own adjustments.

Even without consumer protection laws, there are special Synchronization Limits: Plesk documents web server settings as defaults for newly created domains. According to the administrator documentation, settings under "Logs & Statistics" are not synchronized between plans and subscriptions. Therefore, before making a change, check whether it actually affects existing objects, rather than assuming its effect based solely on the Plan interface.

Plan three hosting plans

Before you create a plan in Plesk, translate your offer into specific resources and permissions. The following table shows three randomly selected sample editorial configurations. These are neither Plesk default settings nor offers from webhosting.de; whether they can be implemented depends on your environment and your own permissions.

Sample pricing plans for planning purposes; these are not Plesk defaults or webhosting.de offers
Sample Rate ScheduleWebsitesMemoryMailboxesGeneral PHP SettingsExceedance
Access110 GB5Centrally managedNot allowed
Extended550 GB25Centrally managedNot allowed
Flexible10100 GB50The customer may manageAllowed

The tiered pricing structure highlights different options: The expanded plan offers more resources without requiring additional self-management. With the flexible plan, customers can change general PHP settings themselves. This permission is also a Synchronization Limit: The affected settings will then no longer be overwritten centrally from the plan. The selection of the PHP version and handler should be considered separately.

The overage policy is also a deliberate pricing decision and does not imply unlimited server capacity. For each plan, specify how you will inform customers about their usage and what operational and contractual consequences an overage will entail. Then test the selected Plesk rule on the test subscription instead of assuming a specific response based on the plan’s name.

A selectable service isn't necessarily ready for use: Before approving an offer, be sure to check email, DNS, PHP versions, and handlers on the specific server. As a reseller, you should also verify your own resources and permissions. A customer plan cannot make a feature available simply by including it in the plan.

AI-generated stock image of an electrical distribution panel and cables in a utility room
AI-generated stock image: Before setting rates, available infrastructure and resources must be assessed.

Create and Review a Service Plan

Open Obsidian in Plesk Service Plans > Add a Plan and assign a name that clearly identifies the rate plan. The English labels are provided for reference; the interface may look different depending on the language, role, and view. You'll need the appropriate administrative permissions to set this up.

Under "Resources," set the appropriate limits—for example, for storage, traffic, websites, and email accounts. Be sure to review the policy for exceeding resource limits as well. Do not simply copy the numbers from an example without checking them: They must be appropriate for your service offering, the available resources, and how you want to handle resource overages.

Under "Permissions," decide which tasks customers are allowed to perform on their own. Users who are allowed to manage general PHP settings not only have the ability to do so, but the corresponding values are also excluded from central synchronization. Check the separate permission for selecting the PHP version and handler independently of this.

Next, verify that the hosting, PHP, email, and DNS settings match the installed and actually available components. A plan is initially just a template; when you create it, Plesk does not fully verify whether all the resources and services listed in it are available. Simply saving the plan does not, therefore, set up a customer subscription.

Assign the plan to a specifically designated Trial Subscription Go there and verify the resources, services, and permissions that are actually provided. In particular, check from the customer’s perspective whether the permitted settings are accessible and whether centrally managed configurations are applied as intended. Document any discrepancies and resolve them before using the plan for other customers.

For similar hosting plans, you can clone an existing plan as needed and make specific changes to the differences. Afterward, compare not only the obvious storage and website limits, but also permissions and overage rules. Also, test the derived plan with a trial subscription before assigning it to a production environment.

Configure Limits and Additional Requirements

If a customer needs additional storage while keeping the rest of their plan terms the same, a Add-on supplement the existing plan. You can assign multiple different add-ons, but the same add-on can only be assigned once. A custom subscription that is not tied to a plan cannot use add-on plans.

Having a separate master plan is often clearer when the same combination of resources and permissions is needed on a regular basis. Before changing a rate plan or removing an add-on, check the current usage and the proposed new limits. Also, clarify what operational and contractual consequences the change will have for the affected customer.

The general storage limit and the rule for exceeding it are determined by the additional hard disk quota . If a supported hard quota is reached, write operations may fail. Under Linux, check whether the operating system supports this feature; an unsupported quota can also cause a synchronization conflict.

Overage and overselling address different issues: The overage rule concerns a subscription’s resource usage, whereas overselling concerns the reseller’s resource policy. Therefore, evaluate both settings separately. A permitted overcommitment does not imply that physical storage is available, nor does it imply that a reseller can allocate resources at will.

Furthermore, a storage limit does not indicate any guaranteed CPU, RAM, or hard drive I/O performance. Plesk lists these limits separately for each subscription; the Obsidian documentation, however, refers to the Plesk Hosting Pack is a prerequisite. Check its availability and licensing in your environment before you include such limitations in a pricing plan.

The specific server environment is also a key factor in database load. The article on explains how to monitor and limit CPU and I/O usage by individual database users on compatible CloudLinux systems: MySQL Governor and Database Resources. This control does not replace either a storage quota or a capacity check on the hosting server.

Roll out plan changes in a controlled manner

Before you modify an existing service plan, get an overview of the associated subscriptions. Make a note of which customers are affected, which subscriptions are suspended or out of sync, and which individual agreements apply. This will help you determine in advance whether a change is technically and contractually appropriate for all customers on that plan.

For a separate Pilot Clone the production plan and assign only a test subscription that is explicitly designated for this purpose to the copy. Make the planned changes to this copy and verify the affected settings and their actual availability on the test subscription. For example, a new service must be available on the server and usable within the defined resource and permission limits.

Only after testing should you intentionally apply the desired changes to the production plan. A test subscription on the shared production plan would not protect the other assigned subscriptions from those changes.

When a plan is changed, the assigned subscriptions that are not locked for synchronization are generally updated. However, this does not mean that every setting on every existing object is overwritten: Special limits apply to some properties, and customer permissions can exclude individual values from central synchronization. Therefore, check the specific property rather than just the plan status.

AI-generated illustration of three paper strips with a contrasting variation and control plates
AI-generated illustration: Individual discrepancies should be reviewed separately before resynchronizing.

A subscription customized through Customize can Locked and will then be exempt from subsequent plan changes. Before unlocking, document the deviating values and the reason for them. Then read the corresponding dialog box and check which adjustments trigger the confirmation, so that an intended special provision is not inadvertently lost.

After the rollout, check the statuses and the affected settings again. In particular, locked and unsynchronized subscriptions require a separate decision: An exception can be intentionally left in place; a conflict, on the other hand, requires an investigation into the cause. Document who is evaluating the discrepancy and, if necessary, coordinating with the customer.

Identifying Synchronization Problems in a Targeted Manner

The displayed status helps narrow down the issue, but it does not answer every question about the configuration. A subscription that is blocked for plan synchronization is different from a subscription whose provisioning fails due to a lack of resources. You should also not confuse an operational block with a synchronization block.

Subscription Status and Initial Diagnosis
ConditionContext and ImpactFirst step in the review process
SynchronizedSynchronizable properties are as specified in the plan; excluded values may differ.Check permissions and the affected property.
LockedPlan synchronization is disabled; individual adjustments remain protected.Document any special adjustments and the reason for the suspension.
UnsyncedIn some cases, the required plans could not be provided.Check for conflicts and available resources or rights.
SuspendedThe subscription is suspended; this is a separate operational status.Check the reason for the operational suspension and evaluate it separately from the synchronization status.

An important exception is Customer Permissions: If a customer is allowed to manage DNS zones or general PHP settings, for example, the relevant values are not overwritten centrally. The subscription may still be considered synchronized. Therefore, if you notice a discrepancy, first check whether it was intentionally allowed by such a permission.

Warning: A conflict dialog is not a "test" button with no consequences. Among other things, Plesk displays planned values and available values; confirming the changes may set settings based on the available resources. Review the differences, assess the implications for the customer, and confirm only if the resulting change is intended.

On a Linux server running Plesk, you can also view subscription settings in read-only mode via the terminal. In the following command, example.com A placeholder for the domain of the subscription being checked. The output supplements the check performed in the user interface; the command is not executed here.

Terminal
plesk bin subscription_settings --info example.com

Manage Exceptions and Capacity

For recurring requests, a single standard plan is usually more straightforward than having many individually managed subscriptions. If a customer only needs additional storage, a Add-on supplement the existing rate plan. If, on the other hand, the combination of resources and entitlements differs permanently for several customers, it is easier to manage a separate plan than to make repeated individual adjustments.

A custom subscription is designed for a deliberately personalized arrangement, but does not require a service plan and cannot use add-on plans. The following also applies to add-ons: Different add-ons can be combined, but the same add-on can only be assigned to a subscription once. These limitations should be taken into account when deciding on the pricing structure.

For each Exception Specify who approves it, why it exists, and when it will be reviewed. In addition to the agreed-upon values, also specify whether the subscription for plan synchronization is disabled. This ensures that, in the event of personnel changes or rate adjustments, it remains clear whether a deviation is intended.

Regularly check the actual resource usage and available server capacity, as well as the reseller’s allocation, if applicable. A value entered in the plan does not automatically reserve the required infrastructure; when a plan is created, Plesk does not fully verify whether all offered resources and services are available. Therefore, plan for growth and operational reserves separately.

A service plan thus standardizes the configuration, but it does not replace monitoring or a performance or availability commitment. If usage and capacity diverge, an operational decision is required—such as allocating additional resources, adjusting the service offering, or coordinating separately with affected customers.

Sources and Current State of Knowledge

Status of the research:

This information is based on the manufacturer's documentation for Plesk Obsidian; the feature set and user interface may vary depending on the version, role, operating system, and installed components. Research date: November 16, 2026.

https://docs.plesk.com/en-US/obsidian/administrator-guide/customers-and-resellers/hosting-plans-and-subscriptions.70623/

https://docs.plesk.com/en-US/obsidian/api-rpc/about-xml-api/reference/managing-service-plans.32891/

https://docs.plesk.com/en-US/obsidian/administrator-guide/appendix-a-properties-of-hosting-plans-and-subscriptions/permissions.65719/

https://docs.plesk.com/en-US/obsidian/reseller-guide/understanding-service-plans-and-subscriptions.64607/

https://docs.plesk.com/en-US/obsidian/administrator-guide/customers-and-resellers/hosting-plans-and-subscriptions/setting-up-addon-plans.70673/

https://docs.plesk.com/en-US/obsidian/administrator-guide/appendix-b-properties-of-reseller-plans-and-subscriptions.65749/

https://docs.plesk.com/en-US/obsidian/administrator-guide/customers-and-resellers/hosting-plans-and-subscriptions/relationship-between-plans-and-subscriptions.65118/

https://docs.plesk.com/en-US/obsidian/administrator-guide/appendix-a-properties-of-hosting-plans-and-subscriptions.70690/

https://docs.plesk.com/en-US/obsidian/administrator-guide/customers-and-resellers/hosting-plans-and-subscriptions/setting-up-hosting-plans.70624/

https://docs.plesk.com/en-US/obsidian/reseller-guide/understanding-service-plans-and-subscriptions/properties-of-hosting-plans-addons-and-subscriptions/hosting-parameters.65720/

https://docs.plesk.com/en-US/obsidian/cli-linux/using-command-line-utilities/subscription_settings-hosting-subscription-settings.37982/

Current articles