Create packages that you can easily hand-off to developers, operations, or even customers that contain everything needed to provision and deploy your applications consistently, across all environments.
Inspect packages to see who created them and why, as well as what application code they contain, and precisely how the environment will be configured and deployed. This allows developers to specify exactly what their application requires, and operations to review packages prior to installation.
Install offline with the Romp CLI, or use BuildMaster to orchestrate deployments across any number of servers and environments. Whichever way you deploy, the same configuration and deployment code is used, including prompts for required input like variables and credentials.
Repair package installations after inadvertent configuration changes to restore the developers’ original intent, or easily uninstall packages to remove all traces of application code and environment configuration. This enables even faster and simpler iterations than rebuilding entire servers or containers.
Discover which packages have been installed on a machine with the Romp CLI, UPack, or Otter to see where the package came from, which tool installed it, and which user triggered the deployment. Romp packages also have a built-in audit history that lets you track changes or repackaging back to the source.
Track everything that changed on a server, from any romp package at any time, using the detailed execution logs that are retained for all package installs, repairs, or uninstalls.