One concrete process-engine problem per folder, solved in working code. Find your problem, read how it was solved and take what you need: a cookbook, not a meal kit.
Most engine material shows how to use an engine. The harder questions come later: how do I put single sign-on in front of Cockpit, or run my own tasklist on Zeebe? process-engine-blueprints shows whole services that automate a process. A recipe here shows one solution:
- One problem. A recipe contains the code for its problem and nothing else.
- As it is. Each recipe exists in one language. There are no variants and no starter: copy the folder or the part you need.
- Self-contained. Every recipe builds on its own, and nothing is shared between recipes.
- Checked by CI. Each recipe is built on every change that touches it and names the engine version it was built for.
| Problem | Recipe | Engine | Language |
|---|---|---|---|
| Single sign-on for the web applications | camunda7-cockpit-sso |
Camunda 7.24 | Java |
| One cockpit for the engines of several services | cibseven-multi-engine-cockpit |
CIB seven 2.2 | Java |
| Every user task form type side by side | cibseven-user-task-forms |
CIB seven 2.2 | Java |
| Your own tasklist via a Zeebe exporter | zeebe-external-tasklist |
Camunda 8.5 | Kotlin |
Looking for an older showcase? They are preserved at the tag archive/showcases-2026.
Open the recipe's folder, not the repository root. Its README.md and AGENTS.md treat that folder as the project.
Every recipe README follows RECIPE_TEMPLATE.md, so they all read the same way: Ingredients (versions and prerequisites), How it works, Cook it (run it locally), Taste test (the automated proof), Take it home (copy it into your project) and Kitchen notes (gotchas).
See CONTRIBUTING.md.
Distributed under the MIT License. See LICENSE file for more information.