Open-Source Licences
Who controls each critical account and can another authorised person recover the service during an incident? Inventory production dependencies and review licence obligations before product distribution or customer commitments.
What You Will Be Able to Decide
- Explain open-source licences in product and business terms.
- Apply this decision: Inventory production dependencies and review licence obligations before product distribution or customer commitments.
- Recognise this material risk: the company cannot meet a dependency's terms or prove what code it is entitled to distribute.
- Use this review: Exercise contractor offboarding, secret rotation, backup restore, and the first incident handoff for the customer portal.
A founder is clarifying who controls the product and how the company will respond when something goes wrong. This lesson gives you a concrete question to take into a build brief, proposal review, or product decision.
Who controls each critical account and can another authorised person recover the service during an incident? The course example is A small team's customer portal with contractors and external integrations; use it to decide what evidence would justify the choice before a builder implements it.
What Does Open-source Licences Mean for Your Product?
A founder is clarifying who controls the product and how the company will respond when something goes wrong.
Use the illustrative service for this course (A small team's customer portal with contractors and external integrations) to make the choice concrete. Who controls each critical account and can another authorised person recover the service during an incident?
Technical term
Open-Source Licences
An open-source licence grants permissions under conditions that may govern attribution, distribution, modification, or disclosure.
How Should a Founder Use Open-source Licences?
For a small team's customer portal with contractors and external integrations, ask what would happen if the company cannot meet a dependency's terms or prove what code it is entitled to distribute.
For this decision, the useful standard is that access, ownership, recovery, and response responsibilities are explicit and can be exercised without one individual.
- Decision: Inventory production dependencies and review licence obligations before product distribution or customer commitments.
- Evidence to request: show that access, ownership, recovery, and response responsibilities are explicit and can be exercised without one individual.
- Owner: name who will respond if the company cannot meet a dependency's terms or prove what code it is entitled to distribute.
- Record the result in the security, ownership, and handover record.
- Practical review: Exercise contractor offboarding, secret rotation, backup restore, and the first incident handoff for the customer portal.
How Do You Choose an Approach to Open-source Licences?
Who controls each critical account and can another authorised person recover the service during an incident? Inventory production dependencies and review licence obligations before product distribution or customer commitments.
The risk is that the company cannot meet a dependency's terms or prove what code it is entitled to distribute. Compare a simpler option with the proposed one, including who will operate either choice.
- Describe the user or business outcome that must be protected.
- Identify the most credible failure and its consequence.
- Compare the simplest adequate approach with one realistic alternative.
- Set a review point for when the decision may need to change.
What Evidence Should You Accept for Open-source Licences?
What Warning Signs Should You Look For?
- The proposal does not address this risk: the company cannot meet a dependency's terms or prove what code it is entitled to distribute.
- Nobody can show whether access, ownership, recovery, and response responsibilities are explicit and can be exercised without one individual.
- The decision has no named owner or review point.
What Should You Ask a Consultant?
- What changes for the user if we choose this approach to open-source licences?
- How have we reduced or accepted this risk: the company cannot meet a dependency's terms or prove what code it is entitled to distribute.
- Can you demonstrate that access, ownership, recovery, and response responsibilities are explicit and can be exercised without one individual?
- Who owns the result, and when will we reconsider it?
Key takeaway
Key Takeaway
Inventory production dependencies and review licence obligations before product distribution or customer commitments. Ask for evidence against the specific risk: the company cannot meet a dependency's terms or prove what code it is entitled to distribute.