MechAMS started as one mechanism for one printer. Where it goes next — new printers, new mods, new integrations, weird and wonderful things we haven’t imagined — is on you. Ship something. We’ll pay for it.
These are the things we want built. First valid submission gets paid. Reward, scope, and acceptance criteria are on each listing — or message us to negotiate before you start.
Adapt MechAMS to any printer that isn’t the Bambu A1 — mounting, G-code, slicer profile, the works. Reward scales with the printer’s install base and how clean the port is. A1 Mini is the most-wanted right now.
No accounts, no gatekeeping, no 47-page contributor agreement. Email-first, human-reviewed, paid quickly.
Claim an open bounty, or propose your own build. Either works.
Make the thing. Test it on real hardware. Document it well enough that we (and others) can verify it works.
Email us the build, the docs, the demo, and the reward you want. We reply within a few business days.
We test, agree on terms if needed, and pay. Then we feature your work on the gallery.
Five lanes. Pick one, mix several, or invent your own — we’re open to anything that makes MechAMS more useful, more interesting, or more fun.
Make MechAMS work on a printer it doesn’t support yet. Brackets, firmware tweaks, slicer profiles, G-code macros. The strategic stuff — and the highest payouts.
Functional upgrades on top of MechAMS — alternate nozzles, filament-runout sensors, lighting, sound dampening, drybox integrations, custom enclosures. Make it better than we shipped it.
Animatronic figures, kinetic sculptures, color-changing displays, stop-motion rigs — anything visual or moving that uses MechAMS as the engine. Show us what we didn’t imagine.
Plugins for OrcaSlicer, Bambu Studio, OctoPrint, Klipper, Home Assistant, Discord. Expose MechAMS to whatever stack people already use.
Find a bug. Or better, fix one. Mechanical, firmware, software, slicer profile — anything that’s broken or could be sturdier. Paid by severity.
Pick what works for you. Mix and match if it makes sense. If none of these fit, propose something better — we’re flexible.
Fixed price tag on the challenge. First valid submission gets paid. Predictable, fast, no fine print.
If your work ends up in our store or generates downloads, you get a cut. We agree the split before you start.
Free MechAMS units, parts, or credit toward future kits. Useful if you want to keep building.
Front-page slot on the gallery, social spotlight, blog post, sponsored content. Cheap for us, valuable if you’re building an audience.
Got a better idea? A licensing deal, a co-branded release, a sponsorship trade? Tell us what you want — we read every proposal.
Community work, ports, mods, weird experiments — once people start shipping, they’ll show up here with credit and a link back to the maker.
We’ll feature the first ten community submissions on the homepage and across our channels — free promotion on top of whatever reward you negotiate.
Get featuredFor now, submissions go through email. We read every one and reply within a few business days. Tell us what you built (or want to build), which category it falls in, and what kind of reward you’re after.
Depends on the project. For paid bounties we usually take ownership or an exclusive license, since you’re being paid up front to build something we asked for. For everything else — unsolicited mods, creative builds, integrations — you keep ownership and grant us a license to host, promote, and (if relevant) distribute it. We agree the terms before you ship anything. No surprises.
Bank transfer (SEPA) or PayPal for cash. Store credit is applied to your account instantly. Hardware ships when ready. We can usually accommodate other payment methods on request — just say so when you submit.
Right now: us. We read everything, reply within a few business days, and ask follow-ups if needed. As volume grows we’ll bring in trusted community testers — with credit and compensation.
Each bounty has acceptance criteria printed on it. In general: it works reliably, it’s documented well enough that someone else can use it, and it doesn’t void anyone’s printer warranty unless that’s explicitly the point. We test before we pay.
Yes. If you spot something we should be paying for — a port, a fix, an integration — pitch it. Tell us what it is, why it matters, and what you’d want for it. Worst case: we say no. Best case: it lands on the bounty board with your name on it.
You’re responsible for taxes in your own country. We’ll send the paperwork our side requires (invoice template available on request). If you’re an EU business with a VAT number, reverse charge applies.
Community contributions are provided as-is. We don’t cover damage to printers, prints, or property caused by community work. If your build involves anything spicy (high temperatures, mains voltage, moving parts under tension), document the safety considerations. We won’t feature work that’s unsafe by design.
Not by default. Open-source contributions are welcome and we’ll feature them prominently, but it’s your call. Some bounties may require an OSS license — it’ll be on the listing.
Absolutely. The Creative Builds category exists for makers, artists, and content creators. Documentation, tutorials, translations, and community videos are also rewarded — reach out and tell us what you’re working on.
The Launchpad is here so you don’t need our blessing to make MechAMS your own. Build it, ship it, get paid.
