Skip to main content

​
Hiro League

Hiro League is a private team of empathetic AI characters. They are active, emotional and loyal. They live in your private environment to serve you, your family and your home.

​
Core concepts

​
Root Node

The Root Node is the desktop where you install and setup HiroLeague. It is where Hiro Server lives and runs. In a local/network only setup, this is also where you install and run Hiro Gate, or the gateway. All Nodes(other Hiro devices) connect to Hiro Server (on the Root Node) through the Gateway.

​
Hiro Server

Hiro Server is the core component of HiroLeague. It controls all of the operations of the HiroLeague ecosystem.
  • Communicates with Nodes and Third Party Apps through Channel Plugins
  • Configure and manage the Workspaces
  • Operate the AI Agents

​
Workspaces

A workspace is an instance of the HiroLeague ecosystem. Typically, you will have one workspace on the Root Node. Only HiroLeague developers may install multiple workspaces to test alternative configurations.

​
Nodes

Any Hiro device that connects to Hiro Server through the gateway is a Node. Hiro devices are Mobile, web and desktop applications, used to communicate with Hiro Server. They are richer communication and control devices than using third party apps like WhatsApp or Telegram.

​
Control Room

The Control Room is a web app, accessible only from the Root Node. It is used to manage all aspects of Hiro Server.

​
Hiro Gate (Gateway)

Hiro Gate is the authentication and routing boundary between Nodes and Hiro Server. Hiro Gate is designed to work in a local/network only setup, or in a remote setup where it is installed on a cloud VPS. Remote setup facilitates remote access to the HiroLeague ecosystem from the internet. Hiro Gate can host multiple gateway instances on the same machine. Typically, you will have one gateway instance. Only HiroLeague developers may install multiple gateway instances to test alternative configurations.

​
Third Party Apps

Third Party Apps are communication apps that connect to Hiro Server through Channel Plugins. Whatsapp and Telegram are the most common examples.

​
CLI Commands

  • hiro is the command-line interface used to run any HiroLeague command.
  • hirogate is the CLI command to manage and operate the Gateway. HiroLeague package bundles both hiro and hirogate commands.

​
What’s next

Hiro Server Components

The concurrent components inside a workspace server process.

Channel Manager

Plugin spawning, subprocess lifecycle, and JSON-RPC communication.

Communication Manager

Message routing, inbound/outbound queues, and permission checks.

Protocol contract

Shared wire contract for messages, events, requests, gateway envelopes, and device frames.

Agent Manager

LLM worker, conversation memory, and available tools.

HTTP Server

Local status, lifecycle, metrics, character profiles, and Tool Registry API.

Gateway instances

Local vs VPS gateway configuration and device authentication.

Tools architecture

How CLI commands, HTTP endpoints, and agent tools share the same interface.