SyntrumDocs

What is Syntrum

Syntrum is digital workforce software. You don't build automations in it — you hire AI employees, called agents, and put them to work inside the tools your company already uses. Each agent has an identity, a job, and the judgment to do that job without being told every step.

This page explains the idea behind the product, how it's different from the tools you may be comparing it to, and the loop that makes an agent an agent.

The thesis: hire, don't build#

Traditional automation asks you to become a builder. You map out every step, connect triggers to actions, and account for every branch — and the moment reality drifts from your flowchart, it breaks and you go back to editing.

Syntrum asks you to become a manager instead. You describe the role, the objective, and the responsibilities, and the agent figures out the how. When something is unclear or risky, it asks — like a good employee would — rather than failing silently or guessing.

That shift changes what your job looks like:

Building automations Managing a digital workforce
You design each step You define the role and the goal
Logic is fixed and brittle Judgment adapts to the situation
You maintain the flow forever You coach the agent over time
Hard to see what ran or why Every action is recorded and explained

How Syntrum differs from RPA and chatbots#

It's easy to file Syntrum next to tools you already know. Here's why it isn't those things.

Not RPA / workflow automation#

Robotic Process Automation and workflow builders execute predefined scripts. They repeat the exact steps you recorded, in the exact order, and they can't handle anything you didn't anticipate. A Syntrum agent isn't following a script — it observes what's actually happening, decides what to do based on its role and memory, and adapts when circumstances change. There's no flowchart to maintain.

Not a chatbot#

A chatbot waits for you to type, answers, and forgets. It's reactive and stateless. A Syntrum agent is proactive and continuous: it watches your tools for work, acts on its own initiative, remembers what it learned, and reports back — even when you're not looking. You can chat with it (see Chatting with agents), but conversation is how you guide the worker, not the whole product.

The short version#

RPA / workflows Chatbots Syntrum
Trigger Fixed rules Your message Watches for work itself
Behavior Scripted steps One-shot replies Reasons and adapts
Memory None Short-lived Durable and improving
Oversight On/off None Supervision, guardrails, approvals
Runs when you're away Only if scheduled No Yes

The loop at a glance#

Every agent runs the same five-phase cycle, continuously:

Observe → Understand → Decide → Act → Report

  • Observe — watch connected tools for new events.
  • Understand — interpret them using role, memory, and company context.
  • Decide — choose an action, checked against your guardrails.
  • Act — do it, or pause to ask when a rule requires approval.
  • Report — record what happened, why, and the outcome.

This loop is the reason an agent can be trusted to work unsupervised within limits you set. The full walk-through, with a worked example and where you can step in, is in The agent loop.

Humans stay in control#

Autonomy without control isn't useful. Syntrum keeps you in the loop through three mechanisms that work together:

  • Supervision modes — how independent each agent is by default. See Supervision & modes.
  • Guardrails — the workspace-wide floor for what any agent may do, including which actions are always blocked or always gated. See Guardrails & sensitive actions.
  • Approvals — the queue where an agent asks before doing something your rules gate. See Approvals.

These resolve through one cascade — Workspace → Agent → Tool — where a block at any level is a floor that lower levels can't loosen. That mental model is The three planes.

In one sentence: Syntrum lets you hire AI employees that observe your tools, decide and act with real judgment, remember what they learn, and stay governed by rules you control — with every action recorded.

What's next#