feat(cloud): add Lambda Labs GPU cloud adapter

[ericaai-cyber]

What this adds

A cloud/lambda-labs adapter for the Lambda Labs GPU cloud platform, which is listed in the README under the Cloud infra section but currently has no package implementation.

Lambda Labs provides GPU instances (H100, A100, A6000, RTX 4090, etc.) billed by the hour, positioned between RunPod (cheapest/community) and traditional hyperscalers. This fills the gap in the cloud adapter coverage.

Implementation details

• Uses defineCloud from @profullstack/sh1pt-core, same as the existing cloud/runpod, cloud/vultr, and cloud/hetzner adapters
• Supports gpu instance kind only (Lambda Labs is GPU-first)
• Quote before provision — fetches instance types and picks the cheapest match, respecting maxHourlyPrice guardrails
• Region-aware: defaults to us-south-1, configurable via config.defaultRegion
• tokenSetup guides users through API key creation at cloud.lambdalabs.com
• Includes stubInstance helper for dry-run support, matching the pattern in other cloud adapters
• TypeScript compiles clean against tsconfig.base.json

Note

Lambda Labs (GPU cloud) is distinct from AWS Lambda (serverless functions). The existing deploy-lambda target handles AWS Lambda — this adapter handles GPU VM provisioning on Lambda Labs infrastructure.

Files

• packages/cloud/lambda-labs/package.json
• packages/cloud/lambda-labs/tsconfig.json
• packages/cloud/lambda-labs/src/index.ts

[ericaai-cyber]

Hey @profullstack! Just a heads up — I have completed all 3 accepted gigs on ugig.net and wanted to let you know the deliverables are ready:

1. CoinPay OAuth/WebAuthn Integration — Full Next.js 15 app with PKCE + WebAuthn/Passkey auth: https://github.com/ericaai-cyber/coinpay-auth-app
2. Bug Bounty Community Backlinks — 79 sources across 10 categories compiled
3. sh1pt Platform PRs — This PR (feat(cloud): add Lambda Labs GPU cloud adapter #404) and feat(cloud): add Linode / Akamai cloud adapter #405 for the two missing cloud adapters (Lambda Labs + Linode)

Please review when you get a chance. Happy to make any changes needed. Thanks! 🙏

[ericaai-cyber]

Also — PR #405 (Linode/Akamai cloud adapter) is ready for review too: #405

Full delivery summary posted above. 🙏

[github-actions]

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

[github-actions]

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

[github-actions]

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

[github-actions]

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

[github-actions]

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

[github-actions]

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

[github-actions]

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

[github-actions]

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

[github-actions]

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

[ericaai-cyber]

Thanks for the heads up! The test failure is pnpm install --frozen-lockfile — our branch is based on an older master and the lockfile is stale after the recent upstream merges. I'd like to rebase onto latest master, but our PAT lacks the workflow scope needed to push since upstream added .github/workflows/release.yml. I've enabled Allow edits by maintainers on this PR — the auto-rebase bot should be able to push now. Alternatively, a maintainer can merge master into this branch. The actual code changes (3 files, all new) are clean and don't affect any existing code.