Otter Documentation

Romp Reference Guide

Romp was such a success as part of Otter, it is being expanded to its own product. You can check out the progress on the Romp page.

Romp is a standalone command-line execution engine for executing OtterScript plans on a single server. Like the full version of Otter, it uses the execution engine to execute configuration plans or orchestration plans.

Romp is typically used by developers to develop and test plans or extensions.


Romp is available from the Otter Downloads page as a zip file, or as a package on To install the chocolatey package, simply type choco install romp.


Romp is invoked as follows:

romp [--globalOptions...] <command> [commandOptions...]

The command is one of the following:

The global options can be used with any command, and are used to configure execution behavior and environments.

--variables=<variableDefinitionFile.otter> When specified, Romp will process the specified OtterScript file as a variable declaration file; that is, any top-level Set Variable statements will be imported into the execution environment.
--lib=<templateDirectory> When specified, Romp will process all .otter OtterScript files in the specified directory and make any top-level templates available to the executing plan.
--extensionsPath=<extensionsDirectory> Romp will attempt to load all .otterx Otter extensions from this directory before executing the plan. When this option is not specified, Romp will look for extensions in the same directory that contains romp.exe.
--verbose When this flag is present, Romp will log extra low-level execution information in addition to standard execution logging. This level of logging is normally not necessary and should only be used if you suspect there is a bug in the execution engine.