Alternatives
Products that do what Speclify does
Turn messy meetings into real software specifications.
- 1

- 2

- 3

- 4

- 5

- 6

- 7

- 8SS
Hey HN, I'm Samuel, founder of Specfy. Very excited to be launching Specfy, an open source platform to improve the way we talk about infrastructure and technology inside our organizations (https://github.com/specfy/specfy). During my time at Algolia --and previous--, I often felt the communication around production, tech choices and infrastructure was messy at best. Trying to understand how various components came together across teams or sifting through documentation scattered everywhere left me thinking there had to be a better way. Almost nobody, from engineering to…
2023 · github.com
- 9
- 10
- 11

- 12UD
Hey HN! I’m the founder of Unify, and we’ve just released our Model Hub, which provides a collection of LLM endpoints with live runtime benchmarks all plotted across time: https://unify.ai/hub A key finding is that static tabular runtime benchmarks for LLMs simply do not work. It’s necessary to take a time-series perspective, and plot the variations through time. We currently have 21 models provided by: Anyscale, Perplexity AI, Replicate, Together AI, OctoAI, Mistral AI and OpenAI, with more on the roadmap. We test across different regions (Asia, US, Europe), with varied…
2024
- 13

- 14

- 15
- 16

- 17

- 18UA
I've been using LLMs for long discovery and research chats (papers, repos, best practices), then distilling that into phased markdown (build plan + tests), then handing those phases to Codex/Claude to implement and test phase by phase. The annoying part was always the distillation and keeping docs and architecture current, so I built Unpack: a lightweight GitHub template plus docs structure and a few commands that turns conversations into phases/specs and keeps project docs up to date as the agent builds. It can also generate Mintlify-friendly end-user docs. There are other…
Feb 2026 · github.com
- 19
- 20DA
Hi All, API integration often cycles in repetitive use cases, API specs, Libraries/SDKs, developer context & tech support. We are building a desktop app that lets SaaS API sellers design their API integration flow and lets their customer integrate APIs in seconds. SaaS API companies (including our existing customers) resort to: 1. For API documentation - readme.io, Postman and Swagger (few use PDFs too.) 2. For Chat/Support/FAQ - Freshdesk/Zendesk/Calendly/Skype/Teamviewer 3. For Developer Context - IDEs for Android/iOS/JavaScript On top of these…
2017
- 21

- 22

- 23SD
Spec Driven Development approach allows to squeeze more from coding agents thanks to few strong concepts: - decomposition across two dimensions. first you generate specs in multiple steps (requirements, code analysis, design), than you split task into multiple subtasks and implement them one by one - you clear context between every step - after spec generation and after subtask implementation. this helps keep cost low and context clear and focused which boost performance - specs written to disk help with information persistency - delivering specs layer by layer help to catch early when agent…
May 2026
- 24CA
I built this because I was tired of creating pull requests in 20 repositories just to change a single line of workflow job version. With Infra as AI, just mention the change. Agents work on all repos in parallel, read the docs, make a bunch of PRs and fill in the description. You can see the demo of the actual dashboard in the landing. Let me know your thoughts :) It means a lot to me!
Sep 2025 · infrastructureas.ai
Ranked by how close each launch is in meaning, then by votes. Refine with a description →