Oxta vs n8n: when you would rather not run a server
n8n is an excellent tool if you have a developer. Self-hosting is free, but the server, updates, backups and uptime become your job.
What is actually being compared
n8n counts whole runs, just as Oxta does, so the cloud price per thousand runs is close. The difference is not the tariff but how much work is left to you.
| Service | What it meters | 1,000 runs |
|---|---|---|
| n8n Cloud | the whole run | $9.18 |
| Oxta Starter | the whole run | $1.20 |
| Oxta Pro | the whole run | $0.39 |
Self-hosted n8n
Yes, you can run it for free. Then you need a server, updates, monitoring, backups and somebody to fix it on a Saturday evening when the scenario has stopped and the shop is not messaging customers.
For a team with a developer that is a fair price for full control. For a shop without a technical department it is not.
Where n8n is stronger
- Full control over the data: everything stays on your server.
- Arbitrary code in steps, and any library you like.
- A large community and a big catalogue of nodes.
Where Oxta is stronger
- Nothing to administer: a scenario works the moment it is installed.
- Scenarios written for Ukrainian shops rather than generic examples.
- Dry runs and sample cases that are replayed after every edit.
- Support in Ukrainian and payment in hryvnia.
The essentials, briefly
Can I migrate workflows from n8n?
Yes, n8n files can be imported: Oxta parses them and shows what carried over and what needs a manual touch.
Can I write my own code in a step?
There are transformation steps driven by expressions. Arbitrary server-side code, as in n8n, is deliberately not available — predictability is the trade.
Where is run data stored?
On Cloudflare infrastructure. The processors involved and the processing terms are set out in the legal documents.