# Deploying workloads

When workload are [Enabled](/platform/1.14/workloads/getting-started/enable.md) on your account, a `Workloads` tab will show up in the top navigation section. Selecting that will take you to an overview of your manage workloads.

![Workloads](/assets/images/empty-list-ffd328dc8566384e910fadaaa2c8a24c.png)

The UI will walk you through all the options you need to deploy a workload. To get started, click the `Deploy Workload` button.

The first option you will be presented with is the type of workload you want to deploy - a `Container` or `Function`. With both *types* you have the option of selecting a Cloud Provider: `AWS`, `Azure`, or `GCP` and a region in the `US`, `Europe` or `Asia`. These cloud providers and regions are the same as `NGS` and your workload will run alongside the global super cluster.

![Deploy](/assets/images/deploy-b752eb430c3af4bf31c5abcc6d9e7224.png)

## Containers

For now any containers must be hosted on a public registry. You can specify typical container options like the entrypoint, command and runtime via the `Advanced` Options.

![Container](/assets/images/container-b7ac3cbfab71ef7381e414a5b77a2954.png)

## Functions

JavaScript functions will execute in a Deno isolate and are triggered when messages come over a specific subject:

![Function](/assets/images/function-ba5ae4d999de7a3d86dee4c067622157.png)
