AThink Cortex

Run your whole robot fleet from one console you host.

Cortex is the fleet console for AThink Desktop. Pair your machines, push robots from one library, run and schedule them from anywhere, let robots on different machines start each other with events, and see every run, log and report, on a server of your own.

Included with AThink Enterprise · Runs on your server with Docker · Machines connect outward

Cortex + Desktop

Every machine, every run, on one screen.

AThink Desktop runs robots on each machine. Cortex is the dashboard that manages them all.

AThink Cortexdevices

StatusName
No devices yet.

Pair a device

JRQXJWZ

Single use · expires in 9:49

AThink Desktopyour machines

FINANCE-PC-01

Not paired

OPS-PC-02

Not paired

HR-LAPTOP-03

Not paired

Events

Robots that start each other, across every machine.

A robot publishes an event to a topic in Cortex. Every robot listening to that topic, on any paired machine, starts its work. One process can hand off to the next without anyone watching a screen, and without opening a port.

ORDERS-PCOrder intake

1Read Emailsemail · orders inbox
2Agent · StartAI · read the order
3Create Sales Ordersap · customer, lines
4Send Messagekafka via Cortex · robot.orders.new
↓

Cortex

robot.orders.new

↓

WAREHOUSE-PCPick orders

1On Messagekafka via Cortex · robot.orders.new
2Enter Pick List5250 · by field name

FINANCE-PCInvoice orders

1On Messagekafka via Cortex · robot.orders.new
2Create Invoicesap · orderId

Publish from any robot

Add a Send Message step to a robot whose Kafka connection is set to Via Cortex Relay. No broker address, no credentials on the machine.

Listen on any machine

Start a robot from On Message, inside a Kafka Events scope. Cortex pushes each event to it as it arrives, over the machine's own outbound link.

Every listener gets it

Each machine reads a topic in its own consumer group, so every machine listening to a topic receives every event.

Kept in its lane

Robots can use only robot.* topics, never Cortex's own. Message size and open consumers are capped, and the broker is never exposed.

Run it from the console

Administrators create topics, watch the traffic and send a test message from the Kafka Bus page in Cortex.

Reporting

From the console to the wall screen.

Everything Cortex collects becomes a report: in the console, in Grafana dashboards that come ready-made, and on a wall screen that rotates through them.

01 — Cortex — Fleet overview

Kiosk · 1/8

Devices online

42/44

Active runs

7

Uptime

99.2%

Runs per day

Cortex rotation · read-only kiosk · next in 1m
Fleet overviewOperations: logs & transactionsGroups & fleet commandsRobot SLA & reliabilityRun analyticsErrorsSecurity & auditTransfers & library

In the console

Reports, ready on day one

  • •Fleet and runs, robot SLA with duration percentiles, flakiness and MTBF, transfers and the library.
  • •Cost and savings: money saved by automation, per robot and over time.
  • •Security and audit for administrators: who did what, sign-ins and failed sign-ins.
  • •Export the report data to CSV for any time window.

In Grafana

Eight dashboards, built in

  • •Grafana ships inside Cortex with eight dashboards already set up, from fleet overview to errors.
  • •No second login: Cortex roles carry over. Administrators edit and build dashboards; operators and viewers read.
  • •Edited a dashboard too far? Reset it to the shipped version in one click.
  • •It runs on open-source Grafana, with no extra licence.

On the wall

A kiosk for the operations room

  • •Point a wall screen at one link and it rotates through the dashboards, full screen.
  • •Choose the speed, from every 15 seconds to every 30 minutes, and the window, from the last hour to the last 90 days.
  • •The screen signs in as a read-only kiosk with its own token, so no password sits on the display.
  • •New dashboards join the rotation automatically.
Reports tabs in the console:Fleet & runsRobot SLATransfers & libraryCost & savingsSecurity & audit

What Cortex does

One console for the fleet, from pairing to proof.

Devices and groups

Pair a machine with a single-use code or QR. See every device online, degraded or offline, save groups, and revoke a device in one click.

One robot library

Upload a robot once and push it to a device or a whole group. Pull a robot from any device back into the library.

Snapshots

When a robot is replaced or deleted, the old package is kept as a snapshot you can restore.

Remote control

Run, stop, pause, resume, enable or disable a robot on one device or across the fleet, with no remote desktop.

Schedules and inputs

Set a robot's schedule and its inputs on every device that has it. Each machine stores the schedule and runs it.

Runs, logs, transactions

Every run, log line and transaction streams back to Cortex, kept for as long as you set.

Reports, Grafana, kiosk

Reports in the console, eight Grafana dashboards built in, and a kiosk that rotates them on a wall screen.

Events between robots

A robot on one machine publishes an event, and robots on every listening machine start from it, through Cortex.

Control

Who can do what, and a record of it.

  • ✓Three roles: administrator, operator and viewer. The last administrator can't be removed.
  • ✓An audit log of actions, sign-ins and failed sign-ins, for administrators.
  • ✓Machines connect outward over WSS with short-lived signed tokens, so no port is opened on any PC. It works through a corporate proxy.
  • ✓A machine that loses its connection keeps its events and sends them when it reconnects.
  • ✓Passwords for protected robots are passed to the machine for one run and never stored.
  • ✓Sign-in uses your AThink account with an emailed code. On an air-gapped site, Cortex runs on a licence file with its own people.

More on sign-in, licences and offline sites on the Security page.

On your server

Three steps, on a server you own.

Your robots, runs and logs stay on your network. Cortex needs a server with Docker; each paired machine runs AThink Desktop, which must be running for its robots to run.

Install

Cortex ships as one Docker Compose stack: the console, MongoDB, Kafka and Grafana. Set three values and start it with one command.

$ docker compose up -d

Secure

Cortex listens only on the server itself. Put your own reverse proxy with TLS in front, and give people the address.

Pair

In AThink Desktop, open Settings → Cortex and enter the pairing code. The machine appears in the console, ready for robots.

AThink Enterprise

Bring your fleet under one console.

Cortex comes with AThink Enterprise. Your agreement sets how many machines can pair and how many people can sign in, and robots are unlimited.

Individual is free on one machine and does not include Cortex.