bre.ad

What It Is

Bread is an open-source project donation tool provided by Andrew Baxter, LLC. Its core goal is to “donate a little to a lot of open source projects.” Donors can create an account, select multiple projects, and have their monthly donation amount distributed across those projects according to configured weights. Project maintainers can create an account, copy their account ID, and add a .bread.yml file to their project to declare the receiving account and dependency project weights.

Core Features and Payment Aspects

In terms of service type, Bread is closer to a donation distribution platform for the open-source ecosystem than a general-purpose payment gateway. It supports donations via project URLs and also allows websites to add a Donate button. Its key feature is weighted allocation: donations can be assigned either to accounts or to project URLs such as GitHub and GitLab, making it suitable for passing funding through to multiple dependency projects in the open-source supply chain. The main content mentions “Set up payments” and monthly donation distribution, but does not disclose the specific supported payment methods, countries covered, fees, currencies, or settlement timelines, so its payment-related commercial information is limited.

API, Integration, and Automation

Bread provides a REST API, though the documentation clearly states that its current capabilities are limited. API requests require a Bearer Token, with permissions controlled via scopes. Existing endpoints include GET /api/account_get_donate_weights for reading an account’s donation weights, and POST /api/account_set_donate_weights for replacing the current donation weights. On the project side, maintainers can use .bread.yml to configure the receiving account and project weights, and can try using bread-scan to generate the configuration automatically. Overall, the integration threshold is relatively low.

Pricing, Compliance, and Risk

The collected content does not provide rates, platform service fees, payment processing fees, or withdrawal costs. It also does not explain fund custody, licensing, KYC/AML, refunds, chargebacks, or risk-control mechanisms. The page only includes links to Terms of Service and Privacy Policy. As a result, Bread has relatively weak transparency from a financial payments evaluation perspective, and it is not suitable for handling high-value or enterprise-level compliant donation workflows without further due diligence.

Pros, Cons, and Best-Fit Users

Bread’s strengths are its clear positioning, open-source-friendly design, simple configuration, and support for weighted distribution across multiple projects. Its weaknesses include limited disclosure around payments and compliance, narrow API coverage, and limited service support information. It is better suited to individual developers, maintainers of small open-source projects, and users who want to support multiple open-source dependencies on a monthly basis. The main content does not mention accessibility from China; network connectivity, payment availability, and local alternatives should be tested separately. Alternatives such as GitHub Sponsors, Open Collective, and Liberapay are also worth evaluating.