why would I use this over n8n?

From our experience, n8n is great for linear workflows and connecting APIs through flowcharts. Rowboat is aimed at building agentic systems (multiple orchestration patterns, autonomous agents coordinating, non-linear decision making).

Those are much harder and time-taking to express and maintain in a flowchart model. Our goal with Rowboat was to make it simple and quick to build and maintain multi-agent assistants. Hence, the copilot is equipped with tools and state-of-art orchestration patterns [1], which allow it to build ready-to-go assistants in minutes from high-level requirements.

[1] https://cdn.openai.com/business-guides-and-resources/a-pract...

	▲	segmenta 5 days ago \| parent [-]
		To add to this, we strongly believe that a flowchart type builder quickly hits the ceiling on the type of assistants you could build with it. And this has do with the fact that many real world tasks don't have a well defined flow to them. This is especially true if there is a human on the other side like in customer support - something n8n is clearly not meant for.