What is octoja?

octoja is a remote monitoring and management (RMM) platform for MSPs and IT service providers. You use it to monitor the workstations, servers, and network devices of all your customers, respond to issues, and carry out management tasks remotely – with one login, in one web interface, and without going on site.

Every managed device runs the octoja agent. It runs checks, reports inventory and health, and installs software and updates. The System Architecture describes how the parts fit together; Core Concepts explains the main terms.

The areas of octoja

Customers

Each managed organisation is a customer with its own devices and optional sites. Customer data stays separate, and groups decide which customers a user can reach.

Learn more: How customers, sites, and devices work, How customers, sites, and devices work

Agents

The agent runs on Windows, macOS, and Linux. You install it on single devices, through Microsoft Intune, or with enrollment tokens that assign new devices straight to the right customer and site.

Learn more: Deploy the Agent on Windows, Supported operating systems

Devices

Every device with an agent reports its hardware, installed software, services, and local user accounts; the inventory rolls this data up across all devices. From the browser, you work directly on a device through the terminal, file explorer, registry editor, or remote desktop. Switches, firewalls, printers, and other devices without an agent are monitored over the network by a device that has one.

Learn more: Search the fleet inventory, How remote access works, Add a Network Device Without an Agent

Checks

Checks are recurring tests, for example for disk space, services, backups, certificates, or hardware. You assign them through config packages to a single device or, by rule, to every matching device. Beyond the built-in catalogue, you write your own script checks or connect community repositories.

Learn more: How checks work

Alerting & Cases

When a check keeps failing, an alert configuration notifies you by email, SMS, phone call, app push, Microsoft Teams, or webhook, or opens a case in octoja or a ticket in your PSA. You work cases with status, priority, assignment, and a full history; end users can also raise them from the octoja agent in the system tray.

Learn more: Set up alerts for a check, Manage Cases

Automations

An automation links a trigger – a new device, a device start, a schedule, or a manual start – to a sequence of actions, for example run a script, install software, restart a device, or create a ticket. A test run on a single device lets you check it before you enable it.

Learn more: Create an automation

Patch Management

You roll out operating-system updates for Windows and macOS through patch policies in staged rings. You approve updates per patch cycle by hand or by rule, they install during the maintenance window, and a healthy rollout can move on to the next ring automatically. Linux devices are not patched; the System Updates check reports pending updates on all three platforms.

Learn more: How patch management works

Software Deployment

You install and update third-party software through config packages with Chocolatey, winget, Homebrew, and APT; you upload your own Windows installers (MSI or EXE) as custom packages. With the Software Kiosk, end users install approved software themselves.

Learn more: How software deployment works, Enable the Software Kiosk

Dashboards

The dashboard shows the health of all customers and devices at a glance, and the customer dashboard shows the figures for a single customer. For a screen in the office, there is the TV view.

Learn more: The customer dashboard, Set Up the TV View for Live Fleet Status

Reports

From built-in or custom templates, you generate PDF reports, for example on patch compliance, device health, or hardware inventory, for one customer or across all of them – automatically on a schedule if you like.

Learn more: Create a report template

Integrations

octoja connects to PSA and ticketing systems such as Autotask, HaloPSA, or TANSS, documentation platforms such as Hudu and IT Glue, security and backup platforms such as lywand, Bitdefender, or Acronis, and any other system by webhook. AI assistants such as ChatGPT and Claude access your octoja data through MCP.

Learn more: How integrations work, Set up Webhooks, MCP: overview and access

Users & Access

There are no fixed roles: groups decide which features their members can use and which customers and devices they can reach. Users sign in with a password or single sign-on, optionally with TOTP as a second factor.

Learn more: How Users, Groups & Permissions Work, How sign-in works

Settings

White-labeling replaces the name, logo, and colours with your own branding, on your own domain if you like. Settings also cover the email sender, among others. Define custom fields separately under Administration → Custom fields. The audit log tracks changes.

Learn more: Configure White-labeling, Custom fields, The audit log

API

The REST API is the same interface the web interface uses. Add /openapi to your octoja instance address for the interactive description of every endpoint.

Learn more: API Design Principles, API Authentication

Migration

You bring customers, sites, and devices over from an existing RMM such as NinjaOne or Datto. The Check Importer turns PowerShell monitoring scripts from the old RMM into custom checks.

Learn more: Migrate from a connected source RMM to octoja, Import monitoring checks with the Check Importer

Tips & Productivity

The command bar (Ctrl+K) searches devices, cases, customers, and users and jumps to any page; keyboard shortcuts let you work through lists and detail views without the mouse.

Learn more: Use the Command Bar, Keyboard Shortcuts

Next step

New to octoja? Start with Step 1 – Your First Login. If octoja is unreachable or a page does not load, see octoja Availability & Status.