risingsunomi/exo-pt
slowing
significant_divergence
Selected Choose this fork only if you want its alternative backend/platform direction. If you want the current exo experience for local cluster serving, dashboard management, and MLX-based distributed inference, upstream looks like the safer default.
freed-dev-llc/exo-rkllama
active
significant_divergence
Choose this fork if Rockchip NPU support is the requirement; choose upstream if you want the broader, more current exo feature set and the standard MLX-centered experience.
badgids/exo
slowing
significant_divergence
Choose this fork if you want a more opinionated, UI-heavy local cluster build and can tolerate drift from upstream. Stick with upstream if you want the broadest compatibility, freshest fixes, and less risk around removed server/eval paths.
pape12377749/exo
stale
significant_divergence
Choose upstream if you want current exo features and active development. Choose this fork only if AMD GPU compatibility or an older, pinned behavior is the main requirement and you are comfortable owning the maintenance gap.
eclecticc/exo
stale
significant_divergence
Prefer this fork only if its older, home-cluster-focused workflow matches your needs and you are comfortable carrying maintenance risk. For most adopters, upstream looks like the safer choice because it is much more active and materially ahead.
raj-poojary/exo-distributed-inference
stale
significant_divergence
Prefer this fork only if you want a bespoke distributed-inference codebase and are willing to maintain it yourself. If you want current exo features, bug fixes, and lower upgrade risk, upstream is the safer choice.
ranjithrajv/exo-extended
stale
significant_divergence
Prefer this fork only if you need its specific customizations and are willing to inherit maintenance risk. For most adopters, upstream is the safer choice because it is active and materially ahead.
Roxonn-FutureTech/Roxonn-Node
stale
significant_divergence
Choose this fork only if you specifically want the Roxonn node/participation direction and can absorb maintenance burden. If you want the newest exo capabilities and broad compatibility, upstream is the safer choice.
Manish-GenAI/exo
stale
significant_divergence
Prefer this fork only if you specifically need its hardware-compatibility or local-ops changes and are willing to own maintenance. For most adopters, upstream is the safer choice because this fork is materially stale and likely missing many recent fixes and features.
smahtz/exo
stale
significant_divergence
Choose this fork if you want the home-cluster framing plus a few concrete usability and compatibility patches, and you do not need the latest upstream features. Choose upstream instead if you care about active maintenance, new multimodal and dashboard work, or staying close to the current exo codebase.