# Manage bootstrap packages with GitOps
Bootstrap packages let you install custom software during device enrollment. This guide shows you how to manage them through GitOps using Fleet's API.
> **Note:** Each fleet needs its own bootstrap package. Fleets can't share bootstrap packages.
## Prerequisites
Before you start, you'll need:
- A Fleet GitOps setup with an API-only user account
- Access to Fleet's API endpoints
- A bootstrap package ready to upload
## Upload the bootstrap package
First, upload your bootstrap package to each fleet that needs it.
You can use either:
- The Fleet UI to upload the package manually
- The [Create bootstrap package](https://fleetdm.com/docs/rest-api/rest-api#create-bootstrap-package) API endpoint to upload programmatically
Repeat this step for every fleet that needs the package.
## Get the bootstrap package token
After uploading, retrieve the unique token for each fleet's bootstrap package.
Use the [Get bootstrap package metadata](https://fleetdm.com/docs/rest-api/rest-api#get-bootstrap-package-metadata) API endpoint. The response includes the token you'll need for the next step.
## Configure your GitOps fleet file
In each fleet's YAML configuration file, add the `bootstrap_package` field with the download URL:
```yaml
bootstrap_package: "https://your-fleet-instance.com/api/v1/fleet/bootstrap?token=your-token-here"
```
Replace `your-fleet-instance.com` with your Fleet instance domain and `your-token-here` with the token from the previous step.
## More information
Learn more about bootstrap packages and setup experiences in the [setup experience guide](https://fleetdm.com/guides/setup-experience#bootstrap-package).