Оффлайн
- Регистрация
- 1 Мар 2015
- Сообщения
- 1,481
- Баллы
- 155
Hey all,
We recently started working on an API Client - Voiden - and wanted to share it here to get your thoughts and feedback.
Over the past few years, we found ourselves managing way too many tools just to work with APIs: one for api specs, another for docs, a third for tests, etc etc. Eventually it starts to feel more like a performance than actual work.
So we built Voiden: A git-native, extensible, and lightweight client that brings everything—specs, docs, tests, mocks—into one place. No bloat, no lock-in, no "platform overhead." Just structured API workflows that don’t fight your tools or your team.
A few things we care about:
-Reusability and composability : APIs as building blocks, not silos.
-Structure over scatter : everything lives together in one workspace.
-No sign-in required : you can use it without creating an account.
Free and open — we are building this with the community in mind.
Just to be clear: The goal is NOT to replace OpenAPI, but to provide a layer around existing specs that feels coherent, hackable, and friendly to real-world dev workflows.
You can check it out here:
And if you have feedback, suggestions, or just want to follow along:
We are still early, but would love to hear what you think—what you like, what is missing. Appreciate any time you take to try it out.
Nikolas
We recently started working on an API Client - Voiden - and wanted to share it here to get your thoughts and feedback.
Over the past few years, we found ourselves managing way too many tools just to work with APIs: one for api specs, another for docs, a third for tests, etc etc. Eventually it starts to feel more like a performance than actual work.
So we built Voiden: A git-native, extensible, and lightweight client that brings everything—specs, docs, tests, mocks—into one place. No bloat, no lock-in, no "platform overhead." Just structured API workflows that don’t fight your tools or your team.
A few things we care about:
-Reusability and composability : APIs as building blocks, not silos.
-Structure over scatter : everything lives together in one workspace.
-No sign-in required : you can use it without creating an account.
Free and open — we are building this with the community in mind.
Just to be clear: The goal is NOT to replace OpenAPI, but to provide a layer around existing specs that feels coherent, hackable, and friendly to real-world dev workflows.
You can check it out here:
And if you have feedback, suggestions, or just want to follow along:
We are still early, but would love to hear what you think—what you like, what is missing. Appreciate any time you take to try it out.
Nikolas