A local-first pipeline automation app for developers powered by AI, running natively on your machine. Think of it as a local Zapier or n8n, built specifically for developers who want to chain shell commands, AI calls, HTTP requests, and file operations into reusable pipelines then trigger them on a schedule, on a file change, or via webhook.
Hey PH! 👋 I'm the maker of buildpipe, and I'm really excited to share this today.
The idea came from a simple frustration: I kept writing the same throwaway shell scripts to chain together AI calls, HTTP requests and file operations then losing them, forgetting what they did and rewriting them from scratch. I wanted something visual, local, and fast. No YAML. No cloud account. No vendor lock-in.
So I built buildpipe, a desktop app where you compose pipelines out of typed steps (shell commands, AI calls, HTTP requests, file ops, conditionals, loops, notifications) and wire them together by referencing outputs like {{step_id.output}}. Everything runs on your machine and stays there.
A few things I'm particularly proud of:
🔁 **Triggers** — cron, file-watch, or webhook. Set it and forget it.
✦ **AI Build** — describe a pipeline in plain English and it scaffolds the steps for you.
📋 **48 templates** — from daily standups to Docker health checks, ready to clone.
🔒 **Privacy-first** — no telemetry, no accounts, API keys encrypted.
I'd love to hear what workflows you'd automate first. And if anything feels broken or missing, please tell me. This is v1.0.0 and I'm all ears. 🙏
Local-first pipeline runner is a smart positioning. I've lost count of how many one-off shell scripts I wrote to chain API calls and then forgot where they lived. The {{step_id.output}} referencing pattern feels natural — similar to how n8n handles it but without the cloud dependency. One thing I'd want before adopting: can pipelines be versioned in git as plain files, or is the visual graph the only source of truth?
The file-watch trigger is interesting — curious whether buildpipe can handle asset pipelines where the output is binary files rather than code. For instance, running a font build step that produces WOFF2 files and then pushing them to a CDN as a chained step. Is the pipeline model flexible enough for arbitrary file artifact workflows, or is it currently more focused on shell/AI/HTTP steps?
Hey, congrats on the launch! This might be a dumb question, but does a device need powerful specs to run your app locally?
Multi-step AI workflows are powerful when they include clear checkpoints. Can a buildpipe workflow pause for approval before a step changes code, posts externally, or calls a paid API?
hey buddy! The idea looks very interesting for productivity.
Just my concern for recurring workflows like Hacker News summaries or daily briefings, do you maintain a searchable history of previous runs? For example, if I saw a story in the morning and later wanted to revisit the ai summary or outputs, having run history would be super useful. It is what we usually do.
But at the same time, storing every pipeline output/log long-term could also become a storage challenge locally specially for heavy AI workflows.
A lot of automation effort gets stuck on auth and secrets: how do credentials work in practice (API keys, OAuth flows, rotation, per-project scoping), and what tradeoffs did you make versus hosted tools that can smooth OAuth but require sending data through their servers?
This looks super clean. Love the direction you’re taking with AI workflows 🚀
the AI calls step in the pipeline is the one i'd want to understand better. chaining shell commands and HTTP requests is well-understood territory. adding AI calls introduces non-determinism into the pipeline which changes how you think about error handling and retry logic. if an AI step returns something unexpected does the pipeline fail, retry, or branch? and how do you define what unexpected means for a step that's inherently probabilisti
Nice work keeping this local-first with encrypted keys, that's the trade-off most pipeline tools skip. Good luck with the launch!
About buildpipe on Product Hunt
“Compose, run and automate multi step AI developer workflows”
buildpipe launched on Product Hunt on May 22nd, 2026 and earned 114 upvotes and 21 comments, placing #11 on the daily leaderboard. A local-first pipeline automation app for developers powered by AI, running natively on your machine. Think of it as a local Zapier or n8n, built specifically for developers who want to chain shell commands, AI calls, HTTP requests, and file operations into reusable pipelines then trigger them on a schedule, on a file change, or via webhook.
buildpipe was featured in Developer Tools (513.7k followers), GitHub (41.2k followers), Maker Tools (2.8k followers) and Alpha (10 followers) on Product Hunt. Together, these topics include over 96.5k products, making this a competitive space to launch in.
Who hunted buildpipe?
buildpipe was hunted by Raiyan Yahya. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how buildpipe stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Raiyan Yahya