Skip to content

Record your work. Ipek automates it.

Describe the process you want to automate: combine APIs, extract from PDFs and spreadsheets, or analyze exports with AI. Ipek MCP plans, builds, tests, and runs the workflow chains for you, on your desktop.

No account needed · Free

1 of 7

Recordings

Record your screen while you talk the task through, or just talk. Speech is transcribed on your computer, and your AI reads the recording to learn the steps.

Your AI

Claude Code, Codex or any other MCP client can operate Ipek from start to finish. You talk to your AI, and it plans with you in the Project document, then builds and refines the workers, workflows and dashboards.

Workers

Each worker is a small, deterministic program your AI writes: fetch from an API, read a PDF, merge or remove duplicates, analyze documents with AI. Workers take parameters, like an API key or a filter. You can open any worker and read its source code, which belongs to you.

Workflows

Connect workers on the canvas to build the process. Branch when needed, combine results, or repeat a step for each file. Each worker saves its outputs in a run folder, including data returned by APIs, so you can inspect the results.

Project DB

Each project has a built-in SQLite database for data a workflow needs to keep from one run to the next, like which stocks your workflow bought on its previous run. Your AI sets it up and manages it, so there is nothing for you to write.

Dashboards

Ask your AI to build a dashboard from your workflow results. Review customer feedback, track prices, or inspect individual records without opening each output file.

Automations

Run a workflow every 10 minutes, every weekday at 9:00, or once a month. Your computer needs to be awake with Ipek running.

Workflows built with Ipek

See the steps, results and dashboards from three working projects.

Yeddi YüzQuiz content review

Review and correct reported quiz questions

15× faster. Students get corrected questions right away instead of waiting for the weekly review.

Students report problems with quiz questions in Yeddi Yüz. The workflow collects those reports from PostHog, uses Claude to check the questions against curriculum notes, and writes corrections to the question files. A dashboard shows the changes, reports that needed no fix, and questions that need a person.

Workflow canvas in Ipek: PostHog feedback, a review queue, a Claude review per batch, and a worker that applies the fixes to the question bank Dashboard in Ipek: questions fixed, reports where the user was wrong, questions that need a person, and each report with Claude’s reasoning Project document in Ipek: an overview of the quiz feedback project, its open questions, and the latest changes
StockSentimentMarket research

Stock market data fetched from various sources and analyzed by AI

24× faster, ~4% more profit. New SEC filings, news and Reddit posts are analyzed within minutes of being published.

Every few minutes Ipek collects what is new, Claude scores each item, and the buy and sell calls go into a portfolio priced from a live broker feed. Each call is graded against the S&P 500 after 72 hours. You can connect your broker’s API to execute orders automatically.

Dashboard in Ipek: every position with its entry, exit, result and price path The News: Analyze workflow on Ipek’s canvas: SEC ticker map, gate and batch, fetch filing text, a Claude score per filing, and a route that ends the run when nothing is new Ipek’s Library: the project’s workers, with the source code of the broker quotes worker Project document in Ipek: what the StockSentiment project tests and how its workflows fit together
PolarstepsCustomer feedback

Customer feedback grouped into product needs and sent to Linear

12 hours saved every week. All customer feedback is now gathered from multiple places and classified.

For Polarsteps, a travel app, Ipek pulls support tickets from Zendesk and reviews from the App Store and Google Play. Claude groups them by the underlying need, checks what is already in Linear, and creates or updates the tickets there. A dashboard ranks the needs, shows how each one is trending, and links every report back to its source.

Feedback dashboard in Ipek: 1,410 feedback items grouped into ranked needs, with their sources, report counts and 30-day trends One need in the dashboard: how often it was reported over time, and the customers’ own words, each linked to its Zendesk ticket Workflow on Ipek’s canvas: a Zendesk ticket extractor, a Linear feedback fetcher, a Claude grouping step, and a Linear ticket creator

Compare to legacy tools

Both can automate the job. Here’s where each one lands for the work Ipek is built for.

Capability
Zapier / Make
Ipek Built by your AI, run on your computer
Where the workflow runs
On their cloud. Your data goes there to be processed.
On your machine, in parallel
What each run costs
Every step × every item is a billed task
Nothing. No per-task fee, run the workflow as often as you need
Who builds the steps
Low-code, but you wire up every step
Your AI builds and debugs them, and you can read the code it wrote, which belongs to you now
Your files and your appsFolders on your disk, plus the tools you already use
Great with apps, but cloud-only, so your local disk is out of reach
Both, and finished files land on your desktop
Whose AI account the workflow runs on
Their platform, their billing
Your own AI, like Claude Code, Codex or Cursor. No markup.
Starts without youA schedule, a new email
Many built-in triggers, webhooks, and schedules
Schedules, while Ipek is running on your computer. Email triggers and webhooks are coming.

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 who want to optimize their process: it installs like a normal app, and the AI plans & builds the workflows just for your needs.

FAQ

Which AI do I need?

Any MCP client, such as Claude Code, Codex or Cursor. Ipek has no AI of its own, so it adds no AI costs: you use the plan you already pay for.

Do I need to write code?

No. Your AI writes the workers. You can open any of them and read exactly what it does.

Does my data leave my computer?

Workflows run on your computer and recordings are transcribed there. What your AI reads goes to your AI provider, and a worker that calls an API sends what that API needs.

What does it cost?

Ipek is free. Workflows run on your own computer, so there are no per-task fees.

Does it run when my computer is off?

No. Automations run while Ipek is open on your computer. Running them somewhere else is on the roadmap.

Start building your workflows.

No account or payment needed. Ipek can run on your own machine, offline.

Get release updates.

Be the first to hear about new features, new releases, and Linux support as they land.