a2ally™ Sign up

Apache 2.0 vs BSD 3-Clause: what is the difference?

Last updated

TL;DR: Apache 2.0: commercial use, modification, redistribution: Yes. BSD 3-Clause: the same uses: Yes. Apache 2.0: Use, reproduce, modify, sublicense and distribute for any purpose, with an express patent license; keep notices, include the license and mark changed files. BSD 3-Clause: Redistribute and use with or without modification, keeping the notice, conditions and disclaimer; contributors' names may not be used to endorse your product.

Is apache 2.0: commercial use, modification, redistribution allowed under Apache License 2.0?

Yes. Every use you described is granted by Apache 2.0, and nothing you described is prohibited.

License: Apache License 2.0 (Apache-2.0, curated)

Duties: attribution, license_notice, state_changes

Is bSD 3-Clause: the same uses allowed under BSD 3-Clause "New" or "Revised" License?

Yes. Every use you described is granted by BSD 3-Clause, and nothing you described is prohibited.

License: BSD 3-Clause "New" or "Revised" License (BSD-3-Clause, curated)

Duties: attribution, license_notice, no_endorsement

How do Apache-2.0 and BSD-3-Clause compare?

The table lists each license's duties and notes side by side.

LicenseDutiesNotes
Apache-2.0attribution, license_notice, state_changesIncludes an express patent license that ends for anyone who sues over patents in the work (section 3). Does not grant rights to the licensor's trademarks (section 6).
BSD-3-Clauseattribution, license_notice, no_endorsementSublicensing is not mentioned, so it is not treated as granted.

Combined in one work: compatible.

What else should I know?

What are the sources?

How can I check it myself (free, no key)?

{
  "tool": "check_license",
  "arguments": {
    "license": "Apache-2.0",
    "intended_use": {
      "commercial_use": true,
      "modification": true,
      "redistribution": true
    }
  }
}

Computed from a2ally's license profiles; not legal advice. JSON · Markdown

Get a free API key in one call

No card and no email needed. 100 free credits; the license and policy checks stay free without a key.

curl -s -X POST https://www.a2ally.com/v1/accounts/signup -H "Content-Type: application/json" -d '{"accept_terms":true}'
export A2ALLY_API_KEY=rs_...   # the api_key from the reply (shown once)
curl -s https://www.a2ally.com/v1/licenses/check -H "Authorization: Bearer $A2ALLY_API_KEY" \
  -H "Content-Type: application/json" -d '{"license":"MIT","intended_use":{"commercial_use":true}}'