Integrations and Hermes
Understand approved-system connections and the boundary between the hosted control plane and Hermes runtimes.
LeenOps Workflows can execute work across approved systems. A connector or runtime integration controls how that work reaches a provider; it does not remove the workflow’s permissions, Workflows organization scope or approval gates.
The Console currently contains integration surfaces for systems including AI runtimes, Google Search Console, GitHub, Sentry, PostHog and Workspace connections. Availability and setup requirements differ by solution. Only rely on an integration when the Console shows it as connected and ready for the current Workflows organization.
Hermes
Hermes is a managed client runtime connected to the hosted Workflows control plane. The client runtime lives in a dedicated Docker deployment; the hosted control plane owns deployment registration, readiness, access, approvals and the client-facing observability surface.
Cloud and Hermes must use the same workflow key, version, schema references and Workflows organization boundary. Secrets are resolved by the target runtime and must not be copied into workflow payloads, artifacts, documentation or support messages.
Hermes is currently marked beta in the Console. Provisioning and operator actions require the appropriate entitlement and role. A Hermes-only user can be restricted to the Hermes product area.
Technical identifiers
Runtime variables, database objects and service paths can retain compatibility
names such as leenops-hermes or products/agents/*. Use the exact identifier
required by the implementation; use LeenOps Workflows in customer-facing
explanations.
Next: Security and governance.