Hosted Quickstart

A hosted software bundle combines the CMS license with compatible hosting. The deployment pipeline prepares the application and database for you. You still need to confirm the domain, secure the CMS account, and configure your organization's settings and integrations.

1. Complete your purchase

Follow Purchasing BRAD. Confirm that the cart includes software and compatible hosting, and that the installation hostname is correct. If using an existing domain, keep access to its DNS provider.

2. Check provisioning progress

After payment, open Services and select the hosting service. Review any deployment status or progress available there. The process validates the purchase and release, prepares hosting and PostgreSQL, uploads the CMS release, configures its environment, starts the app, and configures the domain.

Completion time varies with the hosting node, application build, DNS, and certificate issuance. Closing a progress view does not cancel a running deployment, but an interrupted server process can affect it. Use the service status and support updates to confirm completion.

The installation can finish before a transferred domain or new DNS record becomes usable. Application deployment, DNS propagation, and domain transfer are separate processes.

3. Find your CMS access

Open the service details and look for Your CMS. When the deployment has recorded credentials, this section shows the CMS administrator email, initial password, and an Open CMS link.

Use those credentials on your CMS domain. Your portal password and any hosting-panel password are separate. Change the initial CMS password after the first sign-in and enable two-factor authentication where appropriate.

If the CMS access section has not appeared, confirm that deployment has completed. If credentials or the URL remain missing, open a support ticket with the hosting service reference. Do not assume that a receipt email supplies a magic sign-in link.

4. Connect your domain

Use the hostname and destination supplied by the hosting service. If your DNS remains with another provider, edit records there. Preserve existing email and other service records when making changes.

Test the public hostname over HTTPS. If the host supplies a temporary application URL, use it for checking deployment progress, and confirm the final hostname before regular use. See domains and DNS.

5. Configure the organization

Work through CMS setup: company details, outgoing mail, file storage, modules, and staff access. Test any payment gateway with its test environment before collecting customer payments.

Hosted provisioning does not automatically make every external integration ready, and a running app does not establish a backup policy. Confirm backup and update responsibilities with your hosting service before launch.

If deployment fails

Record the failed step and error, then contact Support Tickets. Include the service, domain, payment time, and whether anything already became accessible. Staff can inspect the deployment record and assess a retry.

A failed deployment does not automatically refund a settled payment. Avoid placing a duplicate order to restart provisioning; request help with the existing service instead.