For business

Support, licensing, custom work.

For print farms, production shops and teams where an outage costs more than a support contract.

Starts October 2026 No seat or printer fees Replies from the maintainer

Commercial support starts in October 2026. Enquiries are open now and being answered in order — we scope it with you over the summer, prepare the contract in September, and the service starts in October. If you need paid support before then, we would rather tell you now than waste your time.

First, the part most vendors leave out

Bambuddy is licensed under the AGPL-3.0. If you run it inside your own business — one printer or an entire floor of them — you owe us nothing. No seat count, no per-printer fee, no licence to buy. That is not a trial or a loophole; it is the licence, and it is not going to change.

So this page is not asking you to pay for permission. It is offering the things an open-source licence cannot give you: someone accountable when a print farm stops printing, a licence that covers redistribution if you need one, and time from the person who wrote the software.

What is actually on offer

Three things the licence cannot give you. Everything else stays free.

Priority support

A named contact and an agreed response time, instead of a queue position behind everyone else's GitHub issue.

  • Direct line to the maintainer
  • Agreed response targets
  • Your bugs triaged first
  • Help with upgrades before you run them in production

Annual or per-incident, invoiced with VAT. From October 2026.

Commercial licensing

Only relevant if you intend to redistribute Bambuddy — ship it on an appliance, resell it, or build it into a product you hand to customers. The AGPL's copyleft terms would otherwise apply to what you ship.

  • Alternative licence for redistribution and OEM
  • Appliance and reseller arrangements
  • Terms that fit your product, not ours

If you only run it internally, you do not need this.

Deployment & custom work

Getting a large fleet onto Bambuddy cleanly, or building the part of it that your operation needs and the community version does not have.

  • Fleet migration and rollout
  • Integration with your MES / ERP / stock system
  • Sponsored feature development
  • PostgreSQL and multi-site setups

Scoped and quoted per project. Available from October 2026.

Who this is for

  • Print farms and production shops running Bambuddy as part of the line
  • Makerspaces and universities with shared fleets and many operators
  • Resellers and integrators who want to ship Bambuddy on hardware
  • Any team where an outage costs more than a support contract

Who you would be buying from

A fair question when the vendor is one person. Here is what is checkable.

Tens of thousands of installations

Bambuddy runs in home workshops, university print rooms, makerspaces and production shops. It is not a product being trialled on you — the code you would depend on is the code all of them already run.

Covered by the press, not by us

Hackaday, the Tailscale blog, MakeUseOf, XDA-Developers, How-To Geek, Fabbaloo, Open Source For You, It's FOSS and Igor's Lab, among others.

See the coverage

Open to inspection, before you commit

Every line of the software is public and AGPL-licensed, the release history is public, and there is a live demo you can use without installing anything or telling us who you are.

The source · The demo · What users say

Your files stay on your network

Bambuddy is self-hosted, and it runs perfectly well with no outbound connectivity at all. For design studios, labs and anyone under an NDA, that is usually the whole question — and it is answered by where the software runs, not by a policy document.

One caveat worth hearing before you ask, rather than after: whether a printer talks to Bambu Lab's cloud is a setting on the printer, not something Bambuddy controls. Bambuddy works fully in LAN-only mode, but putting your printers there is a change you make on the machines themselves.

Talk to us

Tell us how many printers you run and what you need. You will get a reply from the person who maintains the software, not a sales team — because there isn't one. Usually within a working day, and it will be an actual answer rather than a request to book a call.

Prefer email? business@bambuddy.cool  ·  Just want to support the project instead? See the sponsor tiers.