nFPM

nFPM is a Go-based package builder for developers shipping software to Linux distributions or Windows. It is best suited to command-line and Go build workflows; its broad format support is useful, but MSIX needs caution.

Overview

nFPM creates DEB, RPM, APK, IPK, Arch Linux, and MSIX packages from a YAML configuration. That makes it a focused option for developers who need distribution packages without introducing a graphical packaging workflow. The same configuration can cover metadata, files, dependencies, scripts, and format-specific overrides, so a project can accommodate target-specific differences while keeping common package details together.

It runs as a standalone binary without external runtime dependencies and can also be imported as a Go library. That is a practical advantage for build environments that should avoid dependencies such as Ruby and tar, and for projects that want packaging logic in Go code. The trade-off is a configuration-driven approach rather than a visual editor.

Key features

Multiple output formats

nFPM covers six package families, including several Linux formats and Windows MSIX. Shared configuration is useful when releases need more than one package type, while format-specific overrides help address differences among targets. MSIX is the exception to treat carefully: GoReleaser describes that support as experimental and says symlinks are skipped.

CLI, Go library, and release workflows

Use nFPM from the command line or call it as a Go library. GoReleaser can use it to generate and publish Linux packages and Windows MSIX packages, which gives teams already using that release tool a way to incorporate packaging into their workflow.

Installation and artifact checks

Installation options include package managers, prebuilt archives, Docker, Go install, and building from source. Documented package-manager choices include Homebrew, Scoop, APT, Yum, Winget, and NPM. Release artifacts are checksummed, and the checksum is signed with cosign; Docker images are also signed with cosign. These checks are useful for users who want verification steps when obtaining the tool or its container image.

Pricing

nFPM: free. The free plan has no paid tiers or stated usage limits, making it suitable for individuals and teams that want package creation without a subscription. The project is licensed under MIT. No seat count or renewal terms are stated.

Platforms

nFPM targets Linux, macOS, and Windows, and its package outputs include DEB, RPM, APK, IPK, Arch Linux, and MSIX. It also has web listed among its platforms, but the project is described as a command-line tool and Go library rather than a web-based packaging service.

Who it's for

Choose nFPM if you are a developer or release team that wants package creation in a build pipeline, needs several Linux package formats, or wants to invoke packaging from Go. Its lack of external runtime dependencies is especially relevant when you want to avoid installing Ruby and tar for packaging. It is less suitable for users who prefer a graphical installer-authoring workflow, or whose Windows release depends on MSIX behavior that cannot tolerate the documented experimental status or skipped symlinks.

Pros and cons

• Pro: One YAML configuration can define metadata, files, dependencies, scripts, and format-specific overrides, which helps manage releases for multiple package types.
• Pro: A standalone binary with no external runtime dependencies suits lean build environments.
• Pro: CLI and Go library use give teams more than one way to fit packaging into their workflow.
• Con: Configuration is the core workflow, so it is not a visual packaging tool.
• Con: MSIX support is experimental, and symlinks are skipped, limiting confidence for Windows packages that rely on them.

Alternatives

• Software Packaging Tools is the broader directory to consult when you want to compare packaging options beyond nFPM.
• Tauri Bundler is a free open-source Rust library for wrapping Rust executables in OS-specific app bundles; choose it when that Rust-oriented bundling model fits better, while noting its public API stability is not strictly SemVer.
• Electron Forge is a free alternative for teams packaging Electron applications across Linux, macOS, and Windows.
• makeself creates self-extracting archives for Unix-compatible systems under GPL version 2 and above; choose it when that archive format is the goal rather than distribution packages.
• electron-builder is a free alternative for packaging across Linux, macOS, and Windows.
• electron-packager is a free open-source Node.js library and CLI for Linux, macOS, and Windows; choose it if that ecosystem fits, provided Node.js 22.12.0 or higher is acceptable.
• InstallAware has a free Visual Studio edition for commercial use; choose it if Visual Studio is part of your setup.
• IzPack is a free Apache License 2.0 alternative for Linux, macOS, Windows, and self-hosted use.
• NSIS is free for any use, supports installers up to 2GB, and produces installers that run on Windows; consider it when Windows installers are the target.

Verdict

nFPM is a strong choice for developers who need multiple Linux package formats from a no-dependency binary, or want package creation available as Go code. Its free MIT-licensed offering and flexible integration options make it a practical build-workflow tool. Look elsewhere if you need a graphical authoring experience or dependable MSIX support without the experimental status and symlink limitation.