APM, error tracking, and dashboards for modern web apps. Ten-minute setup, transparent flat pricing, and support from engineers who actually use the product. Learn more →
Flake-parts Alternatives
Similar projects and alternatives to flake-parts
-
-
AppSignal
Monitoring that respects your time & budget. APM, error tracking, and dashboards for modern web apps. Ten-minute setup, transparent flat pricing, and support from engineers who actually use the product.
-
-
-
dagger
Automation engine to build, test and ship any codebase. Runs locally, in CI, or directly in the cloud (by dagger)
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
-
-
-
-
-
-
std
A DevOps framework for the SDLC with the power of Nix and Flakes. Good for keeping deadlines! (by divnix)
-
-
npt
Nix Package Tool. A (humble) successor to linux's apt, which makes life easier when using nix as a package manager. (by woile)
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
flake-parts discussion
flake-parts reviews and mentions
-
Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs
There are two kinds of organization happening here that you might not see:
1. All .nix files (besides flake.nix) are flake-parts modules: https://flake.parts/
2. It's not only usable with experimental flakes. Works fine with unflake or trix.
The experimental part of flakes is enabling flake support in the `nix` CLI.
Flakes are also a design pattern in pure Nix syntax that can be evaluated fine without the experimental flag.
If you're curious about this meaningful organization, it's pretty well-documented:
https://denful.dev/
As for the experimental nature of flakes, it's more of a social experiment by now:
https://simonshine.dk/articles/if-flakes-are-experimental-wh...
-
How I Organized over 100 NixOS Modules Without Going Crazy
I settled on a pattern using flake-parts that treats modules like a catalog rather than a tree. Here's the core of my flake.nix:
-
Haskell Project Template with Nix Flakes
haskell-flake -- a recent and modular setup based on flake-parts.
-
Nix is a better Docker image builder than Docker's image builder
There are attempts like
https://flake.parts/
or
https://github.com/nix-community/flakelight
Their aim is to create an ecosystem of reusable Nix libraries. But it is tiny.
-
Nix noob question
You can also just install flakes doing nix profile install . I wrote a tool to make it a bit easier, npt but it's completely optional. Once you install the packages with nix profile. Then in your repos you can use a flake with a devShell and run nix develop. Check https://flake.parts to write your flakes.
-
I'm getting on the hype train. What do you recommend to beginner?
Definitely use flakes from the get-go. It's much more sane. Nix's documentation can be unorganized, but read through it when you can. Modules and other projects tend to have their own documentation as well, like Home Manager and flake-parts
-
Why you don't need flake-utils
That's not a typo, there OP is referring to https://github.com/hercules-ci/flake-parts
-
A note from our sponsor - AppSignal
www.appsignal.com | 9 Aug 2026
Stats
hercules-ci/flake-parts is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of flake-parts is Nix.