b3 Bespok3d Beta
GitHub
Beta, on Snapmaker U1 first, then every Klipper printer.

Install what you want. Your printer, your rules.

Some companies decide what runs on your printer. Bespok3d doesn't.
Some "ecosystems" make you trust a server you don't control. Bespok3d doesn't.
Some tools require the terminal, custom firmware, and a lost weekend. Bespok3d doesn't.

An app store and package manager for Klipper 3D printers. Install plugins, adapters, and features with one tap. No terminal, no custom firmware.

✓one tap ✕no terminal ✕no custom firmware

b3 Beta 0.7.4-beta. Free and open source.

All releases and notes · Source on GitHub

In the index today

Everything below installs with one tap from the app. · ·

      Additional project lists

      Separate indexes published by the Bespok3d project, each with its own plugins. Add one in the app to install from it.

        Why this exists

        The plugins are the shelf. You are the store.

        The community already makes remarkable things for Klipper printers — fixes, drivers, whole features. They're scattered across forums, gists and repos, and getting one running usually means SSH, a config file, and an afternoon you didn't plan on.

        Bespok3d is the app and the registry: one place to publish what you made, one tap for anyone to run it. The U1 plugins above are just what's on the shelf so far. What the project is actually for is everything not on it yet.

        Open to all. No gatekeeping, no approval queue, no company deciding what belongs on your printer.

        01 · Publish

        Ship what you made

        If it works on your printer, it can be a plugin. The builder does the packaging; the zero-to-hero guide takes you from a working hack to a published, installable plugin in nine steps.

        Zero to hero → Builder docs

        02 · Adapt

        Bring your printer in

        Each printer needs an adapter teaching the daemon its board, services and modules. We have a Snapmaker U1 on the desk and, sadly, not one of every other Klipper machine ever built. If yours is missing, that adapter is the piece — and we'll help you write it.

        Adapters repo → How adapters work

        Everything is open source, AGPL, and yours to fork. Nothing you publish routes through a server we control.