Pay-per-seat works well when no proper competition to go against it.
What we built with http://voiden.md should be free forever, with monetization on plugins, but only the ones that introduce costs to the team.
The blessing was that the team was already profitable on another tool, and VC-independent, so nobody shoved some dumb design decisions down anyone's throat.
I mean, isn't that a good thing?
At least there won't be any security concerns during the outage. (:
People are just used ot it. Even with all the bloat. I'm helping up the http://voiden.md folks in an attempt to build an actual API devtool, not a tab+click API SaaS platform.
A helping hand to Ebiose AI here.
I’m super excited to see the project go open source.
There is already some literature about improving agents through the evolutionary process (not only AlphaEvolve). And others are talking about AIs that build other AIs, which is sometimes called ADAS, for Automatic Design of Agentic Systems.
We have already experienced this, notably on math problems.
But here, with the community, the goal is really to trigger the self-improving process.
The only way to do so is to challenge Ebiose with real use cases so that reusable agent components emerge organically and evolve over time.
TL;DR Voiden, a free, offline API workspace, decided to say no to SaaS "Teams" features because they're:
1) bloated,
2) expensive, and
3) break developer workflows.
Git is the real collaboration engine. It's free, familiar, and tied to your codebase.
Much appreciate the feedback! Took it to the team already. I waited to get a confirmation for your question before answering, so here it is: it's built on top of tiptap + codemirror.
You almost had me until the "5px font" line, then it just went into waffle territory.
As for the Hurl comparison: that’s like saying Hurl is the same as Bruno, Yaak, and the rest of the crew - if aiming there, sure. Voiden isn’t a themed CLI, so visually it’s not even in the same category. And functionally, the whole point is having docs, tests, and the spec all in one place. That's something CLI tools don’t really aim to solve.
Some overlap in request-sending, sure, but very different purposes.
It's text-based no? So more like Hurl than Yaak? Or is it more like a notebook?
Yes I would say presenting your software with tiny full-screen screenshots of your IDE where you can barely see the code, rather than code snippets, is very telling. I can right click them and "open image in new tab", but that is the only way to get a sense of the program from the "features" page, other than the GIF on the landing page.
Compare with the Hurl landing page, I immediately know what this does and how it's used: https://hurl.dev/
Pay-per-seat works well when no proper competition to go against it. What we built with http://voiden.md should be free forever, with monetization on plugins, but only the ones that introduce costs to the team.
The blessing was that the team was already profitable on another tool, and VC-independent, so nobody shoved some dumb design decisions down anyone's throat.