Create an app-hosting package that defines the region, instance plan and instance count a customer receives. Each intentionally provisioned service runs one app with one web-service component from its public source.

Create the offering

1. Open Packages → Packages → Add Package.
2. Choose PD DigitalOcean App Platform as the module and select the intended saved DigitalOcean account.
3. Set Region, Plan and Instances in the module options. Review Resource name prefix, optional Project, Client: Redeploy and Client: Change source.
4. Set your package terms and pricing, choose the package group and save.
5. When the offering is ready, add that group to the intended order form under Packages → Order Forms.

Customers supply their public Git repository or Docker Hub image after ordering, from App source on the service’s Information tab. Keep Client: Change source enabled for that intended workflow; do not promise a repository field on this module’s checkout.

Review Hold paid pending services for manual activation and the Provision Paid Pending Services automation task. Leave the hold unticked if your process should activate eligible paid orders automatically, and keep the normal cron running. A paid order can remain pending until the intended activation occurs.

Review the app settings

Choose App Platform regions and plans from this module’s lists. App Platform region names are different from Droplet region codes. The catalogue can be cached or use shipped choices when DigitalOcean cannot be reached, so a listed choice is not a deployment-capacity test for your account.

The module limits instance count to 1–5. Some DigitalOcean plans support only one instance; do not offer a larger count simply because the quantity control allows it. Confirm that the plan and count you intend to sell are supported together.

Project groups the new app in your provider account; it is organisational, not a separate hosting plan or a completed-deployment check. The normal background process attempts that assignment after the app becomes live. Review the selected account and project together.

Review checkout and source collection

Use PD Modules → DigitalOcean App Platform → Products to generate and inspect Region, App plan and Instances choices. Review their visibility, selected values and your own prices in every term or currency you offer before making the package available.

A service without a usable source can show Waiting for source after activation. That is different from a failed provider connection: the customer still needs to submit a public Git repository or public Docker Hub image. The API token stays with the host’s provider connection.

Verify activation and deployment separately

When ready, use your normal authorised provisioning test. A real deployment creates chargeable DigitalOcean resources. Check Clients & Apps, the service page and Activity; keep the normal cron running for deployment progress. A completed order or Ready options label alone does not establish that the app is live.

After the first successful deployment, open the service’s live URL and check the expected application. If an earlier attempt has an uncertain result, reconcile the existing service and provider app before another create action. Keep tokens and customer data out of shared screenshots.

See the PD DigitalOcean App Platform Blesta guide for related setup, or explore PD DigitalOcean App Platform.