Start

GCP

Run your project on Google Cloud, either on infrastructure Spawned manages or in your own GCP project.

Spawned Hosted

The fastest way to start. Spawned runs your project in a GCP project it manages, so you don’t need a Google Cloud account of your own. Pick it as the provisioned option when you create a project. Your cloud costs are included in your Spawned bill, so everything stays in one place. See Billing & Credits.

Bring Your Own Cloud

Connect your own GCP project and Spawned deploys into it. You pay Google directly for the underlying resources, and Spawned bills per component. Choose this when you want to use existing cloud credits, meet compliance requirements, keep direct access to the project, or work alongside resources you already run.

Connect a project

Connect your project under Settings → Clouds. The project must already exist and have a billing account linked, because the required APIs will not enable without one.

  1. Register the project by its ID and pick the region deployments run in. The default is europe-west1.
  2. Run the setup script Spawned generates for you. Paste it into Cloud Shell, or any terminal where gcloud is signed in as someone who can administer the project.
  3. Click Verify connection. Spawned proves the setup works by acting as the deployer identity before the connection activates.

The script creates a dedicated deployer service account inside your project and lets Spawned mint short-lived tokens for it. Everything Spawned does runs as that account, bounded by roles scoped to that project alone. No long-lived credentials are ever shared, and deleting the account severs the integration at any time.

The script is safe to re-run: every step either creates or adopts what already exists. If verification fails right after the script finishes, wait a few minutes and try again, since IAM changes take a moment to propagate.

If your project belongs to a GCP organization that enforces domain-restricted sharing, deployed services cannot be made publicly reachable. The setup script ends with a commented override that lifts this for the project.

Once connected, select the project when you create a project.