Contribute
Microbus is open source under the Apache 2.0 license, and the project welcomes contributions of every kind - from a bug report to a pull request to a sponsorship. This page lists the ways you can help and what to expect at each level.
Try It and Send Feedback
The most useful contribution from a new user is honest feedback. Clone the repository, build a microservice, take the agent-guided tour, and tell us what worked, what didn’t, and what surprised you. File an issue for anything that needs fixing or improving.
Bug reports that include a minimal reproduction and the expected vs. actual behavior get triaged fastest.
Spread the Word
Help grow the project’s reach in the Go and platform-engineering communities.
- Star the GitHub repository and ask peers who care about distributed systems to do the same. Stars are not vanity - they are how new readers find the project.
- Talk about Microbus in your team, at meetups, on Hacker News, on Reddit. We don’t pay for clicks; word of mouth is the channel.
- Write about your experience. A blog post about how you used Microbus is more useful than any marketing copy we could write.
Contribute Code
Code contributions are welcome. Reach out before starting a substantial change so we can align on direction:
- Small fixes (typos, doc clarifications, obvious bugs) - just open a pull request.
- Larger changes (new features, architectural shifts) - open an issue first to discuss the approach. Saves everyone effort if the direction does not match where the framework is heading.
- Extensions (new core microservices, alternative LLM providers, integration helpers) - the framework is built to be extended; talk to us about whether your extension belongs in
coreservices/or as a standalone repository under themicrobus-ioorg.
When you do submit a pull request:
- Follow the conventions documented in the agent rules - they describe how Microbus code is structured.
- Include integration tests for any behavior change.
- Keep PRs focused. One change per PR makes review tractable.
- Update
PROMPTS.mdif your change was agent-driven.
Monetary Support
OSS is free, but maintaining it is not. If you’re in a position to help, the project accepts monetary support. Funds go toward maintainer time, infrastructure, and the agent skills that ship with each release.
Sponsorship
Organizations using Microbus in production can explore partnership and sponsorship opportunities directly with the team. Email info@microbus.io to start the conversation. Sponsors get acknowledgement on the project site, input on roadmap priorities, and a direct line to the maintainers.