GCP
With the release of version 0.2 of dstack, configuring a GCP as a remote is now possible. All the features that were previously available for AWS except [real-time artifacts](https://docs.dstack.ai/basics/artifacts/#real-time-artifacts) are now available for GCP as well.
To use GCP with `dstack`, you will require a service account.
<img src="https://user-images.githubusercontent.com/54148038/223904624-eb246dbc-b7ea-491c-99a1-72716bd2326d.png" width="600"/>
For more details on how to configure GCP, refer to the [documentation](https://docs.dstack.ai).
Once you have created a service account, proceed to execute the dstack config command. After that, you're good to go! Use the `--remote` flag with the `dstack run` command to execute workflows in GCP, and `dstack` will automatically create and destroy cloud instances based on resource requirements, including cost strategies like using spot instances.
<img src="https://user-images.githubusercontent.com/54148038/224349997-2a8cf743-1a10-4eec-895a-0f2a779ee89e.png" width="600"/>