Workflow builder to automate repetitive data work.
Tell Ipek the result you want and let your agent create deterministic workers, then run them on your desktop. Repeatable workflows over files and APIs — with no per-task fees, however much you run.
No account needed · Free with BYO Key or MCP
You describe it
AI builds a worker
…and runs on your canvas
See it in action
Build it, run it, change it.
01
Run a workflow on the canvas
Drop in your files, wire up the workers, and hit run. Each step executes in order while the logs and outputs appear live — the same result every time, so you can trust it and re-run whenever.
02
Update a worker by chatting with AI
Need a step to work differently? Open the worker and tell the AI what to change in plain words — it rewrites the worker for you, then you re-run to see the new result.
Use cases
Built for startups, non-technical teams, and prototype-heavy work.
How it compares
Three honest ways to do the job.
Each approach is good at something. Here's where each one lands for the job Ipek is built for.
| Capability | A custom script | Zapier / Make | Ipek |
|---|---|---|---|
| Run a multi-step job — API calls, files, parallel branches — over and over | ~ You code & host it yourself | ✗ Every step × every item is a billed task | ✓ On your machine — no per-task fee |
| No code to write or maintain | ✗ You write & maintain it | Low-code, but you wire it up | ✓ AI builds the steps for you |
| Bring your own AI — your Claude key, or your own agent over MCP | ~ Your key, but you write every call | ✗ AI runs on their platform & billing | ✓ Your key, no markup — or bring your own MCP agent |
| Reads a folder of files on your computer (PDFs, scans, sheets) | Yes, if you code it | ✗ Cloud-only or through Drive/Dropbox — can't touch your local disk | ✓ A core part of the job |
| Finished outputs land on your desktop, ready to open | ✓ Written to your disk | ✗ Held in their cloud — export to pull them out | ✓ Open them the moment they're done |
| Connects the apps & data you already use (support inbox, Linear, Sheets…) | You code each API yourself | ✓ Their core strength | ✓ Yes — with your own keys |
| Crunch heavy jobs — large files & big batches | ~ You host & scale it yourself | $ Stuck in their cloud — costly at volume | ✓ Deploy the same pipeline to your CI (e.g. GitHub Actions, GitLab CI, Jenkins) for heavy jobs |
| Starts on its own (a schedule, a new email) | ~ You wire up a cron job | ✓ Many built-in triggers, webhooks, and schedules | Not yet, webhooks & cron jobs are coming soon |
| Built for ops / finance / support folks | ✗ For developers | ~ Some setup & glue | ✓ Built for exactly this |
Developer-focused tools like n8n, Windmill, and Pipedream can do a lot of this too — if you're happy running a server/docker or wiring up every step yourself. Ipek is the version for non-technical team leads: it installs like a normal app, and the AI plans & builds the steps for you.
FAQ
Honest answers.
Does my data leave my computer?
Your files stay on your machine. The one part that talks to the internet is the AI that helps build the steps — and we're always clear about exactly what gets sent.
Do I need to write code?
No. You describe what you want in plain words and the AI builds the steps. You can open and adjust those steps, but you never write or compile code. The AI steps read your files, and each result lands as a plain file you can open.
Is the AI free? Do I need a Claude API key?
Two things to separate here — the app and the AI builder. The AI uses your own Anthropic Claude key, so it's "bring your own key": you add it once in Settings, and from then on only the requests that build a worker or ask the chat anything go to Anthropic, straight from your computer. We don't run servers at all — there's no Ipek account or middle-man in between, so we never see your key. And running the workers you've built is free — once they're set up they run locally on your desktop. You pay Anthropic directly for the AI you use (usually cents per run), with no Ipek markup. A key is only needed for our built-in builder — if you'd rather use the AI you already have, you can connect your own agent over MCP instead, and it runs on whatever model and billing that agent uses (more on that below).
Ipek is free now — what happens to my workflows when pricing starts?
It's free while it's in alpha, and becomes a paid app after launch. Anything you've built stays yours and keeps working — and release-waitlist members get a launch discount on the paid version. No rug-pull: whatever version you've downloaded keeps running as-is — we won't block it, disable it, or lock you out when pricing starts.
Can I use a local LLM instead of Claude? What about MCP?
MCP is here now. Ipek speaks MCP, so you can bring your own agent (BYOA): connect the AI tool you already use — Claude Desktop, Cursor, Claude Code, or any MCP client — and drive Ipek from it, instead of the built-in builder. Native local-LLM support for the built-in builder is still on the roadmap — once Ipek has proven the concept it promises, we'll add the option to run workers against models on your own machine. In the meantime, if your own agent already runs on a local model, BYOA effectively gets you there today.
Get it
Start building your workflows.
No account or payment needed. Everything runs on your own machine, offline.
Waitlist
Lock in a launch discount.
Get a discount when Ipek goes paid. You'll also hear about new features and Linux support as they land.
What you build keeps working when pricing starts.
Honest pricing: free in alpha, paid after launch. Waitlist members who use it get a significant launch discount — while all your workflows will keep working on alpha. No rug-pull.