{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicuzzoh2moxv7tfcjff4weue7qc4au6jnm52sh4bk5solxfbstl4m",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mlv43mzexp22"
  },
  "path": "/t/i-built-a-dockerized-way-to-run-open-source-ai-media-workflows-without-fighting-local-dependencies/176032#post_1",
  "publishedAt": "2026-05-15T08:15:42.000Z",
  "site": "https://discuss.huggingface.co",
  "tags": [
    "Openfork.video"
  ],
  "textContent": "Hey everyone,\n\nI’m building OpenFork because I kept running into the same boring wall when testing new AI video/audio/image workflows: CUDA issues, Python packages fighting each other, custom-node conflicts, huge model downloads, and the fear of breaking a ComfyUI setup that already works.\n\nOpenFork is my attempt to make that part calmer.\n\nIt’s an opensource desktop client and python client + web workspace that runs AI media workflows in prebuilt Docker containers. The goal is simple: pick a workflow, let the client pull the right image, run it on your NVIDIA GPU, and send the result back into your project. No configuration needed.\n\nThis is a curated database of opensource ai models and automation. I’m trying to make fast-moving workflows easier to test without spending the evening fixing the environment.\n\nDemo:\n\nOpenfork.video\n\nWebsite/download:\nwww.openfork.video\n\nI’d love early testers, especially people who already run WAN/LTX/Hunyuan/HeartMuLa/Qwen/Z-Image style workflows and can tell me where this still feels rough.\n\nIf you try it, the most helpful feedback is:\n\n  * your GPU/VRAM\n  * Windows/Linux setup\n  * workflow you tried\n  * where it broke, confused you, or saved time\n\n\n\nI’ll be around in the comments and I’ll turn the first real issues into fixes/docs.",
  "title": "I built a Dockerized way to run open-source AI media workflows without fighting local dependencies"
}