# Garnix Blog: garnix modules

**URL:** https://discourse.nixos.org/t/garnix-blog-garnix-modules/60992
**Category:** Announcements
**Created:** [February 28, 2025, 1:09pm UTC](https://discourse.nixos.org/t/garnix-blog-garnix-modules/60992 "2025-02-28T13:09:33Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![jkarni](https://discourse.nixos.org/user_avatar/discourse.nixos.org/jkarni/32/6049_2.png) [@jkarni](https://discourse.nixos.org/u/jkarni)
#### Post date: [February 28, 2025, 1:09pm UTC](https://discourse.nixos.org/t/garnix-blog-garnix-modules/60992/1 "2025-02-28T13:09:33Z")

</div>

We are releasing [garnix modules](https://garnix.io/blog/garnix-modules) today.

If you [try it out](https://garnix.io/modules), you’ll see that on the surface it feels a lot like PaaSs such as Render, Railway, and [Fly.io](http://Fly.io). You pick a stack and a repo, give some basic details about it, and garnix builds and tests your software, and optionally spins up your servers.

But unlike those other services, it has a lot of the benefits we know from Nix, such as great caching, easy local reproducibility, a ton of packages, and easy rollbacks. That’s because under the hood, it _is_ Nix. More specifically, it’s a module system (like NixOS modules) that provides options for various stacks; but unlike existing module systems, it’s designed to work well with HTML forms. So you can provide all the arguments without touching Nix files. In the end, we can generate a pull-request to you repo that captures the choices you made into a flake file, so the configuration is in version control.

Here’s a [short video](https://www.loom.com/share/cec660df2bf4416e9c53fce516974593) demoing it:[![](https://cdn.loom.com/sessions/thumbnails/cec660df2bf4416e9c53fce516974593-de412b0dee0cb3a1-full-play.gif) ](https://www.loom.com/share/cec660df2bf4416e9c53fce516974593)

The module code is open source, and is extensible with newer modules. If you’d like to collaborate on developing new ones, get in touch!
