Utilihive Glossary

This glossary defines key terms used in GridOS Connect.

Term	Definition
Connect Agent	The Connect Agent is a lightweight on-premises runtime version of Connect suitable for running integration flows in constrained or isolated environments.
Connect Console	The Connect Console is the browser-based User Interface (UI) for managing and monitoring integration flows in GridOS Connect.
Connect Platform	The Connect Platform refers to Connect when deployed on GridOS Foundation. It runs as a set of interdependent Kubernetes services to deploy, run, and monitor integrations at scale, with built-in high availability, observability, and security.
Connect Service Account	A Connect Service Account is an authentication identity used to access integration flow endpoints, created with credentials (such as Basic authentication, API keys, OIDC, or Poller user) and granted flow access to invoke specific flows.
Connect SDK	The Connect Software Development Kit (SDK) provides tools to develop and deploy flows on your local computer using a Kotlin-based low-code DSL.
connector	Connect connectors are protocol and transport-level processors that handle communication over standard protocols and services such as REST, SOAP, Kafka, MQTT, SFTP, and cloud messaging.
Deployment Operator	The Deployment Operator is a service within the Connect Platform that manages deployables (flows, secrets, resources, and service accounts) as Kubernetes objects using Custom Resource Definitions (CRDs).
flow	Integrations are represented as flows in Connect.
Flow Access	Flow Access is the authorization mechanism used to grant Connect Service Accounts permission to invoke specific flow endpoints, ensuring that only approved accounts can access the corresponding flows.
Flow Server	Flow Server is the runtime environment where integration flows are run.
Flow Traces	Flow Traces provide a detailed history of messages processed across flows.
GridOS	GridOS provides the modern software tools to orchestrate the complexity of the sustainable energy grid while driving reliability and resilience - even in the face of increasing security and weather threats.
GridOS Connect	GridOS Connect is the official name of the integration platform in the GridOS ecosystem. It is also referred to as Connect.
GridOS Foundation	GridOS Foundation is the underlying infrastructure and core services that support GridOS applications.
processor	A processor is a component within a flow that performs a specific operation on a message, such as transforming data, filtering, flow control, or interacting with an external system.
Resource Registry	The Resource Registry is a centralized repository for integration resources including schemas, secrets, and user-defined dynamic tables.
SDK Deployer	The SDK Deployer is a tool that deploys flow specifications, flow access, resources, and secrets to the Connect Platform.
source	A source is the entry-point processor in a flow that generates, receives, or retrieves data and delivers it to the processing pipeline.

Term

Definition

Connect Agent

The Connect Agent is a lightweight on-premises runtime version of Connect suitable for running integration flows in constrained or isolated environments.

Connect Console

The Connect Console is the browser-based User Interface (UI) for managing and monitoring integration flows in GridOS Connect.

Connect Platform

The Connect Platform refers to Connect when deployed on GridOS Foundation. It runs as a set of interdependent Kubernetes services to deploy, run, and monitor integrations at scale, with built-in high availability, observability, and security.

Connect Service Account

A Connect Service Account is an authentication identity used to access integration flow endpoints, created with credentials (such as Basic authentication, API keys, OIDC, or Poller user) and granted flow access to invoke specific flows.

Connect SDK

The Connect Software Development Kit (SDK) provides tools to develop and deploy flows on your local computer using a Kotlin-based low-code DSL.

connector

Connect connectors are protocol and transport-level processors that handle communication over standard protocols and services such as REST, SOAP, Kafka, MQTT, SFTP, and cloud messaging.

Deployment Operator

The Deployment Operator is a service within the Connect Platform that manages deployables (flows, secrets, resources, and service accounts) as Kubernetes objects using Custom Resource Definitions (CRDs).

flow

Integrations are represented as flows in Connect.

Flow Access

Flow Access is the authorization mechanism used to grant Connect Service Accounts permission to invoke specific flow endpoints, ensuring that only approved accounts can access the corresponding flows.

Flow Server

Flow Server is the runtime environment where integration flows are run.

Flow Traces

Flow Traces provide a detailed history of messages processed across flows.

GridOS

GridOS provides the modern software tools to orchestrate the complexity of the sustainable energy grid while driving reliability and resilience - even in the face of increasing security and weather threats.

GridOS Connect

GridOS Connect is the official name of the integration platform in the GridOS ecosystem. It is also referred to as Connect.

GridOS Foundation

GridOS Foundation is the underlying infrastructure and core services that support GridOS applications.

processor

A processor is a component within a flow that performs a specific operation on a message, such as transforming data, filtering, flow control, or interacting with an external system.

Resource Registry

The Resource Registry is a centralized repository for integration resources including schemas, secrets, and user-defined dynamic tables.

SDK Deployer

The SDK Deployer is a tool that deploys flow specifications, flow access, resources, and secrets to the Connect Platform.

source

A source is the entry-point processor in a flow that generates, receives, or retrieves data and delivers it to the processing pipeline.