Research comparison · verified 22 Sep 2026
Four marketing-work layers, plus an n8n license comparison.
Choose the lowest layer that can do the job with a named owner, a human review step and a cleanup route. n8n is shown beside Activepieces CE to make the source-available versus OSI-style license boundary clear.
Decision rule
Use Mautic for an owned marketing system; Activepieces CE for cross-system triggers and transformations; Marketing Agent OS for planning or research in an existing harness; and Loopmark only as an exploratory local drafting CLI. Use n8n only after checking its source-available license against the intended use and assigning an operator. A small newsletter may need none of these: see the 29 September scoped Listmonk–Keila audit. Neither tool joins this vetted comparison.
At-a-glance comparison
| Candidate | Use it for | License status | Start with | Decision |
|---|---|---|---|---|
| Mautic Platform | Owned contacts, forms, campaigns, landing pages and lifecycle email. | Tagged 7.2.1 metadata declares GPL-3.0; OSI-style for the named component. | Database, PHP/web environment, HTTPS, mail transport and cron/queue operations. | Conditional fit for teams that can operate a self-hosted marketing system. |
| Activepieces CE Orchestrator | Reviewed flows across existing CRM, form, email and analytics systems. | MIT for CE/outside named EE paths; check the path and edition. | Docker Compose, app/worker/Postgres/Redis, public URL for external webhooks and backed-up encryption key. | Conditional fit for technical RevOps with a flow owner and failure test. |
| n8n Source-available | Visual workflows and optional AI/agent steps across systems a team already owns. | Sustainable Use License for covered code; source-available/fair-code, not OSI-style. Check exclusions and intended commercial provision/hosting. | Disposable local Docker test, fictional data, no public webhook and no action node. | Conditional only when the intended use fits n8n’s license and an operator owns deployment and controls. |
| Marketing Agent OS Harness library | Reusable marketing skills in a supported agent harness. | Apache-2.0 declared wrapper/normalized layer; inspect retained upstream licenses. | An approved harness, limited project-scope skills and no secrets for the first test. | Conditional fit for developers and consultants; planning, not execution autonomy. |
| Loopmark Agent Exploratory local drafting CLI | Local drafting in a Python CLI with local JSON. | MIT for the checked repository. | Fictional data, disposable local JSON and only a separately approved restricted test key; leave social credentials absent. | Not a team-approval system, managed scheduler, CRM, or production/unattended publishing service. See the 23 Sep decision. |
License guardrail: n8n and Activepieces CE
n8n: public code and self-hosting do not make it OSI-style open source. Its Sustainable Use License restricts commercial provision/hosting. Read the license, the official FAQ and the n8n dossier.
Activepieces CE: the prior verified report identified MIT for Community Edition/outside named EE paths. That is a component/path boundary, not a claim that every repository path or enterprise feature is MIT. Read the Activepieces CE dossier.
Do not infer more than the evidence supports
No connector was tested. A node or piece entry does not establish permissions, target API behavior, data handling, retries, costs, consent, deliverability or production readiness. Read the dossier before connecting a real system.
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.