Skip to content
dvnt.io

Resources · glossary

Software licence

Permission to use someone else's code on set terms. It is not the same as ownership: when you buy an implementation, you usually buy the right to use it, not the code.

Also called
  • software licence
  • software license
  • licensing terms
  • licence agreement
  1. 01

    Three models you will come across

    Open-source licence (WordPress, Next.js): you use it free of charge, with obligations to the authors. Commercial licence: you pay per seat, per domain or per year. Subscription: you pay for as long as you use it, and when you cancel you keep your data, not the tool.

  2. 02

    Where it hurts in practice

    When you change supplier or scale. A single-domain licence blocks a second shop, a per-seat licence grows with your team, and a plugin with an annual renewal stops getting security fixes once you stop paying.

  3. 03

    Open doesn't mean free

    An open licence removes the fee, not the cost. Hosting, updates and someone's time remain. What it does remove is one risk: nobody can cut you off from your own tool.

  4. 04

    What to check before you sign

    Which parts of the implementation carry paid licences, who holds them (you or the agency), and what happens to them when the work ends.

In practice

Related terms

  • Source code copyrightSettling who may develop, copy and sell the code that was written. Without a written transfer of rights, they stay with the developer, even when the invoice has been paid.
  • Vendor lock-inDependence on a single provider, where switching tools or vendors is so costly that it stops being a real option. It is rarely a decision, usually a side effect.

← All terms

15 minutes. No sales pitch.

A term in a proposal sounds foreign? In 15 minutes we explain what it means for your project.