Show HN: Floneum, a graph editor for local AI workflows (floneum.com)
Floneum is a graph editor for local AI workflows. The project focuses on ease of use and community made plugins. The application is a single executable with no dependencies you need to install. You can extend Floneum with WASI plugins that run in a environment that is issolated from your system so that you can use untrusted community plugins without worrying about malware. It uses llamma.cpp to run large language models locally, and wasmtime to run issolated plugins.
If you are interested in the project, consider joining the discord, or building a plugin for Floneum in rust using WASI
Download: https://github.com/floneum/floneum/releases/tag/v0.1.0
Join the discord: https://discord.gg/dQdmhuB8q5
Build a plugin: https://floneum.com/docs/developer/index
17 comments
[ 2.2 ms ] story [ 52.8 ms ] threadOnce Floneum is more complete, the target users are any non-develper professionals with repetitive tasks. It should serve to automate tasks that are difficult to monetize either because the task itself is too specific to you (like cross refrencing your Google calendar with any events discussed on your corporate slack channel to see if they conflict or watching for any new novels that are about magical worlds by authors that have a terse writing style) or tasks that are too small to pay for by themselves (for example searching a schools class listing and finding the teachers that fit best with a specific students needs). The first example would also benefit from the fact that Floneum runs models entirely locally. (You wouldn't want to send your corporate chat to Open AI)
- Cross referencing your Google calendar with any events discussed on your corporate slack channel to see if they conflict - Watching for any new novels that are about magical worlds by authors that have a terse writing style - Finding classes with teachers that fit best with a specific students needs
Each of these would be difficult to monetize, which is why Floneum is targeted at consumers directly with sharable workflows.
The documentation looks a bit lacking, and maybe my questions are answered somewhere and I just couldn't find them.
Can I call a flow via an API, or turn one into an API endpoint? If not, is it theoretically possible to add with a plugin, maybe via API request and response nodes? This is the primary feature that would make it practical for me.
Currently, requests are limited to simple GET requests from Floneum to a endpoint. In the future I would like to support more methods that would make implementing this as a plugin possible. WASMtime is still in the process of implementing the stream API, which would make implementing this much easier.
2. On a first glance, this looks a bit like LangFlow. I guess this is different, but how?
3. Is this freemium, or fully running stand-alone as OSS?
2. There are a few differences: a) Floneum doesn't require any setup. No need to install python, cuda, or pop. Just download the executable and run b) It has first class support for quantized local models c) It supports fully issolated WASM plugins (not arbitrary python code)
3. Floneum is fully Open Source!
https://github.com/underlines/awesome-marketing-datascience/...
Ex: input speech, convert to text (with any s2t), analyze the text and write an answer(with any LLM), text2speech(with any t2s), all this from a no-code UI. And generate an API where I can just send an audio file, and retrieve the audio answer.
It is a bit different from Flowise because it is focused on end users building workflows instead of companies building on top of Flowise. Because Floneum is focused on non-technical end users, we also have a fully sandboxed plugin system and require no external dependencies like python/npm to get started
This is exactly what we are trying to achieve with Ultraforge: https://www.filterforge.com/ultraforge/
It will be focused on images at first, but if it takes of, nothing prevents us from adding other types of nodes (audio, etc.)
I think graphs + AI is going to be the future, but there's no direct path to market, the landscape is shifting incredibly quickly, and I'm still not sure of the actual use cases that aren't slightly weird pictures and chatbots.
https://docs.anyassistant.ai