Trio's IT Operations (IT Ops) module gives IT teams a unified workspace to connect to cloud and on-premises infrastructure, maintain an accurate inventory of managed targets, browse live cluster resources, store credentials securely, and automate routine tasks across their environment — all from a single console.
Dashboard Overview
When you open IT Ops, the overview screen gives you an at-a-glance summary of your environment:
Total devices managed, broken down by online and offline status
Running automation jobs in real time
Playbook count and vault secret count
A feed of your most recently active devices and recent job executions
Connectors
Connectors let Trio reach out to your cloud accounts and Kubernetes clusters to discover and manage infrastructure. Four connector types are supported today:
Connector | Auth method | What it discovers |
Kubernetes | Kubeconfig file | Cluster resources (nodes, pods, namespaces, deployments, services) |
AWS | Access key + secret | EC2 instances |
Azure | Service principal | Virtual machines |
GCP | Service account key | Virtual machines |
Each connector supports:
Connection testing — verify credentials and reachability before use
Asset sync — pull the latest inventory from the provider on demand
Health monitoring — see the current connection health at a glance
Enable / disable — pause a connector without deleting it
Credentials for all connectors are stored encrypted at rest through Trio's credential system and are never shown after initial entry.
Inventory
Trio builds a unified inventory from all active connectors. Discovered assets appear automatically after a connector syncs and are updated on subsequent syncs.
Assets view shows all discovered targets across every connector in one table. You can search, filter by connection profile or asset group, and open an asset's detail page to see its connection details, associated playbooks, and history.
Network Assets view shows the subset of assets classified as network targets, with the same filtering and detail capabilities.
Asset Groups let you organise assets into logical collections for use as automation targets. Both dynamic groups (rule-based membership) and static groups (manually curated lists) are supported. Each group detail page shows its member assets and the playbooks that have run against it.
Kubernetes Resources
For each Kubernetes connector, Trio provides live browsing of the cluster's current state — no kubectl required.
From the Kubernetes Resources page, you see a table of all your configured clusters with their name, context, status, connection health, last tested time, and creation date. Clicking a cluster opens its resource explorer.
The cluster detail page organises live resources into five tabs:
Nodes — name, roles, ready status, allocatable CPU (cores/millicores), allocatable memory, OS image, kernel version
Namespaces — name and phase (Active / Terminating)
Pods — name, namespace, phase, ready container ratio, restart count, assigned node
Deployments — name, namespace, status, desired / ready / available / updated replica counts
Services — name, namespace, type (ClusterIP / NodePort / LoadBalancer), cluster IP, external IPs, ports
Connection Profiles
Connection profiles define how Trio connects to an asset for automation — SSH, WinRM, or other supported methods. Each profile stores the authentication method and maps to a credential profile for its secrets.
Features include:
Health check — test connectivity to all assets mapped to a profile in one action
Status control — enable or disable a profile without removing it
Multiple auth methods — password, SSH key, certificate, token, and others depending on the connection type
Filtering by status, health, and connection method
Credentials
The Credentials section manages the secrets that power your connectors and connection profiles.
Credential Profiles store typed secrets (passwords, SSH private keys, API keys, bearer tokens, and more). Secret values are write-only after creation and are never displayed again. The overview page shows profiles that need attention, rotation due dates, and resolution failure counts from the past 24 hours.
External Vaults let you connect Trio to your organisation's own secrets infrastructure (such as HashiCorp Vault or similar providers) so that credential values are fetched at use time rather than stored in Trio.
Native Vault is Trio's built-in encrypted secret store for teams that do not use an external vault.
Secret Usage Audit records every resolution event — which secret was accessed, by which automation job, and when — giving you a tamper-evident log for compliance purposes.
Automation
Playbooks are YAML-based automation scripts that you upload to Trio and run against one or more asset targets. You can assign a playbook to individual assets or to asset groups, and run it immediately or save it for later use.
Automation Jobs track every playbook execution. The jobs table shows the playbook name, target device count, current status (pending, running, completed, failed), and timing. Active jobs display a worker status bar so you can see in-progress work at a glance. You can cancel a running job directly from the list.
Automation Catalog provides a library of pre-built commands and playbook templates to help you get started quickly without writing automation from scratch.
Roles and Groups
The Roles page lists the RBAC roles defined in your tenant and their assigned permissions, so administrators can verify who has access to IT Ops capabilities.
The Groups page manages user groups relevant to IT Ops access control, with an inline edit drawer for quick membership changes.