Skip to content
Horon

Core concepts

The ideas the rest of the docs build on: plugins, workspaces, requests, and your files.

Plugins and products#

A product is a tool such as Router, Messenger, or Mail. A plugin is how that product is meant to reach the app, against a fixed C ABI contract.

The agent loads an enabled plugin through that contract, and each product also runs as its own program.

Workspaces#

A workspace is meant to be where a person's files, conversations, and settings sit together, so everything in the app belongs to the one they are in.

The database keeps organizations, members, and projects, and the desktop app's workspace API reads them. The public website does not yet create a workspace for you or show one.

Requests and results#

A request is one task you ask Horon to do. Horon reads the data it needs, plans, runs the work, and returns a result with the steps it took.

You stay in control of where a request goes and what it can touch.