Technical Guide

Software Source-Code & Commercial Licensing Guide

How does source-code licensing work at TechDino?

Buyers receive source code for the applications and modules in their agreed purchase scope. Access to code does not transfer copyright or automatically permit resale. The written licence defines usage, modification, brands, deployments, tenants and support. Single-business operation, multi-tenant operation and redistribution are separate rights; confirm each required right before purchasing.

License Models Compared

Model 1

Single-Business License

A written single-business licence defines the permitted branded deployment and use for your own business, including hosting and modification rights.

1 Production Brand / Domain
Self-Hosting Rights
Readable Source Code Included

Model 2

Reseller / Multi-Tenant License

Multi-tenant operation and redistribution to clients must each be expressly permitted by the written agreement. A multi-tenant product does not automatically include source-code resale rights.

Tenant and client limits agreed in writing
Commercial and support terms agreed in writing
Platform admin where included in the product scope

Discuss Your Licensing Requirements

Contact TechDino to clarify source-code scope for your specific product or project.

WhatsApp TechDino Explore Source Code Solutions

Licensing questions, answered

The points buyers raise most often about this stage, answered in the same terms used in the guide above.

Do I own the source code I receive?: You receive the applicable source code for the agreed scope and the right to use, modify and deploy it for the business described in that scope. Copyright in the underlying product code base remains with its respective rights holder unless a written agreement assigns it.
Can I resell the software to other businesses?: Not under a standard purchase. Redistribution, resale and sublicensing are excluded, and reseller rights exist only under a separate written reseller agreement. Deploying beyond the agreed operational scope is a separate licence item.
What about the open-source libraries inside the code?: Delivered code includes third-party open-source components under their own licences, such as MIT, Apache-2.0 or BSD. Those licences continue to apply independently of your agreement with TechDino, and the licence files stay in the delivered repository.
Who owns custom modules built specifically for us?: Intellectual property in bespoke modules is addressed in the written agreement for that work including any assignment and payment conditions.

Loading TechDino

How does source-code licensing work at TechDino?

License Models Compared

Model 1

Single-Business License

A written single-business licence defines the permitted branded deployment and use for your own business, including hosting and modification rights.

1 Production Brand / Domain
Self-Hosting Rights
Readable Source Code Included

Model 2

Reseller / Multi-Tenant License

Multi-tenant operation and redistribution to clients must each be expressly permitted by the written agreement. A multi-tenant product does not automatically include source-code resale rights.

Tenant and client limits agreed in writing
Commercial and support terms agreed in writing
Platform admin where included in the product scope

Licensing questions, answered

The points buyers raise most often about this stage, answered in the same terms used in the guide above.

Do I own the source code I receive?

You receive the applicable source code for the agreed scope and the right to use, modify and deploy it for the business described in that scope. Copyright in the underlying product code base remains with its respective rights holder unless a written agreement assigns it.

Can I resell the software to other businesses?

Not under a standard purchase. Redistribution, resale and sublicensing are excluded, and reseller rights exist only under a separate written reseller agreement. Deploying beyond the agreed operational scope is a separate licence item.

What about the open-source libraries inside the code?

Delivered code includes third-party open-source components under their own licences, such as MIT, Apache-2.0 or BSD. Those licences continue to apply independently of your agreement with TechDino, and the licence files stay in the delivered repository.

Who owns custom modules built specifically for us?

Intellectual property in bespoke modules is addressed in the written agreement for that work including any assignment and payment conditions.