Light Cloud Client Workspace Setup (Onboarding)

Light Cloud Client Workspace Setup (Onboarding)

1. 01

   Create the client project in Light Cloud and connect the client's GitHub repository

   Confirm the repo builds a frontend, backend, and database in one project before inviting anyone else. If the client repo has no Postgres dependency, still provision the database so the project matches the delivery template.

2. 02

   Provision the managed Postgres instance and set tier, region, and storage

   Match region to where the client's users sit, since Light Cloud wires encrypted credentials to the application automatically. Record the chosen tier in the client runbook so the monthly hosting line on the retainer invoice is traceable.

3. 03

   Assign the custom domain and verify the branch preview behavior

   Push a test branch and confirm a preview URL appears, then delete the branch and confirm the preview is removed. This is the check that tells you per-branch previews are live for the client's reviewers.

4. 04

   Set container minimum instances to zero on non-production environments

   Scale-to-zero stops billing on idle apps, which is what makes a $5/month Lite plan viable for a low-traffic client site. Leave production always-on only if the client has committed to the Starter plan at $19/month or above.

5. 05

   Add the client's developers as team members and confirm seat count against the plan

   Lite and Starter include 1 team member; extra members on Starter cost $9 each. If the client needs more than one seat, price the retainer against Pro at $49/month rather than absorbing overage.

6. 06

   Connect Claude Code or GitHub Copilot through the MCP server for AI-assisted deploys

   Restrict this to your own delivery team unless the client has asked for it. The MCP integration is an internal velocity tool, not a client-facing feature.

7. 07

   Hand off credentials and document the deployment workflow

   State plainly in the handoff note that client-facing dashboards display Light Cloud branding, because the platform publishes no white-label or multi-tenant agency surfaces. Set that expectation at onboarding, not at the first client login.