Partner with us
Partner with BloodBank.software
One open-source blood bank platform. Many ways to build on it — deploy it, integrate it, advise on it, test it, or make it work in your language and your regulations.
No applicationNo certification gateNo approval queue
The invitation
The software is free. The opportunity is open.
BloodBank.software is open-source, self-hosted, and free to use. Partnership here isn't a licensing arrangement, because there is nothing to license. It's about the work that surrounds the software.
Blood banks and hospitals need people who can deploy it, connect it to their EHR, validate it for accreditation, adapt it to local regulations, and support it long-term. That work is real, it's paid, and it's yours to own. We don't compete with our partners for it.
This page just tells you where you'd fit and how to reach us.
Find yourself below.
Where you'd fit
Nine ways to work with us, in three groups
Build a business on the platform, run it in a real operation, or make the platform itself better. Most partners are in exactly one of these.
Build a business on the platform
3 rolesImplementation & development firms
Deploy, customise, and support BloodBank.software for hospitals and blood banks in your region. Zero licensing cost to pass through, and 800+ development hours saved per deployment.
Healthcare software integrators
Connect blood banks to Epic, Cerner, OpenEMR, and lab analysers using our REST APIs and HL7/FHIR support. Integration work without a six-month, $500K project behind it.
Independent consultants & advisors
Advise blood banks on system selection, workflow design, and compliance readiness — with a platform you can actually recommend, demonstrate, and shape.
Deploy it in a real operation
2 rolesBlood banks & blood centres
Commercial or non-profit. Run the platform on your own infrastructure, influence the roadmap directly, and become a reference deployment others learn from.
Hospitals & transfusion services
Bring transfusion workflows, inventory, and compliance into one self-hosted system that integrates with the EHR you already run.
You probably want a demo firstStrengthen the platform
4 rolesClinical & domain advisors
Transfusion medicine physicians, quality managers, and regulatory specialists who can tell us where our workflows diverge from real clinical practice.
QA & validation professionals
Test the platform against real-world edge cases and help build the validation documentation blood banks need for accreditation.
Localisation & regulatory volunteers
Two kinds of localisation: translating the interface, and mapping the platform to your country's blood banking regulations. The second is rarer and matters more.
Open source developers
Contribute code, review pull requests, and build modules on top of the core.
See Grow with usWorking with our team
Don't want to partner? Hire us.
Not every organisation wants to build the capability in-house. Some just want the system running, configured to their operation, and supported.
That's a service we provide directly. The same team that builds the platform does the implementation, so there's no handover between the people who wrote it and the people deploying it.
Depends entirely on scope, scale, and how much integration is involved. There's no price list, because a single-site blood bank and a five-hospital network aren't the same project. Tell us what you're running and we'll scope it honestly.
What we take on
- Full deployment on your infrastructure
- Configuration to your workflows, forms, and reporting requirements
- Data migration from spreadsheets or legacy systems
- EHR, HIS, and analyser integration
- Staff training and go-live support
- Ongoing maintenance and support contracts
Full implementation, handled end to end.
Describe your operation. We'll scope it and send you a real number.
Start the conversation
No application. No approval to wait for.
This form just tells us who you are and what you have in mind. If you'd rather email, or you're mid-deployment and something is broken, say so in the message and we'll move faster.
- Response time
- 2 business days
- Partner fee
- None
- Revenue share
- None
- Minimum commitment
- None
- Approval needed
- None
Typical response time: 2 business days. Faster if you're mid-deployment and something is broken.
Message received
We'll reply within two business days. If you're mid-deployment and something is broken, email us directly and we'll move faster.
FAQ
Common questions about partnering
Cost, approval, pricing freedom, white-labelling, and what AGPL actually means for an implementation partner.
Q01 Is there a formal partner program or certification?
Not yet, and that's deliberate. A certification programme would mean gatekeeping access to software that's open by design. What partners get instead is direct access to the core engineering team — no channel manager, no tier system. If a formal programme makes sense later, existing partners will help shape it.
Q02 Do we need approval to deploy this for clients?
No. The code is open source. You can clone it, deploy it, and bill your client today without telling us. We'd rather you did tell us — we can help, and we'd like to know where the platform is running — but permission isn't required.
Q03 What does it cost to partner?
Nothing. No partner fee, no revenue share, no minimum commitment. We make money from our own implementation and support work; you make money from yours.
Q04 Can we set our own rates for implementation and support?
Yes. Your pricing is entirely yours. We don't set floors, ceilings, or reference rates, and we don't take a cut.
Q05 Can we white-label or rebrand the platform?
Partly, under the default licence. BloodBank.software is released under AGPL-3.0 with one additional attribution term: every deployment must display "Powered by BloodBank.software" with a link to our site, visible in the interface. You can apply your own branding, colours, and client-facing name around it — you just can't remove that notice.
If a client needs a fully white-labelled deployment with no attribution, that's available under a commercial licence. One fee, per deployment, and the attribution requirement is lifted. Get a custom quote and tell us the deployment you have in mind.
Q06 What does AGPL mean for us as an implementation partner?
In practice, very little. Deploying the platform on a client's own infrastructure is exactly what the licence is designed for — your client already has the source, so there's nothing extra to disclose. The obligation only bites if you modify the code and offer it as a hosted service to third parties, in which case your modifications need to be published. If that's your model, talk to us about a commercial licence instead.
Q07 What support do partners get?
Direct technical contact with the engineering team, help with integration and deployment questions, early visibility into roadmap changes, and input on features your clients need. What we don't provide is first-line support to your clients — that relationship stays yours.
Q08 We're a hospital, not a services firm. Is this the right page?
Probably not — you likely want a demo rather than a partnership conversation. Request a demo and we'll walk through the platform against your workflows. Come back here if you decide you'd rather have us implement it for you.
Q09 How do you handle regional regulatory differences?
The platform is configurable rather than hard-coded to one regulatory regime. Compliance rules, audit trail requirements, reporting formats, and master data can be adapted per region. Where a country's requirements need deeper work, that's exactly what our regulatory localisation partners take on.
Q10 What if we want to contribute code rather than deploy?
That's the Grow with us path — repository access, API documentation, a sandbox environment, and direct engineering support for contributors.
Q11 How quickly do you respond?
Two business days for most enquiries. Faster if you're mid-deployment and something is broken.
Related
If this wasn't quite the page you wanted
Developers want the first one. Blood banks evaluating the platform want the last one.