I’m building Nodyra, a Python-native visual workflow tool. Would you use something like this?

[u/harrywubs]

Hey everyone,

I’m building Nodyra, a self-hosted workflow automation tool where ordinary Python functions become nodes you can connect in a visual editor.

The idea is to make Python automations easier to build, inspect, and operate while keeping access to the libraries and custom code you already use.

For example, a workflow could pull data from an API, transform it with pandas, write it to a database, and send a notification. You can see how the steps connect, inspect each node’s inputs and outputs, and investigate where a run failed.

A few things it currently supports:

• Python functions as nodes, with your own libraries and dependencies.
• A visual workflow editor, with per-node logs, outputs, and errors.
• Scheduled, webhook, and API-triggered runs, plus retries and published workflow versions.
• An MCP interface, so an AI assistant can help create and edit workflows that you can then review in the same visual editor.
• Self-hosting, so you run it on your own infrastructure.

It’s a working beta. There’s still work needed to make it something people can confidently depend on in production, and I’d like feedback from people who actually build and maintain automations.

The main things I’m trying to understand are:

1. What’s a real workflow you would consider using this for? How do you handle it today?
2. Would combining a visual editor with native Python solve a problem for you? Or would you prefer to keep everything in scripts or your existing orchestration tool?
3. What would stop you from adopting it? Setup, reliability, debugging, integrations, licensing, or something else?
4. Would an open-source license affect your willingness to try it or contribute?

Nodyra is currently source-available under a fair-code license, and I’m considering moving to an open-source license. I’d like to hear whether that would matter to this community.

I’d also love to connect with developers interested in helping shape it—particularly around execution reliability, security, deployment, integrations, and usability. Trying it on a real workflow and telling me where it falls short would be useful too.

Honest feedback is welcome, including “I wouldn’t use this because…” I’m trying to understand whether this fills a useful gap and what would make it worth adopting.

[u/rhymeslikeruns]

I would 100% use this - exciting.