Skip to content

The operations IDE for founders.

Turn the data scattered across your startup into automated operations. Ipek connects your tools, APIs and files into workflows and dashboards.

See what’s happening and act faster, all in one place:

  • Customer feedback
  • Product analytics
  • Backend observability
  • Lead sourcing and reply drafting
  • News, prices and market watchers
  • Invoice and document analysis

Free · No account · Bring your own AI

PDF API How an Ipek project fits together Your AI (Claude Code, Codex, or any MCP client) builds and revises one Ipek project on your computer. The project holds the Project document with recordings of your work, which your AI keeps current; Workers, code with parameters that reads and transforms data from APIs and your backend; a Workflow that fetches from an API and takes in local files, then transforms, runs an AI step and saves, on weekdays at 09:00; Runs and results with the Project DB; and an Operations Overview dashboard. You observe the dashboard, act on it, and ask your AI for changes. One Ipek project · on your computer Project documentPlanDecisionsOpen questionsRecordingsof your workWorkersCode your AI wroteFetch.ktTransform.kt1val days = param("Days")2val rows = api.get("/tickets")3 .filter { it.age <= days }4save("tickets.json", rows)56ParametersDays7StatusopenSkip dupesReads & transforms data fromAPIsBackendOperations OverviewUser requests248↑ 12%Backend alerts3newNew signups56↑ 8%Failed runs0this weekWorkflowsWeekdays 09:00FetchFilesTransformAI stepSaveRuns & resultsrun_13Running…Succeededrun_12Succeededrun_11PartialProject DB used as steps saves outputs feeds Your AIconnects over localhost MCPClaude CodeCodexCursor, or any MCP client builds the dashboard writes the workers wires the workflow updates project memory observe and act you ask for a change Youreview and decide
1 of 9

Your AI

Claude Code, Codex or any other MCP client on your desktop does the planning and building. Tell it what you want to automate, and it writes the workers, wires the workflow, builds the dashboard and keeps the Project document current.

Project document

One living document for the project: the plan, the decisions you made with your AI, what is built and the questions still open. It is saved in the project on your computer, so it stays when you switch AI clients.

Recordings of your work

Record your screen and talk a task through, or just talk. Speech is transcribed on your computer, and the recording is saved in the project for your AI to use as context. Great for starting a new project or showing what to automate.

Workers

Each worker is a small program your AI writes and compiles. It reads and transforms data: calls an API, queries your backend, parses PDFs and spreadsheets, or asks a model to sort something. It is plain, deterministic code you can open and read, and parameters such as a date range change without touching the code.

Workflows

Workers connect on a canvas into a workflow: this one fetches data from an API, takes in your local files, transforms both, adds an AI step and saves the result. Each step keeps what it produced, API responses too, so when a number looks off you can open the run and see why.

Automations

Ipek runs your workflows on a schedule: every 10 minutes, weekdays at 9:00 or once a week, which keeps your dashboards current. Schedules run on your computer while Ipek is open and your computer is awake.

Runs & results

Every run gets its own folder with each step’s outputs and logs, so you can rerun from any step or debug an earlier run. The Project DB remembers what a workflow already handled, like the tickets it grouped last time.

Dashboards

Results from your workflows are gathered into dashboards, for better observability of your operations. Just ask your AI what you want to see and which actions or triggers you need.

You

Connect the Ipek desktop app to Claude Code or Codex, in their app or your terminal, and drive the whole operation from there.

A command center for your startup

From juggling fourteen tabs, retyping the same AI prompts and double-checking answers that change every time, to one Ipek project: workflows your AI builds once, running the same steps on schedule.

Real jobs, built and run with Ipek

Four projects, with the dashboards people actually open, the workflows behind them, and the notes the AI keeps up to date.

Yeddi YüzQuiz content review

Review and correct content based on user feedback

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

When a student flags a quiz question in Yeddi Yüz, the report lands in PostHog. The workflow picks it up, has Claude check the question against the curriculum notes, and writes the fix straight into the question files. The dashboard shows what changed, which reports were false alarms, and which questions need a human.

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
XMarketingLead generation

Leads found from their posts on X, with replies drafted for review

415 people assessed for about $4. Each one judged from their own profile and posts, at roughly a cent per person in X API reads.

My own marketing for Ipek. Ipek searches X for people describing the automation work it’s built for and reads their profile and recent posts through the official X API, under a spending cap. Claude judges the fit and drafts a personal message. A review desk drafts replies to relevant posts, and another workflow turns industry news into post ideas. Nothing goes out on its own: I read every draft and send it myself.

Leads dashboard in Ipek: a person found on X, why Ipek fits their work, and a drafted message to send yourself (sample data shown) Review desk: a post on X, why it is worth a reply, and a suggested comment waiting for review (sample data shown) Post ideas from public news: the angle, why to post, and a drafted post with its source Workflow on Ipek’s canvas: a feed watcher reads news feeds, a step collects startups and evidence, Claude drafts post ideas, and a validator saves them
PolarstepsCustomer feedback

Customer feedback grouped into product ideas and ranked in a dashboard

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

Polarsteps, a travel app, hears from travelers everywhere: Zendesk tickets, App Store and Google Play reviews. Ipek pulls it all in, and Claude groups it by what people actually need. The dashboard ranks those needs, shows which ones are growing, and links every report to its source, so the product managers can decide what makes the roadmap.

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
StockSentimentMarket research

Stock market data fetched from various sources and analyzed by AI

24× faster. New SEC filings, news and Reddit posts are analyzed within minutes of being published.

My own side project. Every few minutes Ipek collects new SEC filings, news and Reddit posts, Claude scores each one, and the buy and sell calls go into a portfolio priced from a live broker feed. After 72 hours, every call is graded against the S&P 500.

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

Compare to legacy tools

Zapier and Make can automate the job too. Here’s where Ipek differs.

Capability
Zapier / Make
Ipek Built by your AI, run on your computer
Where it runs
In their cloud. Your data goes there to be processed.
On your computer, privacy is in the architecture
What each run costs
Most steps count toward a monthly task or credit limit
No per-task fees. Run it as often as you like
Who builds it
You, step by step in their editor
Your own AI (Claude Code, Codex, Cursor) writes code you can read
Your files and your apps
Great with apps, but your local disk is out of reach
Both. Finished files land in a folder on your computer
Starts without youA schedule, an incoming event
Schedules, webhooks and many app triggers
Schedules, while your computer is awake and Ipek is open. Webhooks & headless on-prem deploy are coming soon
Explore more differences

Plain scripts, n8n, Windmill and Retool too, and how Ipek fits next to Claude Code and Lovable.

FAQ

Which AI do I need?

Whatever you already use: Claude Code, Codex, Cursor or any other MCP client. Ipek has no AI of its own, so there’s no second AI bill. Your AI works on the plan you already pay for.

How is this different from asking my AI for a script?

A script gets you the first run. Ipek is for the hundredth: schedules, a run folder with every step’s output, reruns of just the failed items, a database that remembers what was already handled, and dashboards over the results. Your AI still writes the code, and you can read every line.

Does my data leave my computer?

No. Ipek is a desktop app, so your files, runs and dashboards stay on your computer. Your AI, or a worker that calls an API, sends data only when you ask it to. Ipek’s own anonymous usage stats never include your files or their contents.

What does it cost?

Free. Your workflows run on your own computer, so there’s nothing to meter.

Does it run when my computer is off?

Not yet. Automations run while Ipek is open on your computer. Running them on a server is on the roadmap: subscribe to release updates to hear when it ships.

Download Ipek and connect your AI.

No account, no card. Connect Claude Code or Codex in one click, then describe the job you’re tired of doing by hand.

Get release updates.

Hear when something ships: new features, releases, Linux support. Occasional emails, no spam.