Home

Auton8

A self-hosted business automation platform: model a process, define the data it works on, and give people the screens to work it.

Most automation tools stop at the workflow engine and leave you to build the application around it. Auton8 ships both halves — a BPMN engine and the records, documents, forms, dashboards and query tools a process actually runs on — behind one administrable UI.

Status: 0.1. Early, and honest about it. It runs, it is tested, and it is in use — but interfaces move, and there is no upgrade-compatibility promise between 0.x releases yet.

Start here

If you want to…	Go to
Install and run it	Installation
Learn to use it	User-Guide
Understand how it is built	Architecture
Know what it depends on, and why	External-Services
Change the code	Structure · Conventions · Testing

Using Auton8

Guide	Covers
Records	Record types, fields, records, relationships, comments
Workflows	Modelling BPMN, deploying, running, tracing
Documents-and-Notes	Collaborative documents, DOCX, notes and pages
Queries-and-Dashboards	AQL, saved queries, sharing, widgets
Data-Stores-and-Pipelines	Stores, connectors, datasets, pipelines
The-Assistant	The in-app agent and its limits
Administration	Users, roles, permissions, menus, plugins, health

Building Auton8

Page	Answers
Architecture	Components and boundaries, request flow, authorization, events, the agent loop
External-Services	Postgres, Flowable, Dapr, NATS, Redis, the two Node sidecars, LLM providers
Stack	Languages, frameworks, versions, configuration keys
Integrations	Environment variables and wiring detail
Structure	The directory map — "where do I put this?"
Conventions	Naming, patterns, error handling, with real excerpts
Testing	How the suites are organised and run
Concerns	Known tech debt and fragile areas — see the caveat below

Two caveats

The generated map pages are a snapshot. Stack, Integrations, Architecture, Structure, Conventions, Testing and Concerns were produced by tooling from a specific commit, and each carries a provenance banner. Much has changed since — most issues Concerns cites are fixed. Read them for the shape of the system; read the issue register for what is open.

The hand-written pages — Installation, User-Guide and the guides under it, External-Services — are maintained directly.

Issue numbers may be stale. The project moved repositories on 2026-09-02 and numbers were not preserved. References to the old register are written archived-N and can be looked up in docs/history/. A bare #N means an issue in the current repository.

Elsewhere

• Repository · Contributing · Security
• Development · Deployment
• Licensed Apache-2.0. Third-party components keep their own licences — notably bpmn-js, whose "Powered by bpmn.io" attribution must be preserved.