What we have been up to

Leveraging NixOS Tests in your Project

By Linus Heckemann, Simon Lackerbauer, Franz Pletz on Thu, 7. Jul 2019

NixOS contains infrastructure for building integration tests based on QEMU/KVM virtual machines running NixOS. Tests built on this infrastructure are continuously run on new nixpkgs versions to ensure that NixOS continues to install and boot and that various services continue to operate correctly. This post illustrates how one may test a simple web service using NixOS tests. To have a simple enough example at hand, we wrote a small service in PHP—a classical guestbook in which visitors can leave a message that will then be written to a database and subsequently shown to later visitors of the same site.

Continue reading

The nixops defaults module

By Simon Lackerbauer on Thu, 11. Nov 2018

Avoiding code repetition in a nixops deployment As with most configuration management tools, there are some options in nixops that need to be defined for virtually any machine in a deployment. These global options tend to be abstracted in a common base profile that is simply included at the top of a node configuration. This base profile can be used for including default packages, services or machine configuration usually needed on all machines—like networking debug tools and admin users with access to the whole network.

Continue reading

The NixOps resources.machines option

By Robin Gloster on Fri, 10. Oct 2018

The resources.machines attribute set NixOps provides the evaluated node configurations of a deployment network in the resources.machines attribute set. Using this information, one can easily implement machine configurations that are generated from options in an existing network. For example, a reverse proxy that automatically proxies to all other webservers in the network—one which could handle TLS termination for all of them—can be generated without having to manually define individual virtual hosts.

Continue reading

Our Crew

Franz Pletz

Franz Pletz


NixOS Security & Release Manager

Franz has been herding GNU/Linux systems for over 15 years. You are probably running some of his code right now because he loves submitting patches just as much as ranting about broken code.

Robin Gloster

Robin Gloster


NixOS Release Manager

Robin has been using Linux since he was a 13 year old child in school and has always been hacking around with it, being happiest with NixOS and loving its declarativity. No more eventual consistency, the usual case with other configuration management.

Linus Heckemann

Linus Heckemann


NixOS Release Manager

Discovering nix a year after living through a period of docker-related frustration made Linus very happy, and he has since become a very active member of the community, regular contributor, and release manager for NixOS 19.03 and 19.09.

Simon Lackerbauer

Simon Lackerbauer


nixpkgs contributor

With research interests in statistics and data analytics, another failed virtualenv led this long-time functional programming enthusiast to nix. He hasn’t looked back since.

Our Services


Whatever the challenges are, that you are facing using Nix and the related tooling, we have the prevalent solutions you can depend upon.


In individual workshops we will introduce you and your team to the wonders of reproducibility without the need for scary side effects.


After evaluating and analyzing your current infrastructure, we will provide you with the insights you need for a successful transition to the Nix ecosystem.


Whether you want continued assistance on your declarative journey or long term support for a NixOS release with security updates, we have got you covered.

Contact form

Tell us more about what you are building and we will get back to you with our thoughts and ideas. We love video conferencing and encourage you to propose some date and time to meet up and get acquainted. Giving you the advice you need to reach an informed decision before getting down to business goes without saying for us.


Mayflower GmbH
Landsberger Straße 314
80637 München

Email: nix@mayflower.de
Github: mayflower
Twitter: @nixflower