HCB: A Rails-Based Fiscal Sponsorship Platform Built for Hackathon Finance

What HCB Actually Solves

HCB solves a specific problem: high school hackers and creative clubs need to accept money without forming their own nonprofit. Hack Club itself runs a fiscal sponsorship program, and HCB is the software behind it. The platform gives each organization a restricted fund backed by Hack Club's 501(c)(3) status. That means a local hackathon can collect donations and pay expenses legally, without incorporating. The intended users are clear: hackathons, Hack Clubs, and robotics teams. This is not a generic crowdfunding tool. It is a purpose-built system for youth-led tech events that need a financial shell.

The Architecture: A Rails Monolith for Money

The repository is a Ruby on Rails application. The README does not list specific gems or services, but the structure implies a classic Rails monolith: models, controllers, views, and background jobs. The platform handles funds, transactions, and probably invoices, though the README does not enumerate those features. What is visible is the integration with Hack Club's fiscal sponsorship program. HCB is not a standalone product; it is tightly coupled to Hack Club's legal entity. That coupling is the core mechanism. A restricted fund is created under Hack Club's 501(c)(3), and HCB manages the money flow. The documentation folder, dev-docs, likely contains the schema and data flow, but the README only links to it.

Getting It Running: Three Paths, One Documentation File

The README points to a single file, dev-docs/development.md, for setup. It lists three supported environments: Codespaces, Docker, and native setup. That is the entire instruction set in the README. There are no commands shown in the README itself. To run HCB, you must open that documentation file. The lack of inline commands is a minor friction point. A developer scanning the README cannot start immediately. They have to click into the dev-docs folder. Once there, likely there are bundle install and rails server commands, but the README does not show them. This is a documentation style choice that favors thoroughness over quick start, but it slows down evaluation.

Security Reporting and Bounty Program

The README dedicates a section to security vulnerabilities. It asks reporters to email [email protected] and points to security.hackclub.com for bounty details. This is a positive sign for a financial platform. Handling money means handling sensitive data, and a clear reporting channel is essential. However, the README does not describe any security features, such as encryption, audit logs, or two-factor authentication. Those may exist in the codebase, but they are not documented in the README. If you are evaluating HCB for your own use, you need to inspect the code or the dev-docs to see what protections are in place.

The AGPL-3.0 License: A Real Constraint

HCB is licensed under AGPL-3.0. This is a strong copyleft license. If you modify the code and run it as a network service, you must release your modified source code to users. For a fiscal sponsorship platform, that has implications. If a nonprofit or company forks HCB and adds proprietary features, they cannot keep those changes private if they serve users over a network. This is a deliberate choice by Hack Club to keep the platform open. For a small hackathon team, this is likely irrelevant because they will use HCB as-is. For a commercial entity, it is a deal-breaker. The license also means you cannot embed HCB in a closed-source product without violating the terms.

Maintenance and Upgrade Cost

The latest default-branch commit visible on 7 November 2026 was dated 6 November 2026. Check current history and security advisories when evaluating maintenance. The README mentions a Slack channel, #hcb-dev, for contributor support. That suggests an active community, but the absence of release tags is a gap. For a financial platform, regular updates matter. Security patches and bug fixes are critical. If the project does not tag releases, you cannot easily track versions or know when a fix is applied. You would have to follow the main branch. That is a maintenance cost: you either run a moving target or you pin a commit and miss updates. The AGPL-3.0 license also means you must provide source code to your users if you run a modified version, which adds compliance overhead.

The Wrong Tool for General Fundraising

HCB is not a general donation platform. It is tied to Hack Club's fiscal sponsorship model. If your organization is not a hackathon or a youth tech club, or if you already have your own 501(c)(3), HCB offers little. The restricted fund is the core value, and that fund is backed by Hack Club's legal status. You cannot use HCB to spin up a fund under your own entity without significant modification. Also, if you need features like recurring donations, donor management, or event ticketing, HCB may not have them. The README does not list any of those. A real alternative is a platform like Open Collective, which also provides fiscal sponsorship but is designed for a broader range of projects and has a different legal and funding model. Open Collective lets you create a collective under an existing fiscal host, and it handles payments, invoices, and transparency dashboards. The difference is that Open Collective is a multi-tenant platform, whereas HCB is a single-tenant Rails app meant to be run by Hack Club or a similar host.

Editorial conclusion

Adopt HCB if you run a hackathon, Hack Club, or robotics team that needs a legally backed restricted fund and you are comfortable with Rails and AGPL-3.0. Do not adopt it if you need a general-purpose donation platform or if you cannot commit to the license's copyleft terms. Before deploying, verify your own nonprofit status and check the development documentation for the exact setup steps, since the README only points to that file. Also confirm how HCB handles bank integrations and tax reporting, because the README does not describe those details.

Frequently asked questions

Official sources

1. Official documentation
2. Official README
3. Project repository