LukeflowPlatform Manual

A multi-tenant BPMN process engine and its capability fleet — forms, email, signatures, phone, documents, access and workflow — documented end to end.

Introduction

Architecture

The Fleet

Platform Services

The Java/Spring core engine (FluxNova — a Camunda-7 fork), the WorkOS↔engine auth gateway, the S3 file/PDF proxy, and the FastAPI AI-agent fleet.

Core Engine, Auth, File Proxy, Agents

Applications

The consumer orchestrator UI, the operator cockpit (Camunda-cockpit-style ops console), and the public marketing site.

Consumer UI, Core UI, Marketing

Headless Libraries

Framework-agnostic engines vendored into the apps — Forms, Email, Signatures, Lists, Analytics and Workflow — each a core + React + builder monorepo.

Forms, Email, Signatures, Lists…

Capabilities

The domain features tenants subscribe to — how forms, email, e-signature, phone (Vapi), documents, access requests and calendars/SLA fit together.

Capability model

Operations

The Render deployment blueprint, the fleet-wide security program, the testing strategy, and the Postman API collection.

Deploy, test, secure

Reference

A completeness scorecard rating every repo across six metrics, plus a glossary of Lukeflow terms.

Scorecard & glossary

About this manual

This is the engineering manual for Lukeflow — the platform behind the luke-* repositories. It is written in the spirit of the Camunda 7 manual: a wiki-style reference with a section tree on the left, prose and reference tables in the middle, and an On this page outline on the right.

The platform is built around a multi-tenant BPMN process engine (luke-core-engine, a fork of the FINOS FluxNova / Camunda-7 engine) that also hosts an in-process capability data layer. Everything else — the UIs, the headless authoring libraries, the auth gateway, the file proxy and the AI agents — orbits that core.

Documentation snapshot

This manual reflects the state of the fleet as of July 2026. Where a component is still in progress, the page says so explicitly and links to the relevant gaps in the Completeness Scorecard.