CI/CD in your terminal, zero YAML
Details
- External ID
- 47515218
- Source
- HN
- Company
- —
- Product
- CI/CD in your terminal, zero YAML
- Website domain
- zippy.sh
- Launched
- March 25, 2026
- Cohort
- —
- Upvotes
- 7
- Upvotes percentile
- 0.4108241082410824
- Tags
- —
- Fetched at
- Sept. 7, 2026, 9:26 p.m.
- Updated at
- Sept. 7, 2026, 9:26 p.m.
Description
We're two engineers that got fed up with context switching. Why do we need to do a git push, open a browser tab, wait for some task to actually start, bite nails (or read HackerNews) for 10 minutes or more while dependencies are being installed for the 100th time and finally end up with an invalid YAML error. And for some reason this usually happens in the final stage of the pipeline leading up to the inevitable git commits "Fixed", "Fixed again", "Test", "Really fixed this time". We can do better.We set out to build Zippy. A CI/CD system that works from your terminal. No context switching, no slow containers, instant feedback and seamless Claude Code integration. Just git push, instant build, and move on. Two bash scripts, one to setup the (cached) environment, one to run the build process.
Enrichment
- Theme
- self-hosted infrastructure and security tools
- Vertical
- —
- Function
- Workflow automation
- Audience
- Developer
- AI stance
- Not AI
- Project type
- Commercial product
- Normalized one-liner
- ci/cd in terminal without yaml
- Manually corrected
- False
Could you build this?
Partial The client terminal experience is essentially a git remote hook, but the backend requires high-throughput streaming git servers, ephemeral container runners, and multi-tenant isolation.
What it would actually take: The stack needs a custom SSH/Git server (using Go's `crypto/ssh` or custom git-receive-pack hooks) that streams standard I/O directly back to the push client while spinning up ephemeral containers (Docker/Firecracker). The primary hurdles are secure multi-tenant execution sandboxing, real-time bidirectional log streaming over SSH channels without buffer stalling, and aggressive caching of dependency layers across builds. It requires deep expertise in Linux containers, distributed job scheduling, and secure infrastructure operations.
Discussion
5 comments analyzed.
Competitors mentioned: Pre-commit hooks, Traditional CI/CD tools with SSH access
Concerns raised: Unclear how this differs from existing pre-commit hook workflows, Distinction from standard remote CI/CD systems not immediately obvious
Competitors
Other products that read as similar to this one — 211 launches clear the similarity bar, closest 8 shown.
Attention rank: #130 of 212 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).
Launched 146 days after the earliest competitor.
- PipeStep · hn · 2026-03-12 · 12 upvotes · similarity 0.50
- Zetken CI/CD Studio · ph · 2026-09-14 · 3 upvotes · similarity 0.49
- Git-workty · hn · 2026-01-06 · 7 upvotes · similarity 0.48
- I built a visual node system for CI/CD that supports GitHub Actions · hn · 2026-02-10 · 18 upvotes · similarity 0.48
- Volt · hn · 2026-03-10 · 5 upvotes · similarity 0.46
- GitByBit — Git course integrated into VSCode and Cursor · hn · 2026-01-27 · 13 upvotes · similarity 0.46
- Commitdog · hn · 2026-03-02 · 5 upvotes · similarity 0.45
- Ec · hn · 2026-02-04 · 18 upvotes · similarity 0.45
Other launches for this product
- No other launches for this product.