Your startup’s codebase has rules: What founders should know about software licensing

Takeaways from a lunch & learn with Steven Smith, co-founder & CEO of Perdix Software, Inc.

TL;DR

  • Open-source software can help startups move faster, but every component comes with licensing requirements to understand and follow.
  • Licensing issues can surface during customer audits, investor due diligence, acquisitions, and other reviews of a company’s codebase.
  • AI can speed up software development, but founders still need to review code, dependencies, and licenses before using them.
  • Tracking your software dependencies can help you understand what’s in your codebase and make sure your licensing choices fit your business model.

Software development moves quickly, especially at startups with a Software as a Service (SaaS) business model. Open-source packages, third-party libraries, and AI-assisted development tools can help teams solve problems faster and bring products to market more efficiently.

But each of those tools and components comes with its own licensing terms, and understanding those terms is an important part of building a product that can scale.

Steven Smith

At a recent NextCorps lunch & learn, Steven Smith, co-founder & CEO of Perdix Software, shared practical lessons on software licensing and what founders should consider when incorporating third-party code into their products. Drawing on his experience working between software development and legal teams at Juniper Networks, Smith covered everything from the basics of open-source licenses to how startups can keep track of the software inside their products.

Smith emphasized that he is not a lawyer and was not providing legal advice. Instead, the session focused on helping entrepreneurs understand what questions to ask before bringing third-party software into their products.

Start with one simple question: What license does this use?

Smith’s biggest piece of advice focused on what most people don’t take the time to do: read the license. Software is automatically protected by copyright, so finding code on GitHub or another public website doesn’t automatically mean it’s free to use. If a repository does not include a license, Smith explained, there is no license granting permission to use it.

Different open-source licenses also come with different requirements. Some, such as MIT and BSD, are relatively permissive, while others can place additional conditions on how software is incorporated into or distributed with another product.

That does not make one license inherently better than another. Smith noted that companies can intentionally build businesses around licenses such as the General Public License. The important thing is understanding what a license requires and whether those requirements fit the way a startup plans to build, distribute, and monetize its product.

A licensing problem can become a business problem

Licensing might not be top of mind while a startup is focused on building its product, but it can become much more important during customer audits, investor due diligence, acquisitions, or automated code scans.

Smith shared an example from Perdix Software that brought this to life. A customer wanted to import PDF files from a manufacturing marketplace into Perdix Software’s product. Smith looked for a way to process the files and, with the help of an AI coding tool, found a popular Python package that appeared to be a good fit. Then he checked the license.

The package was licensed under the Affero General Public License, with a commercial licensing option available from its publisher. For Perdix Software, purchasing that license did not make sense for the particular customer request.

Rather than incorporating the package directly into the company’s proprietary software, Smith created a separate executable program file that processed the PDF and returned the results as JSON (JavaScript Object Notation). The main product could then consume that information without directly incorporating the open-source component.

The solution allowed Perdix Software to use the package while keeping it separate from the rest of the product. More broadly, the example showed why understanding a license early can influence technical decisions later.

AI changes the workflow, not the need for review

AI-assisted development adds another reason to pay attention to what is going into a codebase.

Smith discussed the evolving questions around copyright and AI-generated code, but his practical advice was that AI-generated code still needs to be reviewed before it becomes part of a product.

That means checking what the code does, where dependencies come from, and what licenses apply to them. An AI tool may recommend a package that looks like a perfect solution, but developers still need to investigate that package before adding it to the product.

AI can make software development faster. It does not change the need to understand the software being shipped.

Know what’s inside your codebase

One way startups can keep track of those components is through a software bill of materials (SBOM).

Smith compared an SBOM to a bill of materials used in manufacturing. Instead of listing the physical parts that go into a product, it keeps track of the software components that make up an application, including their versions, sources, and licenses. It should also account for transitive dependencies, or the additional components brought in by other dependencies.

Perdix Software started this process manually with spreadsheets before integrating SBOM generation into its build and release process. As the company’s codebase grew, automation made it easier to monitor dependencies and flag licensing changes.

For an early-stage startup, Smith’s advice is not to build a complicated system overnight. Start by documenting what third-party software is in your product and what licenses apply. Then, as the company grows, make that process part of the development workflow.

Build with the business in mind

Software licensing isn’t about avoiding open-source software or slowing down development. It’s about understanding what you’re building with and making sure those choices are a good fit.
For founders, that means reading the licenses attached to the software they use, keeping track of what’s in their codebase, and considering licensing as part of the product and development process from the start. As Smith put it, “Match the license to your business model, not to your vibe.”

Interested in future NextCorps workshops and events? Subscribe to the NextCorps newsletter to stay up to date on upcoming workshops and events.

Access the State of Innovation Report

Close Welcome Bar

Stay in the Loop!

Subscribe to NextCorps communications to stay up-to-date on what’s happening in the region’s startup community, including info on upcoming events and opportunities that can help forward your business. No spam. No ads. Unsubscribe at any time.

This field is for validation purposes and should be left unchanged.