FabricvsOpenWork
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Fabric | OpenWork | |
|---|---|---|
| Score | 81/100 | 75/100 |
| Rank in category | #3 of 120 in AI Assistant | #20 of 208 in AI Agents |
| GitHub stars | 44 646 | 24 544 |
| Stars, last 30 days | +407 | +344 |
| Stable releases, 12 months | 131 | 16 |
| Latest release | v1.4.576 · 15 Nov 2026 | v0.18.67 · 13 Nov 2026 |
| Setup | Moderate | Moderate |
| Official Docker image | Yes | Yes |
| License | MIT | MIT |
| Main language | Go | Typescript |
Which one should you pick?
Fabric scores 81/100 against 75/100 for OpenWork, so it is the safer default.
Fabric ships more often: 131 stable releases in the past year, against 16 for OpenWork.
Key differences
- Language: Fabric is written mainly in Go, OpenWork in Typescript.
- Platforms only Fabric lists: Arch Linux, Build from Source, Docker, Raspberry Pi.
- Platforms only OpenWork lists: Kubernetes.
- Features only Fabric lists: Command Line Interface, Custom patterns, Helper apps, Image Generation and 11 more.
- Features only OpenWork lists: Admin control plane (OpenWork Den), AI agents on local files, AI Gateway with access rules and spend limits, Anthropic-compatible plugin import and 10 more.
Fabric details →OpenWork details →
Swap a project
Keep Fabric, compare it with
Keep OpenWork, compare it with