Jaws Deploy ships with a built-in package store. It's a feed that lives inside the workspace - no separate server to operate, no separate credentials, no extra cost. Push packages to it directly from CI.
Pushing packages
Three common ways: the PowerShell SDK, the REST API, or the NuGet protocol. CI tools that already know how to push NuGet packages can target the built-in feed as a NuGet source with no special configuration.
From a CI build step after producing the package
The API key needs feeds.push permission on the workspace.
Connect-JawsDeploy -Url "https://app.jawsdeploy.net" -ApiKey $env:JAWS_API_KEY
Push-JawsDeployPackage `
-Workspace "default" `
-Feed "built-in" `
-Path ".\\out\\Checkout.Web.2026.5.17.zip"