System Architecture

Overview of the octoja architecture and its main components.

Written By Erdinc Akay

Last updated 17 minutes ago

This article describes how octoja is built and how the individual components work together.

Overview

octoja is made up of three main components: the Agent, the platform, and the web interface.

The Agent runs on each monitored device and sends data over HTTPS to the octoja platform. The platform stores the data, evaluates check results, and serves the web interface that you use in your browser.

The Agent

The Agent is installed on monitored devices and is responsible for local data collection and communication with the platform.

  • Collects system metrics such as CPU, memory, disk usage, and service state
  • Runs local checks and sends results to the platform
  • Collects hardware and software inventory
  • Installs operating-system and third-party patches
  • Provides remote desktop access and other remote operations
  • Uses outbound HTTPS on port 443

The Agent also includes an on-device app that lives in the system tray, so people at the device can send a support request, install approved software from the Software Kiosk, and allow or decline a remote desktop session when consent is required.

The Platform

The platform is the central service that receives Agent data and makes it available for monitoring and operations.

  • Receives and stores Agent data
  • Evaluates check results
  • Provides the web interface

The Web Interface

The web interface is the central place where you manage your tenant from a browser. It covers customers, sites, groups, and users; devices, check results, and dashboards; cases; integrations; branding; reports; agent enrollment and deployment; and remote operations on monitored devices.

Data flow

  1. The Agent collects metrics on the monitored device.
  2. The Agent sends that data to the platform over HTTPS, and keeps a persistent realtime connection (WebSockets over TLS) open for live commands, presence, and remote desktop streaming.
  3. The platform stores the data and evaluates check results.
  4. Users review the current state in the web interface, which receives live updates over the same realtime channel.

Connectivity requirements

ComponentRequirement
AgentOutbound HTTPS (port 443) to the octoja service endpoint, plus a persistent WebSocket connection over TLS on the same port for the realtime channel
Web interfaceAny modern browser with internet access
Outbound integrationsoctoja reaches external integration endpoints (webhooks, PSA and ticketing systems, inventory sync) over HTTPS on port 443 only. Other ports can be requested through support.