RackN offers customers a compelling set of solutions overcoming the integration gap existing today between base provisioning and orchestration services for building up the stack. By automating bare metal provisioning RackN is able to quickly configure and boot services independent of the orchestration or platform chosen. Thus, we can deploy bare metal, operating systems, virtual machines, cloud resources, and even edge packages from one tool.

Digital Rebar Platform (DRP) is the powerful provisioning and workflow platform with an open ecosystem managed by RackN. Kept to an extremely small footprint and without external dependencies, DRP offers customers a modern provisioning tool capable of supporting existing service destinations regardless of resource.

RackN builds management and automation tooling to operate DRP via a first-class CLI and our air gap self-hosted and SaaS-based RackN Portal solution. Using our workflow paradigm, customers are able to monitor and control every step in the process from resource identification to provisioning to tear down.

FAQs about RackN and Digital Rebar Platform:

  1. Is your product a service?  No.  Our product is software that is operated by our customers behind their firewalls.  We do not provide a managed service, hosted offering or appliance.
  2. What type of virtualization do you use?  None.  Our product automates the actual physical infrastructure using its native APIs (PXE, IPMI, DHCP, etc).  No virtual machines are required for control; however, we can install a wide range of VM management platforms on top of the bare metal including one implementing ESX and KVM.
  3. Which hardware vendors do you support?  All.  We work hard to make sure our products are vendor neutral and heterogeneous.  We can support any hardware vendor, ARM, Intel and AMD processors, IPv4 and IPv6, and Windows, Linux, CoreOS, ESXi and others.
  4. Do I have to replace my DevOps tools and Systems of Records?  No.  We work hard to integrate with existing configuration management and management systems.  While we can replicate this functionality, we always plan to minimize disruption during initial phases.