So I built a visual workflow builder where my non-technical teams can create & run those deterministic workers themselves, see the logs, and produce the outputs on their own machines. They can also connect an agent over localhost MCP and vibe code new workers; what comes out is real Kotlin that compiles and plugs into the workflow. An agent can drive the whole app, which is great for iterating on workflow building.
There is no server side, it's a JVM app (not Electron! :D) that lets you create, compile & attach your own workers; it's basically an IDE for automations. You can create workers either from your own agent over localhost MCP (Claude Code, Codex) or using the builtin Claude chat with your own API key — so Ipek is completely free to run, with no per-task fees; your only cost is your own API usage, and you own the data & software. Check the video on the website for more.
Current state, honestly: it's quite a stable alpha, available for macOS and Windows; Linux is on its way. I also want to implement triggers, schedules, cron jobs, and deploying a workflow to the CI/CD of your choice, in case the workflows/data gets heavy.
Tech stack: Kotlin Compose Multiplatform on the JVM, SQLDelight, workers are Gradle-built plugins that hot-load — so each worker is actually a self-sustainable(?) JAR executable that attaches like a JetBrains IDE plugin, then Ipek orchestrates and executes them.
I think Ipek will be useful for many of you, too; I'd like to hear which repetitive tasks you would actually throw at it. Cheers!