Windows remoting through connections — not a free PowerShell.
WinRM and PowerShell Remoting (PSRP) are one Windows connection family. You store the host and choose WinRM or PSRP, keep passwords and certificates in the vault, then test the path or run approved Windows Ansible books. Same idea as SSH: a governed connection, not a shell in the request.
What Windows remoting is allowed to do
WinRM connector. People who only browse the catalogue can see connections; creating, changing or rotating them is for administrators. Passwords and client certificates stay in the organization vault — not in a prompt or in process text.
WinRM and PSRP
One connection record, two plugins: WinRM and PowerShell Remoting. You pick the plugin when you create the connection.
Secrets in the vault
Passwords and client certificates stay in the organization vault — never in the request or in automated process JSON.
Test the host
winrm.test checks connectivity with vault credentials before a automated process depends on the Windows host.
Windows Ansible books
Predefined books (for example ping and facts) and approved Windows scenarios run over that connection — not an arbitrary remote script from the model.
Not a free shell
There is no open remote PowerShell. Calls go through the connection and approved books, the same way SSH uses command profiles.
With Ansible workspaces
Windows playbooks in an Ansible workspace can be marked for WinRM and run against this connection.
Behind VPN when needed
If the Windows host is only reachable over VPN, bring the gateway up first — then WinRM or PSRP.
Explore more
Terraform
A Terraform connection points at modules you have approved. Automated processes can validate, plan, apply and show the result. Destroy stays off unless the connection allows it and a person has approved. Typical work: a Proxmox VM, deploying or upgrading a stack, preparing an environment. Provider credentials — including Proxmox API tokens — stay in the organization vault. The run can be local or over an existing SSH connection.
Ansible
Ansible connections bind inventory and playbooks into governed automated process steps. A run uses an approved playbook, sensitive credential-referenced credentials and organization policy. Chat does not get a free ansible-playbook shell.
SSH
SSH connections store host, port, user and keys in the vault. Automated processes run approved command profiles. A free-form remote command from the model is off; a named profile is used instead.
VPN
VPN connections (IPsec / IKEv2, SSTP or WireGuard, client or server role) sit in the same governed catalog as SSH and Ansible. From a server connection in admin you generate secrets once, then download ready profiles and install commands grouped by iPhone, Android, Windows and Ubuntu. Typical path: gateway first, then SSH, playbooks or Windows remoting on the far side.
Connectors
The platform composes tools, capabilities and connections: MCP, REST, SQL, GitHub, SSH, Ansible, Terraform, WinRM/PSRP and other deployed connections. Calls go through organization policy and sensitive credential references.
Ready to move beyond the chatbot?
Build AI that understands your business, works with your knowledge, follows your processes and can actually finish the job. You decide which actions are allowed, when a person must step in and how much AI usage your organization can consume.