Deploy a monorepo end to end

Create the project and analyze itCopy Anchor Link

Choose New project and paste the GitHub URL. Or from the terminal:

loomctl projects create "Acme shop" --repo acme/shop
loomctl analyze acme-shop

When it finishes you get a line like "found 4 services (3 deployable), 2 packages and 1 resources at 3f2c1a9" (your numbers will differ). In the dashboard, open the graph and check each service and database against the files it points at. A resource found only from a driver in a dependency list is marked to confirm.

If Loomplane found something you don't deploy (a demo app, say), leave it out of the manifest. If it found a resource you don't use, list its kind under ignore.resources so plans stop asking.

Draft and edit the manifestCopy Anchor Link

loomctl manifest acme-shop --draft > loomplane.yaml

Edit it so the web app runs on Vercel and the API and database run on Google Cloud:

version: 1

defaults:
  provider: cloud-run
  region: us-central1

services:
  api:
    source: go:services/api
    needs: [db]
    scale: { min: 1, max: 5 }
    size: { cpu: 1, memory: 512 }
  web:
    source: apps/web
    provider: vercel
    needs: [api]
    environments:
      preview:
        enabled: false

resources:
  db:
    kind: postgres
    provider: cloud-sql
    version: "17"

web needs api, so it gets API_URL. The API is public here, which a Vercel app on another cloud needs, because a private Cloud Run service only takes calls from the project's own services. api needs db, so it gets DATABASE_URL through Secret Manager. If the Dockerfile copies files from across the repository, add build: { context: . } to the service.

Save it:

loomctl manifest save acme-shop -f loomplane.yaml

Connect the cloudsCopy Anchor Link

Under Integrations, add the Vercel token and the Google Cloud key. If a check says permissions are missing, grant them and check again. Then confirm each environment uses the account you meant. With one ready account per cloud, Loomplane picks it for you.

Add variablesCopy Anchor Link

Set anything your services read that Loomplane doesn't generate:

loomctl vars set acme-shop LOG_LEVEL=info --env production
loomctl vars set acme-shop STRIPE_KEY=- --secret --env production --service svc:api:go:services/api

The service ID comes from the graph. See Variables and secrets.

Plan the environmentCopy Anchor Link

loomctl plan acme-shop --env production

Read it from the top. Check the actions are only the ones you expect (a database, an API, a web app), that each sits on the provider you chose, and that no problems are listed. Read the warnings too. A service without a port falls back to 8080 with a warning, and you can fix that in the manifest.

Approve and watchCopy Anchor Link

An admin approves:

loomctl approve <plan-id>

approve follows the deployment step by step and exits nonzero if it fails. Cloud SQL can take several minutes. If a step fails, fix the cause (often a missing permission) and run loomctl retry <deployment-id>. It resumes from the failed step.

loomctl status acme-shop

shows what runs where, with addresses, and flags any drift.

Change and redeployCopy Anchor Link

Push to the repository. If you've set up the GitHub App's webhook, Loomplane re-analyzes on its own. Otherwise run loomctl analyze. Then plan and approve again. To move only one repository in a multi-repository project, plan with --scope web.