Catalog and Infrastructure

The customer-facing catalog must correspond to real prices, license entitlements, and infrastructure that can fulfill a paid purchase. Prepare those connections before making a product available.

Product groups and pricing

Open Catalog → Product Groups, then Products. Organize related products and review each product's type, visibility, description, billing cycles, prices, setup fees where applicable, and configurable options.

Software and hosting products have different fulfillment roles. A hosted CMS bundle needs both the license service and a compatible hosting service linked by the purchase flow. Domain pricing is managed separately under TLDs.

Check the public configurator after catalog edits. Marketing visibility alone does not grant module access or establish a purchasable price.

Module options and entitlement

Paid module entitlement is resolved from the purchased service's selected configurable options in a group named Modules. The issuer derives stable module slugs from the option names and sends them in the license response.

Ensure those identifiers match the actual CMS module slugs. Renaming an option can change the derived slug and break entitlement. Coordinate a new paid module across the portal catalog and CMS rather than adding an unrelated marketing label.

A manually issued license without a linked service does not automatically receive paid module entitlements. Review the linked service and selected options when investigating a missing module.

Hosting servers and groups

Open Infrastructure → Servers. Create the server group and provisioning node needed by the hosting product. Select the correct provisioning module and supply its connection fields, status, capacity, and default plan. Use the available connection test before assigning customer traffic.

Credentials and node configuration belong in the office database-backed records. Plesk environment values are a fallback, not a substitute for a managed server inventory.

The current managed BRAD CMS deployment pipeline uses Berth. Ordinary provisioning integrations also include Plesk, but a Plesk-only node is not a valid target for the current managed CMS pipeline.

For Berth, review:

• Panel URL and Admin API Key.
• Default Plan Slug, or the plan selected by the service configuration.
• The node's active status and assigned server group.
• Capacity and access to application, PostgreSQL, and domain provisioning.

Assign the hosting product to a group containing an active compatible node. A product without a server group, a group without an active Berth server, or a missing plan slug will fail managed deployment.

Releases required for deployment

Before offering managed installation, publish a complete CMS release for the linked license product under Licensing → Releases. The pipeline needs that archive on the platform server.

The current uploader checks ZIP structure and a 200 MiB upload ceiling. Publishing an arbitrary URL or incomplete source archive is not enough for managed deployment. See release publishing.

Registrar and TLD setup

Open Infrastructure → Registrars to configure the supported registrar account and default selection. Review connection results and required account settings.

Under Catalog → TLDs, configure extensions and supported registration, transfer, and renewal pricing. Confirm the public domain-search and checkout behavior matches what the registrar can fulfill.

Treat domain registration and transfer as independent from CMS deployment. Accurate registrant contact details and required verification must be handled even if the application is already running.

Validate a complete product

Use a controlled test account and the intended payment environment to purchase the configured bundle. Confirm the order, settled invoice, services, license key, module entitlements, release download, hosting resources, and CMS deployment.

Check the final CMS public URL, initial credentials, and domain status separately. Record what succeeds and what requires manual intervention before enabling the offer for customers.