What Is NixOS
NixOS is a declarative Linux distribution where the entire system configuration -- packages, services, users, firewall rules, kernel modules -- is defined in a single specification file. Building a NixOS system from the same configuration always produces the same result. osModa chose NixOS as its foundation for atomic rollback, reproducibility, and declarative security.
Declarative vs. Imperative Configuration
On a traditional Linux distribution (Ubuntu, Debian, CentOS), you configure the system imperatively: run commands to install packages, edit configuration files, enable services, add users. The system state is the cumulative result of every command ever run. Two servers that started identical can drift apart as different administrators make different changes.
NixOS inverts this model. You write a configuration file that describes the desired system state. NixOS evaluates the configuration and builds the system to match. If you want nginx with a specific configuration, you declare it. If you want a specific version of Python, you declare it. The system is the configuration, and the configuration is the system. Two servers built from the same configuration are identical.
Why osModa Chose NixOS
osModa is an AI-native platform built on NixOS + Rust. The choice of NixOS is driven by three properties that are essential for AI agent infrastructure:
Atomic Rollback
Every deployment creates a new generation. If the deployment breaks something, SafeSwitch rolls back to the previous generation in seconds. No partial states, no manual recovery.
Reproducibility
Every osModa server built from the same configuration is identical: same packages, same service configurations, same 9 Rust daemons. No configuration drift. No "works on server A but not server B."
Declarative Security
Firewall rules, user permissions, service isolation, and security policies are all part of the NixOS configuration. Security is not an afterthought -- it is declared alongside everything else and enforced consistently.
NixOS + Rust: osModa's Technical Foundation
osModa runs 9 Rust daemons on NixOS, each defined and managed through the NixOS configuration system: agentd, osmoda-mcpd, osmoda-watch, osmoda-routines, osmoda-voice, osmoda-mesh, osmoda-keyd, osmoda-teachd, and osmoda-egress. These daemons are built as Rust binaries and declared as NixOS services, which means they are automatically started, supervised, and included in system generations.
The Nix package manager handles all daemon dependencies. Each daemon's dependencies are isolated from other daemons -- a library version used by osmoda-mcpd does not conflict with a different version used by osmoda-mesh. This dependency isolation prevents the class of bugs where updating one component breaks another.
NixOS for Server Infrastructure
NixOS is particularly well-suited for server infrastructure where reliability and reproducibility matter more than desktop convenience. The declarative model means infrastructure is code: the NixOS configuration can be version-controlled, reviewed in pull requests, tested in staging, and deployed identically to production.
osModa servers are available in four regions: Frankfurt, Helsinki, Virginia, and Oregon. Every server in every region runs the same NixOS configuration, ensuring identical behavior regardless of geographic location. Plans range from Solo (2 CPU / 4 GB / 40 GB at $14.99/mo) to Scale (16 CPU / 32 GB / 320 GB at $125.99/mo), all on dedicated infrastructure.
For a detailed guide to NixOS deployments and rollbacks on osModa, see NixOS Atomic Deployments & Rollbacks. For a comparison of NixOS with other deployment approaches, see NixOS vs Docker for AI Infrastructure.
Frequently Asked Questions
What is NixOS?
NixOS is a Linux distribution built on the Nix package manager. Unlike traditional Linux distributions where you install packages imperatively (apt install, yum install) and configure services by editing files in /etc, NixOS defines the entire system -- packages, services, users, firewall rules, kernel modules -- in a single declarative configuration file. Building a NixOS system from the same configuration always produces the same result, regardless of what was installed before.
What does 'declarative' mean in this context?
Declarative means you describe the desired end state, not the steps to get there. Instead of saying 'install nginx, then create this config file, then enable the service,' you write a NixOS configuration that says 'the system has nginx running with this configuration.' NixOS figures out how to get from the current state to the desired state. If nginx is already installed with a different config, it updates the config. If nginx is not installed, it installs it.
Why did osModa choose NixOS?
osModa chose NixOS for three properties critical to AI agent infrastructure: atomic rollback (every deployment is a generation that can be instantly reverted via SafeSwitch), reproducibility (every server built from the same config is identical, eliminating 'works on my machine' problems), and declarative security (firewall rules, user permissions, and service isolation are all part of the system config, not ad-hoc additions).
How does NixOS enable atomic rollback?
NixOS maintains a history of system generations. Each generation is a complete, self-contained system state. Switching between generations is a symlink operation that takes seconds. If a deployment breaks something, you roll back to the previous generation instantly. The new generation does not overwrite the old one -- both coexist on disk. osModa's SafeSwitch automates this with health checks after each deployment.
Is NixOS harder to use than Ubuntu or Debian?
NixOS has a steeper learning curve because it uses a different model: declarative instead of imperative. But for server infrastructure, this model is an advantage. You write the configuration once, and it is reproducible, version-controlled, and rollback-safe. osModa handles the NixOS configuration for you -- the platform ships with a pre-configured NixOS setup including all 9 Rust daemons, 83 MCP tools, and security policies.
Can I customize the NixOS configuration on osModa?
Yes. Every osModa plan provides full root SSH access. You can modify the NixOS configuration to install additional packages, configure custom services, adjust firewall rules, and add system users. Changes are applied through the NixOS rebuild process, which creates a new generation. If the changes cause problems, SafeSwitch rolls back to the previous generation automatically.
Experience NixOS on Dedicated Infrastructure
Full root SSH access to a pre-configured NixOS server with atomic rollback, 9 Rust daemons, and 83 tools. Plans from $14.99/month.
Spawn Server