distributed-llama
UNCLAIMEDBy b4rtaz
distributed-llama — Distributed LLM inference. Connect home devices into a powerful cluster to accelerate LLM inference. More devices means faster inference. Listed under Inference engines in the Inference / Serving layer. 4 of 9 comparison attributes are recorded, each with the page it was read from.
Distributed LLM inference. Connect home devices into a powerful cluster to accelerate LLM inference. More devices means faster inference. - b4rtaz/distributed-llama
3 OF 4 SIGNALS HELD · MISSING LOGO
What it runs on, and what runs on it
0 cited edgesComputed from the stack graph, both directions. Every cited edge links the page it was read from; a vendor-added one links the vendor’s own source — this is the reason to be here rather than on the vendor’s own site.
No edges on record for distributed-llama.
Nothing in the directory documents depending on it, and its own docs do not name what it runs on. An edge is only stored when a source states it.
Submit a documented integration →From b4rtaz? No claim is needed for this: a link to your docs that names what distributed-llama runs on is enough.
Open-source signals
A HOLLOW RING IS UNMEASURED, NOT ZERO · WE DO NOT SUBSTITUTE A PARENT COMPANY’S REPOSITORY FOR A PRODUCT THAT HAS NONE
Price
We hold no price for this product.
This is open-source software: you can run it yourself and the licence costs nothing. If the project also sells a hosted service, we do not yet hold the page it prices it on. If that changes — or if you publish /.well-known/pricing.json — it appears here with a capture date.
How we read prices →What its categories ask
4 answered · 5 unanswered9 questions declared by Inference engines. Most rows across the directory read like these.
“Supports Linux, macOS, and Windows. Optimized for ARM and x86_64 AVX2 CPUs.”2026-09-29
“Only the following quantizations are supported #183 : q40 model with q80 buffer-float-type f32 model with f32 buffer-float-type”2026-10-06
A ROW WITH NO ANSWER IS NOT A ROW WITH A “NO” · A VENDOR MAY ANSWER A BLANK ONE, MARKED VENDOR CLAIMED WITH ITS SOURCE · A DOCUMENTED VALUE IS DISPUTED, NOT OVERWRITTEN, AND STAYS VISIBLE WHILE WE RE-READ THE SOURCE
Practitioner reviews
Nobody has written one yet.
A review here is structured, not a star: hardware, scale band, what broke in production, and whether you would choose it again.
NO PERCENTAGE IS SHOWN UNDER FIVE REVIEWS · NO STAR RATINGS, EVER
Also in this category
47 products in Inference engines. Comparison defaults to within the category — pairing this with a GPU cloud would produce a page that means nothing.
Frequently asked
Is distributed-llama open source?
What does a blank mean on the distributed-llama page?
Where do the distributed-llama figures come from?
Can distributed-llama change what this page says?
Something here is wrong — how do I fix it?
Is this listing run by b4rtaz?
Cite this page
A model that quotes us should quote us correctly. The reading and its date sit inside the citation rather than beside it, because a quotation carrying only a URL goes wrong the week the URL changes.
infratoapp, “distributed-llama — Inference engines”, read 23 September 2026. Deployment: self-hosted only as published at github.com. https://www.infratoapp.com/products/distributed-llama
What distributed-llama can and cannot change here
Claiming b4rtaz lets its admins and editors change the tagline, description, logo, docs link and deployment model of every product that org owns — live, labelled as theirs, and logged. Answers to blank questions and dependencies go live too, marked as the owner’s and sourced; a documented answer cannot be overwritten. Everything else on this page is a stated fact with a dispute route: price, licence and OSS figures. Those columns are ungranted at the database level, so they are not a feature we withheld — they are a write that cannot happen. Name, category, website, pricing page and package names can be changed by the owner only through our review. A dispute never deletes a value; it marks it and publishes the correction.
b4rtaz’s website is on shared hosting, so an email address cannot prove who owns it and there is no claim by address. If you maintain it, send a correction with a source.
Maintain b4rtaz? Ask us to verify you.