Standalone releases control the deployment of a single project or package. They are provided to simplify release management when releasing only one item, which may be applicable for emergency releases or it may be part of normal operating mode for some projectsto align to feature-driven development agile methodologies.
...
Standalone releases are linked directly to a project. Due to this, standalone releases can not be viewed within the standard release folder structure. Instead, to view existing standalone releases for a project, navigate to the Releases tab within the project.
...
Standalone releases can be automatically created when submitting a build request for a project, which is the recommended approach. This can be done performed by selecting Create new Standalone Release from the release dropdown in a the build request popupform.
...
Specify a release name and pipeline. After submitting the build request, a new standalone release will be created and the project/package will be added as content. Once the build completes successfully, a snapshot will be automatically initiated for the new standalone release.
...
Along with all other releases, standalone releases can be “Promoted” to other releases during a snapshot execution. Content of the standalone release can be added to other releases for group deployments to higher environments by using the Promote Step in the associated pipeline. This enables a feature-driven development agile methodology. That is, manage individual features through their own independent release lifecycle, each promoting to the master delivery release if/when they are approved for delivery.
For more information, viewsee: