Welcome to the new Golem Cloud Docs! 👋


This guide will get you up and running in Golem in minutes.

Install Golem CLI

Golem CLI is a command-line application that allows you to deploy new invincible workers onto Golem.

To install golem-cli you currently need to use cargo, Rust's build tool.

To get cargo on your system, we recommend to use rustup (opens in a new tab):

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
rustup install stable
rustup default stable

Then you can install golem-cli with the following command:

cargo install golem-cli

If you want to try out the hosted version of Golem you can register for the Developer Mode preview (opens in a new tab). You will then be provided with a link to download the Golem Cloud CLI.

You need to create an account and authenticate yourself before using any Golem Cloud commands. This is easy to do with Github OAuth2. Lets do it right now by using the following command:

golem-cloud-cli account get

Once you authenticate, Golem Cloud CLI will cache an API token in a local directory named $HOME/.golem. This token will allow you to use Golem Cloud CLI without further authentication.

We will use golem-cli as opposed to golem-cloud-cli in all examples unless they are specific to Golem Cloud, but golem-cloud-cli supports all commands supported by golem-cli.

Setting up Golem

To use the open source version of Golem you need to deploy it in your own infrastructure.

To get started we recommend using the Docker Compose file from the Golem Docker examples (opens in a new tab). You will need to have Docker (opens in a new tab) and Docker Compose (opens in a new tab) installed on your system.

Once you have Docker Compose installed, you can make use of docker-compose file in Golem repository to spin up Golem.

# Download an example docker-compose file along with .env file that has a few common configurations
curl -O https://raw.githubusercontent.com/golemcloud/golem/main/docker-examples/docker-compose-sqlite.yaml -O  https://raw.githubusercontent.com/golemcloud/golem/main/docker-examples/.env
# Start Golem with backend storage as SQLite and Redis
docker-compose -f docker-compose-sqlite.yaml up

Note that, here we are making use of an example docker-compose file. You may need to modify it to suit your needs, or refer other examples in Golem repository (opens in a new tab). That said, the example docker-compose file along with .env file should be enough to get you started.

If you are running into any port conflicts you can modify the .env file that was downloaded as part of the above curl command.

If you are using the hosted version of Golem, you can skip this step.

Building an Example

Golem runs components that are WebAssembly programs. Components are like applications, except they may expose functions that can be called externally.

To deploy to Golem, you must first build a component using any programming language and toolchain that can build WebAssembly components.

To get started quickly, you can use Golem CLI to create a component from an example:

golem-cli new --example rust-shopping-cart --component-name shopping_cart

This will generate a new shopping_cart directory in the current directory with the example for your component.

To build the newly created component you need some development tools installed. These are collected for each supported guest language on the Building Components page. For the above example, please read the Rust specific instructions to set up cargo-component.

Once you have that, navigate to the shopping_cart, and run:

cargo component build --release

This will write the resulting component to shopping_cart/target/wasm32-wasi/release/shopping_cart.wasm.


The golem-cli new command prints out the necessary steps to build your component exactly as you have to type them - using your custom component and package names and the selected example's language specific tools.

Uploading Your Component

To upload your component to Golem, you can use the component add command. Navigate to shopping_cart/target/wasm32-wasi/release and then do:

golem-cli component add --component-name shopping-cart shopping_cart.wasm

Uploading a component to Golem does not actually execute the component. Instead, it only makes it available for execution to Golem .

Every separate execution of your component is referred to as a worker based on that component.

Create Workers

In Golem, every worker has a unique id, which is arbitrary text that you define. If you don't need a meaningful id for workers, you can generate a UUID.

Once you have chosen a worker id, you can launch the worker either explicitly, or by invoking any function on the worker (for example, a “main” function).

Here, we creating a new worker shopping-cart-1 :

golem-cli worker add \
  --worker-name shopping-cart-1 \
  --component-name shopping-cart

When you add a component you will see some basic information about the component such as its name, unique identifier, version, and size. In addition, you will see a list of exports. These are the public API of your worker and can be used to call it with the CLI or REST API, as we will see below.

Invoking Workers

Thanks to the WebAssembly component model, your Golem applications are not just an executable. Rather, they may export functions that can be called from the outside. Exported functions allow your workers to be given instructions or queried for their state.

Here, we invoke the function initialize_cart on the worker with a single string parameter:

golem-cli worker invoke-and-await \
    --component-name=shopping-cart \
    --worker-name=shopping-cart-1 \
    --function=golem:component/api/initialize-cart \

If a worker of the specified name has not been created, then when you attempt to invoke a function on the worker, it will first be created.

Check the Component interface section to learn about how to figure out the function name and how to encode your parameters in JSON.

Next Steps

In this guide, you have learned how to build and deploy invincible serverless workers on Golem, and seen how you can interact with them as they execute.

Take your next steps with Golem by exploring the following resources:

  • Building Components describes you can use different programming languages for building Golem components
  • Promises are a way to block your program until an external condition fulfills it.
  • The Golem CLI page lists all the commands available on Golem's command line interface
  • Golem can also be controlled using its REST API
  • Read the FAQ page for frequently asked questions