Skip to content
This repository has been archived by the owner on Jun 4, 2021. It is now read-only.


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit

* (SEC-166) update jdbc-postgres to 42.2.14

This commit updates jdbc-postgres to 42.2.14 to
fix CVE-2020-13692.

* (maint) update rack to 2.1.4

This commit updates rack to v2.1.4 to address CVE-2020-8184

* (maint) update NEWS for 1.9.9 release

Co-authored-by: Steve Axthelm <>

Git stats


Failed to load latest commit information.
Latest commit message
Commit time
October 31, 2019 15:43
October 31, 2019 15:43
October 31, 2019 15:43
June 11, 2013 14:46
October 31, 2019 15:43
August 22, 2019 14:43

Razor server

Razor is an advanced provisioning application which can deploy both bare-metal and virtual systems. It's aimed at solving the problem of how to bring new metal into a state where your existing DevOps/configuration management workflows can take it over.

Newly added machines in a Razor deployment will PXE-boot from a special Razor Microkernel image, then check in, provide Razor with inventory information, and wait for further instructions. Razor will consult user-created policy rules to choose which tasks to apply to a new node, which will begin to follow the task directions, giving feedback to Razor as it completes various steps. Tasks can include steps for handoff to a DevOps system such as Puppet or to any other system capable of controlling the node (such as a vCenter server taking possession of ESX systems).

Getting in touch

Getting started

The Wiki has all the details; in particular look at

What does Razor do anyway?

Razor is a power control, provisioning, and management application designed to deploy both bare-metal and virtual computer resources. Razor provides broker plugins for integration with third party configuration systems such as Puppet.

Razor does this by discovering new nodes using facter, tagging nodes using facts based on user-supplied rules and deciding what to install through matching tags to user-supplied policies. Installation itself is handled flexibly through ERB templating all installer files. Once installation completes, the node can be handed off to a broker, typically a configuration management system. Razor makes this handoff seamless and flexible.

Razor MicroKernel

The MicroKernel is a small OS image that Razor boots on new nodes to do discovery. It periodically submits facts about the node and waits for instructions from the server about what to do next, if anything.

A prebuilt archive is available.

Razor Client

The Client is a small Ruby script that makes interacting with the server from the command line easier. It lets you explore what the server knows about your infrastructure, and modify how machines are provisioned, by interacting with the Razor server API



Razor is distributed under the Apache 2.0 license. See the LICENSE file for full details.


Razor is next generation provisioning software that handles bare metal hardware and virtual server provisioning



Code of conduct

Security policy





No packages published