# Built-in Package Store

Source: https://www.jawsdeploy.net/guides/built-in-package-store

Useful for teams that do not already have a NuGet, Artifactory, or S3 setup they want to keep.

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"
```

> **// When the built-in feed is the right call - Teams shipping fewer than ~50 artefact versions per day rarely need anything else.**
> 
> The built-in feed scales well past that - the question is more about whether you already have an artefact server you'd be operating in parallel for no benefit. If you don't, use the built-in. If you do, connect the existing one as an external feed.