License overview

Open-source in the repositories

The BrokerBridge retail package is developed in this repository from Hermes Agent. The fork's root LICENSE file (for example MIT, with copyright held by upstream where shown) governs that source tree as published on GitHub. Third parties who receive code under that license obtain the rights and obligations that license grants — we do not replace or erase upstream license terms.

If you redistribute or modify code that is clearly under MIT (or another permissive license), follow the notice and attribution requirements in that license. Where BrokerBridge adds files, check each file or directory for SPDX or license headers.

Subscription, website, and authorized builds

When you use brokerbridge.tech (checkout, account, APIs) or install software we provide through our subscription or authorized channels, your relationship with us is governed by the Terms of Service, including Section 10 (Acceptable Use and Software License) and the End User License summary. Those terms add restrictions on unauthorized redistribution, circumventing subscription or technical controls, and certain uses of our software, branding, and services — separate from the question of what upstream MIT (or other) licenses permit for a given copy of source code.

If you are unsure which license applies to a specific component, check the repository and file headers, or ask us for clarification.

Why this can look like two stories at once

A permissive OSS license (such as MIT) allows broad reuse of that code for recipients who receive it under those terms. Separately, we offer a commercial product and service (subscription, APIs, branding, documentation, and support) with contractual obligations. Your counsel can help you align public-facing terms, repo LICENSE files, and Stripe customer agreements so they are consistent.