Skip to content
Artifact Repository Manager
Download

Features

AI-native catalogue. CI, agents, and operators.

Built-in MCP for chat agents. Machine publish with scoped grants. A fixed promote lane. Native APT, pacman, NuGet, MSI, MSIX, and DMG feeds for the software you ship. artifactd itself runs on Linux.

Inside artifactd

Your releases. The whole picture.

Explore the workspace that connects your packages, your teams, and the people using your software.

01 / The dashboard

Know what shipped. See what’s happening.

Start with a clear view of your repository: uploads, downloads, published artifacts, and client feedback. Channel trends and recent publications put the next investigation one click away.

  • Repository activity in one view
  • Published artifacts and feedback by channel
  • Direct links to the underlying catalogue and audit
Explore the documentation →
artifactd dashboard showing repository metrics, channel trends and recent publications View full screen ↗
Actual artifactd interface · illustrative demo data

02 / Package promotion

From a new build to the right audience.

Keep versions, formats, and publication channels together. Inspect an artifact and choose where it is published as it moves through alpha, beta, testing, canary, and release.

  • One catalogue for APT, Arch, MSI, MSIX, DMG, and NuGet
  • Visible version and channel context
  • Promotion for operators, CI, and MCP agents
Explore the documentation →
artifactd artifacts catalogue with the selected build and publication controls View full screen ↗
Actual artifactd interface · illustrative demo data

03 / Users & permissions

Give every team the access it needs.

Organize users into groups, then scope grants to the package, channel, and action. Let CI publish testing builds and production clients pull releases with credentials you can rotate.

  • Users and groups in a dedicated workspace
  • Separate pull and publish permissions
  • Package and channel scopes visible at a glance
Explore access control →
artifactd grants table showing group, package, channel, pull and publish permissions View full screen ↗
Actual artifactd interface · illustrative demo data
See the users workspace
artifactd users workspace with demo users and group membership View full screen ↗
Actual artifactd interface · illustrative demo data

04 / Client Feedback

The release is only the beginning.

Turn what happens after installation into input for your next development cycle. Investigate crashes, errors, bug reports, and feature requests against the affected version, then bring that evidence into AI-assisted fixes and feature work.

  • Filter reports by kind, period, package, or channel
  • Inspect exception details and client context
  • Investigate repeated issues in an artifact’s Top problems
Explore the documentation →
artifactd Client Feedback with reports tied to a package version and report details View full screen ↗
Actual artifactd interface · illustrative demo data

Put your next release in focus.

Self-host your catalogue. Connect your pipeline. Stay close to your users.

Get artifactd →

Client Feedback

Ship the build. Hear back from your users.

Crashes, errors, bug reports, and feature requests in one place. Every report is linked to the released package and version, so you can connect what users experience to what you shipped.

  • Crash reports

    Capture unhandled exceptions from client apps, with exception details and stack traces to investigate failures in the field.

  • Error reports

    Report selected, handled failures with their operation and exception context, even when the application keeps running.

  • Bug reports & bugfix requests

    Let users describe what went wrong with a title and description, so requests for a fix stay connected to the affected build.

  • Feature requests

    Collect ideas for new capabilities directly from your client apps, with the user’s title and description alongside the version they use.

From client app to the affected release

Integrate the Client Feedback SDK (.NET, Python, Rust, Node.js, or PHP) into your apps to queue and send feedback. In Client Feedback, filter by kind, period, package, or channel and inspect individual reports. Open the artifact’s Top problems to see repeated reports grouped with occurrence counts.

Feedback keeps its package and version context even after the release binary is removed. Bring this release-specific evidence into AI-assisted development: investigate failures, prioritize user requests, and verify the next build. Your AI agent can use built-in MCP to inspect the catalogue and promote artifacts; individual feedback reports are currently available in the operator UI.

Explore Client Feedback integration → Get the SDKs on GitHub ↗

Formats

Package formats the catalogue can host

artifactd is a Linux server. MSI, MSIX and DMG are formats it stores and serves for your Windows and macOS applications; the product itself is not distributed in them.

  • deb

    APT

    Debian and Ubuntu

    Signed indices and pool downloads. Suites follow the distribution, with channel suffixes such as trixie-testing.

  • pkg.tar.zst

    Arch

    pacman

    Repository names match the channel. Clients install with the usual pacman drop-in and HTTP Basic pull token.

  • msi

    Windows MSI

    Windows installers

    Latest JSON plus pool files per architecture. CI uploads the installer; clients fetch the current published build.

  • msix

    Windows MSIX

    Windows app packages

    Same flow as MSI with its own latest route and pool. MSI and MSIX stay separate formats, so one package can publish both.

  • dmg

    macOS DMG

    macOS disk images

    Latest JSON plus pool files for Intel, Apple Silicon, or universal builds. CI uploads the image; clients fetch the current published build.

  • nupkg

    NuGet

    restore feeds

    V3 restore per channel. One grant covers the software on that channel the same way it covers deb, Arch, and the installer formats.

More ecosystems

More package formats on the horizon

These formats are not supported in the current release. They are listed for visibility into future ecosystem coverage; availability and release dates are not committed.

  • Not yet supported

    npm

    Modules, integrations, and components distributed through npm

  • Not yet supported

    OCI

    Container images and OCI artifacts

  • Not yet supported

    RPM

    Fedora, RHEL, and compatible distributions

  • Not yet supported

    PyPI

    Packages distributed through the PyPI ecosystem

  • Not yet supported

    Maven

    Libraries and build artifacts distributed through Maven repositories

Pipeline

Promote along a fixed lane

CI and AI agents upload onto a named channel. Promote sets publication. Unpublish clears it. APT suite names follow the distribution plus an optional channel suffix.

  1. Alpha
  2. Beta
  3. Testing
  4. Canary
  5. Release

Capabilities

What ships with the operator UI

  • Six package formats, one catalogue

    Debian APT, Arch pacman, NuGet, and the Windows MSI, MSIX and macOS DMG installers of your own applications live as packages and versioned artifacts in the same catalogue. artifactd itself runs on Linux. Grants and channels apply once — not once per format.

  • AI-native: CI publish plus built-in MCP

    Use Client Feedback to guide AI-assisted fixes and feature work. Through built-in MCP, your agent can inspect the current catalogue and promote the resulting build; CI publishes with scoped Bearer tokens. Individual feedback reports are currently inspected in the operator UI.

  • Release pipeline you can see

    Upload requires a channel. Promote along alpha, beta, testing, canary, and release. Unpublish clears publication. Operators, CI, and chat agents watch the same lane instead of guessing which feed is current.

  • Visibility of what is in the repo

    Packages and Artifacts list identity, format, distribution, architecture, channel, and status. Filter unpublished. Home shows uploads, downloads, published-by-channel, and recent publications.

  • Authorizations that match the job

    Groups hold grants. Users inherit the union. Each grant names a package or Any, a channel or Any, and Allow pull, Allow publish, or Allow creating new packages — sized for a CI identity or an agent role.

  • Separate pull and publish credentials

    Clients pull with HTTP Basic. CI and agents publish with a Bearer token shown once and rotatable. The admin token cannot upload. User detail copies APT, Arch, and NuGet snippets.

  • Retention and integrity

    Named policies cap unpinned versions, age, and size. Pin keeps a build. Integrity scan marks missing blobs as error so the catalogue does not pretend the file is there.

  • Audit and Client Feedback

    Audit uploads and downloads. Open Client Feedback for crashes, curated errors, bugfix requests, and feature requests from your apps, all linked to the artifact version that shipped.

  • Client Feedback SDK

    Add the Client Feedback SDK (.NET, Python, Rust, Node.js, or PHP) to apps that publish through the catalogue. It queues crashes, curated errors, bugfix requests, and feature requests locally, uploads them with the pull identity, and binds each report to the released artifact by package name and version.

  • Self-hosted Debian package

    Install artifactd from APT, set the env file, and run the service. Dataplane serves clients; management serves the operator UI and API on a separate listen address.