AI Builder
Connect and supervise the BigCloudy AI Builder integration.
1Overview
AI Builder is an optional panel module that connects verified hosting inventory with the BigCloudy website-building service.
2Before you begin
Administrator actions can affect multiple customer accounts and server services. This is an advanced task; schedule it carefully and keep a rollback path.
3Step-by-step workflow
Open AI Builder, verify module and agent status, confirm the server inventory connection, then use the displayed deployment controls for eligible hosting accounts. Review activity and errors before re-enrolling an agent.
- Open AI Builder and inspect its connection, module, or server-agent status.
- Confirm the destination server and the account/domain that should receive a generated website.
- Configure the integration with a scoped API token rather than a shared root or panel password.
- Review whether the project is static HTML or a supported application requiring a runtime.
- Keep deployment files inside the selected hosting account and its approved website or application root.
- Review generated files and environment settings before making the new site public.
- Deploy through the approved integration and read its status and log.
- Open the public URL, test its main pages, and retain a previous deployment for recovery.
4Practical example
Example: a generated static HTML site can be deployed into the selected customer document root. A generated Node.js or Python application also needs its runtime, dependencies, start configuration, and managed process.
5Verify the result
Validate the outcome from the affected account or an independent client connection, not only from the administrator screen.
- Confirm the intended server shows Live or connected.
- Review the latest integration message before retrying a failed enrollment.
6Common problems and what to check
The integration is disconnected: check the module/agent state and token settings before retrying a deployment.
Account creation is denied: review provisioning scope and package limits.
A deployed site is blank: check its output directory, entry file, build result, and domain routing.
7Security, impact, and rollback
Keep the module and its server agent from a verified source. Do not expose enrollment credentials or bypass the account inventory checks that protect deployment ownership.