About Business Process Tracker

What it is

At its centre is a process library: how the business works, modelled in BPMN 2.0 on a diagram canvas, organised five levels deep from value chains down to work instructions, each process with an owner, a version history and an approval.

Around it is an ERP — finance, procurement, inventory, manufacturing, quality, service management, projects, people, customers, contracts, risk and compliance. The records those modules keep are joined to the processes that produce them, so a purchase order, a non-conformance or a month-end close can be traced to the process it followed and the control that governed it.

Why it is built this way

Organisations that answer to auditors and regulators usually keep their processes in one tool, their records in another and their evidence in a third, and reconcile the three by hand before every audit. BPT keeps them in one place, and builds the controls into the software rather than around it:

• whoever drafts or changes a record never approves it;
• approvals that are records are electronic signatures, bound to a hash of exactly what was signed;
• every change is written to an append-only, hash-chained audit trail, in the same transaction as the change itself;
• each customer organisation’s data is separated from every other’s by the database, not only by the application.

It is designed to be provable against SOC 2, ISO 27001, NERC CIP, HIPAA and 21 CFR Part 11: each control is written down as code, mapped to the requirements it answers and tested. BPT does not hold a certification or attestation against any of these frameworks; they are what it is designed to let its customers demonstrate. The Security page describes the measures in place.

AI that proposes, and people who commit

BPT can draft a process, or a whole landscape of them, from a description of the business. The model it uses is one the deployment runs itself, and its drafts are proposals: nothing a model writes becomes a record until a person accepts it, and each run is recorded with the model that produced it.

Where it runs

BPT is one container image and a PostgreSQL database. It runs on its operator’s own servers — on premises, in a private cloud, or with no connection to the internet at all — and needs no outside service to work: its virus scanning, its AI model and its office editor run inside the same deployment. This site is itself a self-hosted deployment of BPT.

Where it stands

BPT is being built now, module by module. The site describes the finished product, and not every part is available yet. Access is by invitation while it is built: sign-up is closed, and every request is read by a person.

To see it for your organisation, request access. To ask anything else, see Contact.