Get started
Core concepts
The words the product uses, and how the pieces fit together.
How the pieces fit
You work inside an organization. Its work is split into projects. In a project you chat with Auprimus and give it an instruction. It plans a workflow of steps, runs them against the project's connectors, guided by skills, and records everything each step does.
Terms
| Term | What it means |
|---|---|
| Organization | Your company or team in Auprimus. Members, billing, model keys and skills belong to it. |
| Project | A piece of work with its own chats, workflows, connectors and files. Access is set per project. |
| Chat | A conversation in a project. Each chat is kept, so you can pick it up later from History. |
| Instruction | What you ask for, in plain English. It describes the outcome, not the steps. |
| Workflow (DAG) | The plan Auprimus builds from an instruction: steps and the order they depend on each other. The app calls it a DAG. |
| Step | One unit of work in a workflow, such as reading a table or making a chart. The app calls it a node. |
| Run | One execution of a workflow, with its own time, tokens, cost and outputs. |
| Connector | A system Auprimus reads from and writes to over one connection: a database, files and storage, a stream or queue, an API or an MCP server. |
| Skill | A written guide that tells a step how your organization, or Auprimus, does a kind of task. |
| Guardrails | What Auprimus is allowed to do in a project - install packages, write to your data, send results out - and what it must ask you about first. |
| Script | The code a step ran. It is saved when the step succeeds and replayed on reruns. |
| Output | What a run produced: tables, charts, files and reports, in Files Explorer. |
| Schedule | A rule that reruns a finished workflow hourly, daily, weekly or monthly. |
Something wrong or missing? Write to [email protected] about “Core concepts”.Updated 11 Oct 2026