Orchestrator dossier · checked 27 Sep 2026
Activepieces CE: run a flow, but own its effects.
Community Edition is a self-hosted workflow executor for teams with an operator. The 27 Sep audit reads release 0.92.0 and current docs; it did not run a flow or test recovery.
Source and edition
The root license on main places code outside named EE paths under MIT Expat, subject to third-party component licenses. EE paths require a commercial production license. License files were not compared at the 0.92.0 tag; a piece's own license and CE availability need checking. Flow Approvals require Enterprise/Cloud and Environments; RBAC and audit logs are marked paid. A manual human review is an operator rule, not an enforced CE feature.
Execution and credentials
Documented run path. App → Redis/BullMQ → worker/engine. PostgreSQL holds flows, runs and Connections; current production recovery docs also name S3 for logs/checkpoints. A crashed in-flight step may re-run, so target-service writes need idempotency and compensation. Durable execution · recovery
Key and network path. Losing AP_ENCRYPTION_KEY makes backed-up Connections unreadable. Current environment docs list unsandboxed execution and unrestricted network defaults. Inspect code/egress and back up key material separately. Environment reference
Smallest proposed evaluation
On an isolated disposable CE instance, use a fictional brief, Manual Trigger, and one local transform to make a three-item Markdown calendar. Create no Connection, LLM, HTTP, email, social, CRM, public webhook, or paid-media action. Inspect a run and a harmless failure if possible; name a human reviewer, then purge data and secrets. Stop if the selected version cannot take the manual fictional input. This is a plan, not a test result.
The current Limits page says self-host default execution-data retention is 30 days and log cap 50 MB, but Truncated Logs says 25 MB. Neither establishes deployed retention or backup deletion. Verify the actual version, flags and deletion.
Read the audit
Execution, credentials and recovery audit → · Research library · Layer comparison
For the separate draft → approval → optional action responsibilities, read the 28 Sep cross-layer handoff synthesis. It is not a tested integration or a recommendation to connect these products.