BloodBank.software

For developers

Build custom blood bank software on BloodBank.software

Open sourceAPI-firstNo lock-in

Skip six months of boilerplate. Start with a working blood bank platform. Customise features, add integrations, deploy for your clients. Full code access, clean REST APIs, direct engineering support, no licensing fees.

BloodBank.software is built for developers who want to build custom healthcare solutions without rebuilding the foundation from scratch. You get complete source code (MIT license), comprehensive APIs, a sandbox environment, and direct access to our engineering team.

We're early-stage and moving fast. No rigid marketplace or plugin store. You fork the code, customise, deploy, and own the relationship with your clients.

Get the code Join Slack
bash
git clone https://github.com/bloodbank-software/core.git cd core docker compose up → blood bank platform running on localhost

What you get

A developer-first platform, not a walled garden

Four things, none of them conditional on a partnership agreement: the code, the APIs, a place to test, and engineers who answer.

01 · Code

Open-source code

Full access, no restrictions

Everything is on GitHub under MIT license.

  • You see the complete codebase — no black boxes
  • Modify anything without asking permission
  • Deploy on your infrastructure, so your clients own their data
  • No vendor lock-in — even if we shut down, you have the code
  • No licensing fees, so you keep 100% of revenue
02 · APIs

REST APIs

Everything is connected

Full API access to the platform

  • Donor management — search, register, track donors
  • Blood inventory — track units from collection to transfusion
  • Blood requests — find compatible blood, allocate units
  • Camps — schedule, manage collections, track analytics
  • Messaging — send targeted communications to donors
  • Audit & compliance — access logs, change history

What you can do with it

  • Build custom dashboards for hospitals
  • Integrate with hospital EHR systems — Epic, Cerner, others
  • Create specialised workflows for your clients' needs
  • Build mobile apps on top
  • Automate anything
03 · Sandbox

Sandbox environment

Test risk-free

A full development environment, ready to break.

  • Sample data included — donors, inventory, requests, camps
  • All features available, so you can test everything
  • No quotas — develop without limits
  • Reset anytime to start fresh for a new project
  • Direct database access (PostgreSQL)
04 · Support

Direct engineering support

Not a support queue

Real engineers, reachable directly.

  • Slack workspace for developer partners
  • Weekly office hours — ask anything
  • Code review for critical implementations
  • Architecture guidance when you hit complexity
  • Response time — under 2 hours for real questions

What you can build

Real use cases — what's actually possible

Three kinds of build on top of the platform, and one business you can build around it.

Custom blood bank modules

Build specialised features your clients need.

  • Rare blood management and tracking
  • Immunology workflows with antibody databases
  • Component-specific tracking for complex protocols
  • Country-specific regulatory modules
  • Hospital-specific workflows for your clients' processes

You own the code, the logic, and the domain expertise.

Hospital system integrations

Connect the blood bank to hospital systems.

  • Epic EHR integration — orders flow in, results flow back
  • Cerner, OpenEMR, or other hospital systems
  • Lab analyser connections for automated test results
  • Device integrations — refrigerators, centrifuges
  • Donor management system connections

Integration takes days via APIs, not months of negotiation.

Regional customisation

Customise for different markets.

  • Localise the interface into any language
  • Adapt to regional blood type distributions
  • Configure country-specific regulations
  • Match local hospital workflows
  • Deploy multiple regional instances from one codebase

One instance for India, another for Brazil, another for Australia — all customised.

Professional services business

Or build the implementation service itself. The platform is the part you don't have to sell, staff, or maintain.

Step 01

Client calls you for blood bank software

Step 02

You deploy BloodBank.software

Step 03

You customise for their workflows

Step 04

You train their staff

Step 05

You provide ongoing support

Step 06

You keep 100% of revenue

3–6 weeksTo deployment, vs 6–12 months from scratch
800+ hoursOf development work already done
ZeroLicensing cost

How to get started

Three simple steps

No approval process, no partner application, no sales call before you can see the code.

Step 01

Get the code

Clone the repository from GitHub. Full open-source codebase, MIT license. No permission needed, no approval process — just clone and start.

Start the development environment locally; the Docker setup is included. You now have a working blood bank platform running on your machine.

bash
git clone https://github.com/bloodbank-software/core.git docker compose up

Step 02

Explore the platform

Use the sandbox environment. See what's possible. Test the APIs, try the admin interface, and understand how blood bank operations work in the system.

Read the documentation. Review example integrations. Understand the data model. Everything is documented.

Step 03

Tell us what you want to build

Email developers@bloodbank.software and describe your idea. Or join the Slack community and ask questions. Or book office hours and talk directly with engineers.

  • We'll answer technical questions
  • Point out gotchas you might hit
  • Help you avoid dead ends
  • Connect you with the right person on our team

Support & community

You have direct access to our team

Three ways to reach a person, and four places to read the answer yourself first.

Slack

Slack community

  • Ask questions, get answers from engineers
  • Share what you're building
  • Get feedback before you deploy
  • Connect with other developers
Office hours

Talk to engineers

  • 30-minute slots with our engineers
  • Ask anything about the platform
  • Discuss your architecture
  • Get feedback on your approach

Tuesdays · 2 PM UTC

Email

Direct email

  • Real engineers, not a support queue
  • We debug with you if needed

developers@bloodbank.software
Under 2 hours, business hours

API reference Complete endpoint documentation Integration guides How to connect to hospital systems Deployment guide How to deploy for production Security & compliance HIPAA, encryption, regulatory

What we ask

Basic expectations for developers

Two things we ask, and one thing we don't. None of it is a contract.

Do your work professionally

Test before deploying. Treat your clients with respect. Follow security best practices. Don't expose APIs to unauthorised users.

Tell us what you're building

So we can help. Share blockers early — we might have solved it already. Report bugs immediately. Ask for help when you're stuck.

No strings attached

  • Use BloodBank.software without being an "official" partner
  • Build for your clients without telling us
  • Keep all revenue from your work
  • Take your code and data with you if you want to leave

FAQ

Developer questions we hear

Licensing, ownership, security, and what happens if we disappear. Answered plainly.

Q01 Can I modify the code for my clients?

Yes. MIT license means full modification rights. No permission needed. Your code is yours.

Q02 Can I charge my clients for deploying BloodBank.software?

Yes. You charge for implementation, customization, support. You don't pay us licensing. All revenue is yours.

Q03 Do you own my customizations?

No. Your code is yours. You own it completely. We only ask you contribute improvements to the core platform back (if you make them).

Q04 What if you shut down?

Code is open-source on GitHub forever. You have the full codebase. You can fork and run it independently.

Q05 Can I white-label this?

Yes. Customize the branding, UI, colors. Your clients see your branding. Under the hood, it runs BloodBank.software.

Q06 How do I contribute to the core platform?

GitHub pull request. We review, test, merge. You get credit in release notes. Community contributors shape the platform.

Q07 What's your security & HIPAA story?

Encrypted data at rest and in transit. Role-based access control. Complete audit logs. Self-hosted means you control the data. HIPAA-ready (your organization handles the administrative controls).

Q08 What happens when you release breaking changes?

30-day notice to all developers. Migration guide provided. We help you update. No surprises.

Q09 Can I integrate with hospital systems like Epic?

Yes. We have APIs. Epic has APIs. Integration is possible. We can help with the architecture.

Q10 How long until I have a working deployment?

For a basic deployment: 1-2 weeks. For a customized deployment: 3-6 weeks. For a complex integration: 6-8 weeks. Much faster than building from scratch.

Q11 Do you have a plugin marketplace?

Not yet. Right now you fork code or build via APIs. Marketplace coming when we understand what developers need.

Q12 How do I get direct engineer access?

Email developers@bloodbank.software and tell us what you're building. If you're serious, you get it. ---

Ready to build

Start with the code. See what's possible.

Explore the platform, test the APIs, and tell us what you're building. Nothing here needs our permission first.

Get the code

Clone from GitHub. Full MIT-licensed codebase, start in minutes.

Join Slack

Developer community. Ask questions, share what you're building.

Book office hours

Talk to engineers. Schedule 30 minutes, ask anything.