PowerOps

Deterministic infrastructure operations for power-sensitive environments.

PowerOps gives infrastructure operators one command-line interface for inventory, outage response, orchestration, and provider-backed operations. The CLI connects to a TLS-only PowerOps Service. A simulator lets operators rehearse the same command workflows before enabling real adapters.

PowerOps keeps consequential actions visible: the operator chooses the target, mode, credentials, safety options, and moment of execution.

What you can do

• Register and inspect provider Authorities for vCenter, Azure, AWS, and Linode.
• Manage Physical Nodes, Virtual Machine Nodes, UPS Nodes, Node Groups, and Device Groups.
• Discover network devices, maintain HTTP/SSH/USB/serial Device inventory, and assign Devices to Nodes.
• Track outages through detection, confirmation, securing, recovery, resolution, and history.
• Create, plan, freeze, start, inspect, stop, and evaluate orchestration policies.
• Migrate Virtual Machine Nodes and evacuate Physical Nodes when the selected provider supports the operation.
• Protect provider credentials and sensitive configuration with a master-password workflow.
• Back up and restore the PowerOps database, follow logs, and inspect health information.
• Rehearse operational workflows against a manifest-backed simulator.

Current product boundary

The current PowerOps interface is the CLI connected to the TLS TCP Service. PowerOps does not ship a browser control plane, HTTP API, RBAC, MFA, multi-user identity system, or autonomous AI operator.

Provider support is capability-based. A provider may support inventory but not power, migration, evacuation, or another operation. Real USB and serial command execution are currently unavailable; their inventory commands remain available.

The installed package is authoritative for its command version. Run powerops help whenever this guide and an installed package differ.

Install

Choose your platform:

• Install PowerOps on Windows
• Install PowerOps on Linux

Both packages install the Service and CLI. The local-lab setup creates a local TLS certificate, configures CLI certificate pinning, starts a machine-bound trial, and records an operator-owned orchestration master password for protected workflows.

For shared or production environments, use an operator-owned certificate and your normal secret-management process.

Start safely

After installation, confirm the Service and license before changing inventory or policy state:

powerops help
powerops license status
powerops device network list
powerops node vm list --output table
powerops orchestration status --output json

Use the simulator before power, shutdown, migration, evacuation, restore, purge, or live-provider operations. Verify the exact target and Service mode, confirm a recovery path, and obtain human approval immediately before the action.

Command basics

powerops <area> <type> <command> [arguments] [options]

Examples:

powerops help device
powerops help node vm migrate
powerops device network monitor
powerops outage list --output table
powerops orchestration status --json

Output choices:

• --output human for normal text;
• --output table for table-preferred human output;
• --output json or --json for redacted machine-readable output.

--format is unsupported. Use --culture en, --culture fr, or --culture de to select human-message language. Command names, JSON fields, identifiers, and protocol values remain invariant.

For protected commands, use bare --masterpassword to receive a masked prompt. For unattended operation, pass the name of an environment variable with --masterpassword-env <env-var-name>. Provider credentials follow the same pattern with --password, --password-env, --secret, and --secret-env.

Never place secret values directly in command arguments, configuration files, logs, or support messages.

Read by task

Need	Guide
Install or remove PowerOps on Windows	Windows guide
Install or remove PowerOps on Linux	Linux guide
Learn end-to-end operating workflows	User manual
Find the current command families	Command reference
Configure the Service, CLI, TLS, database, or simulation	Configuration guide
Review human-control and secret-handling boundaries	Safety guide
Diagnose connection, TLS, Service, license, database, provider, or simulator problems	Troubleshooting

A safe operating pattern

1. Check powerops license status and powerops help.
2. Read current state with list, get, status, health, or plan commands.
3. Back up the database before a risky change.
4. Rehearse in simulation where practical.
5. Review the target, provider, mode, credentials, flags, and recovery path.
6. Execute only after explicit human approval.
7. Read the result, health state, outage state, and logs.
8. Record what changed and whether recovery completed.

License

Use of PowerOps is governed by the PowerOps EULA included with the package. Review it before installation or use. This guide does not replace or modify the EULA.