What is open source and what is licensed to you

Open-source in the repositories

The BrokerBridge retail package is developed from Broker Bridge 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.

Paid access, website, and authorized builds

When you use brokerbridge.tech (checkout, account, APIs) or install software we provide through paid access or authorized channels, your relationship with us is governed by the Terms of Service, including Section 10 (Acceptable Use and Software License), Section 17A (Prepaid Credits, Payments, and No Refunds), and the End User License summary. Those terms add restrictions on unauthorized redistribution, circumventing activation or payment 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.

Open-source and service licenses

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 (paid access, APIs, branding, documentation, and support) with its own terms. The license accompanying a component defines your rights to that code; our Terms of Service govern use of BrokerBridge services.