I build open-source label software and printer drivers in TypeScript — the thermal-label stack (Brother QL, DYMO LabelWriter, LabelManager, shared contracts & transports) and burnmark-io design tools, plus small shared libraries under mbtech-nl. Everything is MIT-licensed and aimed at people who ship real integrations or print real labels at home and in small businesses.

Why sponsor? Your support pays for time, CI, and hardware: printers, tapes, and odd USB/BLE devices I don’t already own — including unsupported or untested models where the only way forward is to buy the thing and probe it. Sponsorship de-risks that experimentation; it does not magically guarantee every device ends up fully supported, but it makes saying “yes, I’ll try” much more realistic.

Companies: If you rely on this stack commercially, a recurring tier helps keep releases and docs alive. If you need scoped work — a new printer family, a specific feature, or priority support for an integration — that often fits a direct conversation (email + agreement) better than a generic tier alone; get in touch and we can line up scope, timeline, and whether it’s a good fit.

Individuals: A small monthly or one-time tip is genuinely appreciated — think of it as coffee for late-night protocol reads.

Sponsorship helps fund printers, media, and lab gear so drivers and docs are tested on real hardware — including models that are unsupported or untested today. If you have a device you’d love to see supported, a larger sponsorship or a sponsored development conversation is the right path; recurring tiers keep the lights on either way.