Build, Buy or Open Source: Making Software Component Decisions
A modern application is mostly code its team did not write: operating system libraries, frameworks, protocol stacks, database engines and hundreds of indirect dependencies. The decision that matters is not whether to reuse, but what to reuse, on what terms, and who will maintain it once the product ships.
At a glance
- Copyleft
- Licences such as the GPL require source to be shared for derivative works that are distributed.
- Permissive
- MIT, BSD and Apache 2.0 mainly require copyright and licence notices to be kept.
- SBOM
- A software bill of materials lists every component and version that ships in a product.
- Transitive
- Most dependencies arrive indirectly, pulled in by the libraries a team chose on purpose.
The problem
Writing everything in-house looks like control, but it makes the team the maintainer of code that is not its product: a parser, a protocol stack or a cryptographic routine that a mature library already does better.
Adopting components casually has the opposite cost. A library with an incompatible licence, a single overstretched maintainer or no security fixes becomes the product owner's problem the day a vulnerability is published or a customer asks for a licence audit.
Build what makes the product different. Reuse the rest, but choose it as carefully as you would choose a supplier.
Reading the licences
Permissive licences allow use in closed-source products with attribution, and Apache 2.0 adds an explicit patent grant. The LGPL lets proprietary code use a library, typically through dynamic linking, provided users can replace it. The GPL extends its terms to the whole derivative work when distributed, and the AGPL extends them to software offered over a network.
Connected products need particular care, because shipping firmware or a device image counts as distribution, and version 3 of the GPL and LGPL adds requirements for installing modified versions on consumer devices. Regulation is moving too: the EU Cyber Resilience Act makes manufacturers responsible for vulnerabilities in components they ship.
What good looks like
Separate the components that define the product from those that are infrastructure. Only the first group is a strong candidate for building in-house.
For each candidate component, check the licence, maintenance activity, security history and the cost of replacing it, then record the decision.
Generate an SBOM in the build, scan it for known vulnerabilities on every release, and give someone ownership of keeping dependencies current.
| Licence | Type | Main obligation when distributing |
|---|---|---|
| MIT, BSD | Permissive | Keep copyright and licence notices |
| Apache 2.0 | Permissive | Keep notices, mark changes; includes a patent grant |
| LGPL | Weak copyleft | Share library changes and allow the library to be replaced |
| GPL | Strong copyleft | Provide source for the whole derivative work |
| AGPL | Network copyleft | As GPL, and also when users interact over a network |
| Build in-house | Buy or adopt | |
|---|---|---|
| Up-front cost | High | Lower |
| Fit to requirements | Exact | Close enough |
| Time to first use | Slow | Fast |
| Ongoing maintenance | All on your team | Shared with vendor or community |
| Control over roadmap | Full | Limited |
What it changes
Focus
Engineering time goes into the features customers pay for, not reimplementing common infrastructure.
Compliance
Licence obligations are known and met before release, not discovered in due diligence.
Security
An up-to-date SBOM shows quickly whether a newly published vulnerability affects the product.
Longevity
Components chosen for healthy maintenance are less likely to strand the product later.
Where to go next
Buying makes sense when a commercial component brings support, certification evidence or indemnity the team would otherwise have to create. Check its terms for redistribution and per-unit fees.
Where you modify an open-source component, contribute the change upstream if you can. Carrying a private fork makes every future update harder.
Problems this prevents
- A copyleft licence found during an audit
- Dependencies nobody is updating
- A vulnerability report you cannot assess
- A private fork that blocks upgrades
Discuss your project
Email support@aavico.com or use Get in Touch when the website finishes loading.