Blu and BroadBuilder
Blu is a BroadBuilder project designed to connect donors with reviewed individual recipients through small, person-to-person gifts. Its purpose is to give the person, their current needs, and the limits of the available information a clear place in the giving decision.
A person at the center of the decision
Blu is intended for people considering a small gift to another individual, and for people seeking support for everyday needs. The design starts with a recipient profile and context about needs such as groceries, transport, or school materials.
For a donor, the useful questions are who the profile represents, what has been reviewed, and what is still uncertain. For a recipient, the aim is to explain a need without making sensitive personal evidence part of a public story. The About Blu page describes this people-first purpose.
BroadBuilder’s design and development role
BroadBuilder is behind Blu’s design and development. The approach is to make the context of a possible gift understandable before asking someone to act: the individual’s story, the information reviewed, and the qualifications attached to an impact estimate.
That approach also means distinguishing intended features from what is currently available. Blu’s giving journey is a product design, not evidence that money is moving. Read BroadBuilder’s Blu project overview for the relationship between the platform and its builder.
Review and privacy have clear limits
Blu’s profile model uses a first name and last initial for public identity. Private verification documents and payout details are outside public discovery. Human review is part of the intended moderation process; a reviewed signal does not guarantee a person’s circumstances or a future outcome.
Impact labels are dated local estimates. Prices and how a recipient uses support can change. Recipient updates describe what the recipient reports, rather than independently audited results. Read Trust and safety and the privacy information to understand these boundaries.
Current status: payments disabled
Donations and payouts are currently disabled. Blu does not have an approved production payment provider. Checkout and payouts must remain unavailable until written provider approval and end-to-end verification are complete.
You can read how Blu is designed to work to understand the proposed giving journey. Descriptions of gifts, checkout, or recipient support explain the platform’s purpose; they are not confirmation of live donations, completed payouts, or available funding.
Current product brief
Blu’s current public product is a responsive web experience with donor and recipient account paths, a private recipient application, a human-moderation workflow, privacy-safe public profile fields, qualified local impact estimates, donor records, and recipient-reported updates represented in the product design.
That description is a product brief, not a statement that every journey has completed with real users or real money. Public recipient inventory requires a consenting person who has completed review. Live donations require an approved provider and production proof.
Current release gates, without promised dates
The next gates are to publish only approved recipient profiles, obtain written payment-provider approval for Blu’s exact person-to-person model and launch markets, verify authentication and staff controls, and prove the payment, webhook, ledger, refund, dispute, and payout lifecycle end to end.
Blu does not publish a promised date for those gates. Earlier whitepaper or roadmap language about fees, payment providers, blockchain, tokens, a DAO, nonprofit status, donation volume, countries, or completed phases is not current product evidence.