# Open-source n8n alternatives for developers: engines and agents

> A workflow engine runs the graph you draw; an agent harness runs the job you describe. When the work is a fixed flowchart, keep n8n. When it is not, Kortix is open source, and your agents, skills and memory live in one git repo you own.

URL: https://n8n-alternative.com/n8n-alternatives-for-developers

## Kortix and n8n, side by side

Every n8n cell comes from n8n's own docs; the Kortix column quotes Kortix.

| | Kortix (recommended) | n8n |
| --- | --- | --- |
| Open source | Yes. Read it, fork it, audit it. | No. Its docs say it does not call itself open source. |
| The unit of work | An agent session on its own machine. | A workflow of nodes you draw on a canvas. |
| Who sets the steps | The agent plans; a person approves the change. | You wire each node; the engine follows the graph. |
| Where the logic lives | Markdown agents and skills, plus kortix.yaml, in git. | Nodes on a canvas, plus code steps in JavaScript or Python. |
| Version control | The config is the repo. | Git version control needs a paid plan. |
| Human approval | Approval gates you set. Off until you set them. | Human approval for tool calls. |
| Where it runs | Kortix Cloud, your VPC, or on-prem network. | Self-hosted with Docker, or n8n Cloud. |
| Where work lands | Session work reaches main through a change request. | The workflow runs and acts in the connected apps. |

## A scheduled job is a few lines of YAML

`triggers/reports/weekly.yaml`

```yaml
# triggers/reports/weekly.yaml
triggers:
  - slug: weekly-report
    type: cron
    agent: kortix
    cron: "0 0 15 * * 0"
    prompt: Build the weekly report.
```

Source: https://kortix.com/docs/project/manifest

Triggers live in the repo, so a cron schedule or a signed webhook starts a session with nobody present.

## A workflow engine and an agent harness are different tools

A developer searching for an n8n alternative usually has one of two jobs, and the tool differs.

A workflow engine runs a graph you draw. You place nodes, wire them, and the engine follows the same edges on every run. n8n is one of these, and its docs describe it as a fair-code workflow automation tool that combines AI features with business process automation. When the path is fixed, that graph is right: it is deterministic, readable, and cheap to run at high frequency.

An agent harness runs a job you describe. You state the outcome, and an agent plans the steps, installs what it needs, and works until it is done. Kortix is that harness with everything around it. OpenCode is the harness, configured by a file in the repo, and each session boots its own isolated machine with your repo already on it.

If your task list is a set of fixed flows, n8n is a fair choice. This guide is for the developer whose backlog is not a flowchart.

## The developer setup path

Kortix is open source, and a project is a git repo you own. The shape on disk:

- `agents/<name>.md` holds one agent's behavior.
- `skills/<name>/SKILL.md` holds a skill the company shares.
- `memory/` holds what the company has learned, as files.
- `kortix.yaml` declares what each agent may reach, the triggers, the connectors and the machine image.

You work from a terminal. The CLI creates the project, scaffolds `kortix.yaml` and your agents, and brings it live. A scheduled or signed-webhook trigger starts a session with nobody present, so the jobs you would give an n8n cron node run here too.

When a session runs, the agent commits to its own branch and opens a change request. Merge is default-deny for agents, so you read the diff before it reaches the default branch. Models are your choice: any model provider with your own keys, or the ChatGPT plan you already pay for.

## Which shape to reach for

- A nightly sync between two systems, the same fields every time: a workflow engine.
- Research a market and write a one-page brief: an agent session.
- Reproduce a failing test and open a fix: a coding-agent session with a change request.
- Reconcile a month of records where the exceptions vary: an agent that plans its own steps.

The [open-source n8n alternative guide](/open-source-n8n-alternative) walks the self-host path, the [migration checklist](/migrate-from-n8n) covers leaving n8n, and [n8n for AI agents](/n8n-for-ai-agents) goes deeper on the agent case. The [Kortix blog](https://kortix.com/blog/kortix-vs-n8n) carries the longer comparison.

_FAQ_

## n8n alternatives for developers, answered

The questions a developer asks before choosing a stack.

### What is a good n8n alternative for a developer?

It depends on the job. For fixed flows, keep n8n. For open-ended work, Kortix is the open-source AI Operating System, with agents running on their own machines from one repo you own.

### Is n8n open source?

No. Its docs say it does not call itself open source and describe the product as fair-code.

### Can I self-host Kortix?

Yes. Self-host is free: install the CLI, initialize the instance, and start the stack on your own machine, VPC or on-prem network.

### Where does the configuration live?

In one git repo you own. Agents are markdown, skills and memory are files, and kortix.yaml declares what each agent may reach and when work starts on its own.

### How does work land in the codebase?

Each session works on its own branch and opens a change request; merge is default-deny for agents, so a person reads the diff before it reaches the default branch.

## Run the work you cannot draw first.

Kortix is open source, and the repo is yours to keep.

[Try Kortix](https://kortix.com) · [Read the docs](https://kortix.com/docs)

Open source · Any model, your keys · Self-host, VPC, or on-prem