# Deploy Aembit Edge with GitLab Jobs

> How to deploy Aembit Edge Components in a CI/CD environment with GitLab Jobs

Aembit provides many different deployment options you can use to deploy Aembit Edge Components in your environment. Each of these options provides similar features and functionality; however, the steps for each of these options are specific to the deployment option you select.

The following pages provide information about using Aembit Edge in [GitLab Jobs](https://docs.gitlab.com/ee/ci/jobs/):

* [GitLab CI/CD Component](/user-guide/deploy-install/ci-cd/gitlab/gitlab-jobs-component) - Use the Aembit Edge GitLab CI/CD component
* [Aembit CLI](/user-guide/deploy-install/ci-cd/gitlab/gitlab-jobs-cli) - Use the CLI with GitLab CI/CD jobs

> **When to use the Component vs CLI**
>
> Most users should use the Aembit Edge GitLab CI/CD Component, but some specific use cases may require the Aembit CLI directly.
>
> Use the **[GitLab CI/CD Component](/user-guide/deploy-install/ci-cd/gitlab/gitlab-jobs-component)** when you:
>
> * Want automatic CLI download and OIDC token configuration without manual setup steps
> * Want simplified job configuration with built-in `allow-failure`, `stage`, and `job-name` options
> * Prefer a streamlined, declarative approach that integrates natively with GitLab CI/CD pipelines
>
> Use the **[Aembit Edge CLI](/user-guide/deploy-install/ci-cd/gitlab/gitlab-jobs-cli)** when you:
>
> * Need advanced CLI options or flags not exposed through the component interface
> * Want to combine the CLI with other tools in custom scripts or have specific error handling requirements