Skip to main content

What Cobblr connects to

A directory of the integrations that ship today, grouped by what they're for. Non-exhaustive by design: drivers and sources are installable, so the list grows without waiting for a Cobblr release.

Machines (digital fabrication)

Digifab talks to a machine's own firmware or manager:

  • Direct to firmware: Duet (RRF), Klipper (Moonraker), OctoPrint, PrusaLink, FluidNC, Elegoo (SDCP), Bambu (cloud, and LAN via the edge bridge).
  • Farm managers: FDM Monster.
  • Home Assistant, for driving what HA already controls.
  • LightBurn, via the edge bridge on the PC it runs on.
  • Print-failure detectors: PrintGuard, Obico (ML API), your AI provider's vision, or any local HTTP scorer, watching a camera (Cobblr's frames or the detector's own) and pausing on a suspected failure.

Machine drivers are declarative manifests you can install, and the edge bridge has its own MIT-licensed driver set for hardware Cobblr can't reach directly.

Syncing records in

Sync sources mirror another system's records into a workspace: Ravelry (yarn) and Homebox ship as built-in sources, and a source is an installable manifest, so any system with an API is fair game. Spoolman connects on the inventory side to keep filament stock in step. One-shot imports exist too: BrickLink (wanted lists and order history), and CSV import/export on inventory and locations.

Telling you things

Notifications reach in-app and browser push out of the box, and integrations carry events out to Slack, Discord, email, and any webhook, with a generic HTTP-out connector as the escape hatch.

AI providers

Bring your own: OpenAI, Anthropic, Ollama, any OpenAI-compatible endpoint (LM Studio, vLLM, llama.cpp), or a model on your own machine over the edge bridge.

Scanning lookups

Barcode resolution consults public catalogs, each individually switchable: go-upc (with your API key), upcitemdb, the Open Food / Products / Beauty Facts trio, and a web-search fallback.

Everything else

  • Paper printers over CUPS/IPP (document printing).
  • Backup destinations: local filesystem, Google Drive, any S3-compatible bucket (backup).
  • Your own Claude over MCP, and anything else over the REST API.