License Terms

These License Terms define what you can and cannot do with themes, templates and smart contracts purchased from Coodes. Every Item is sold for a one-time payment under either a Regular License or an Extended License. The license you choose depends mainly on one question: will end users be charged to access or use your end product? Effective date and last updated: September 18, 2026.

1. Definitions

In these License Terms, the following terms have the meanings below:

• "Coodes", "we", "us", "our" means the operator of coodes.org, based in Cairo, Egypt.
• "Item" means a digital product purchased from Coodes, including Next.js website themes and templates, Solidity smart contract templates, Flutter mobile app templates, and all accompanying source code, design files, components, documentation and updates.
• "Licensee" or "you" means the individual or legal entity that purchased the license.
• "End Product" means one single website, web application, mobile application, decentralized application or other product that you create by incorporating the Item and adding significant original content, customization or functionality. An End Product is not a template, theme, starter kit, UI kit or any product whose main purpose is to be reused by others to build their own products.
• "End User" means a person or organization who accesses or uses the End Product.
• "Client" means a third party for whom you create an End Product.

These License Terms form part of our Terms of Service. If there is a conflict between the two regarding the use of Items, these License Terms prevail.

2. Regular and Extended Licenses

Items are licensed, not sold. Ownership of the Item and all intellectual property rights in it remain with Coodes or its licensors. On purchase and full payment, Coodes grants you a worldwide, non-exclusive, non-sublicensable (except as permitted below), perpetual license, subject to termination under section 13, to use the Item as follows.

2.1 Regular License

The Regular License allows you to use and modify the Item to create one single End Product, for yourself or for one Client, where End Users are not charged to access or use that End Product. Typical examples include a company or portfolio website, a marketing landing page, a blog, a free mobile app, or a free-to-use dApp front end. Your End Product may be commercial in the sense that it promotes your business or sells separate goods and services, as long as End Users are not charged for access to the End Product itself.

2.2 Extended License

The Extended License allows you to use and modify the Item to create one single End Product, for yourself or for one Client, where End Users may be charged to access or use the End Product. Typical examples include a SaaS platform with subscriptions, a paid mobile app, an app with paid in-app access to features built on the Item, a membership site behind a paywall, or a dApp where users pay fees for the functionality provided by the Item.

Both licenses are one-time payments with no recurring license fee. Pricing for each license type is shown on the Item page and on our pricing page.

3. License Comparison

4. The Single End Product Rule and Client Work

4.1 One license per End Product

Each license covers exactly one End Product. If you want to use the same Item for a second website, a second app or a second Client, you need to purchase a second license. Development, staging and testing environments for the same End Product are covered by the same license, as are reasonable variations of the same End Product (for example, the web version of a service and its administrative dashboard, or localized language versions of the same site). A mobile app released on multiple platforms (such as iOS and Android) from the same Flutter codebase counts as one End Product.

4.2 Client work

You may create an End Product for a Client and transfer that End Product to the Client, who may then use it under the same license terms. You may charge your Client for your services. The license must be purchased for the specific End Product, and when you transfer the End Product, you must ensure the Client is aware of and complies with these License Terms. After transfer, you may not use the same license for another project.

4.3 SaaS and charging End Users

If End Users pay to access or use your End Product, in whole or in part, you need an Extended License. This includes subscription fees, one-time access fees, freemium models with paid tiers that depend on the Item, and app store purchase prices. Using an Item to build an application that lets your customers create their own websites or apps from the Item (for example, a website builder) is not permitted under either license without a separate written agreement.

5. Prohibited Uses

Under both license types, you may not:

• redistribute, resell, lease, lend, sublicense, give away or share the Item or any part of it as stand-alone files, whether modified or unmodified, including by uploading its source code to a public repository, marketplace, file-sharing site or template library;
• resell or distribute the source code of the Item, even as part of an End Product, in a way that allows recipients to extract and reuse the Item (for example, selling your End Product's source code as a starter kit, boilerplate or template);
• use the Item to create a competing theme, template, UI kit or smart contract template, or include it in any product sold on a marketplace for templates;
• mint, tokenize or sell the Item itself, its source code, designs or any substantially unchanged part of it as an NFT or other digital asset (creating NFTs of your own original content through an End Product that uses our NFT contract templates is permitted, see section 6);
• use one license for multiple End Products or multiple Clients;
• remove or obscure copyright notices or license headers in the source code where present;
• use the Item, or any trademarks or demo content associated with it, in a way that suggests the End Product is endorsed by Coodes;
• use the Item in any End Product that is unlawful, fraudulent, deceptive (including scams, phishing, rug pulls or fake token projects), defamatory, or that infringes third-party rights; or
• use the Item or its demo content as training data for machine learning models intended to generate competing templates.

6. Smart Contract Deployment Rights

Items that include Solidity smart contracts grant you the right to compile, modify and deploy those contracts to any public or private blockchain network for the one End Product covered by your license. You may deploy multiple instances of a contract where reasonably required for that End Product, such as test network deployments, redeployments after fixes, or deployments to several networks serving the same End Product.

Because verified smart contract source code is often public on block explorers, publishing the verified source of a contract deployed for your End Product is permitted and does not breach the redistribution restrictions, provided that you do not separately package, market or distribute the contract as a reusable template. You may use NFT, token, marketplace or staking contract templates to issue your own tokens or NFTs representing your own content through your End Product; such tokens and NFTs are your responsibility.

7. Third-Party Assets and Open-Source Components

Items may include or rely on third-party components, such as open-source frameworks and packages (for example, Next.js, React, Flutter packages or Solidity libraries), fonts and icon sets. These components are licensed to you by their respective owners under their own licenses (such as MIT, Apache 2.0, BSD or OFL), not under these License Terms, and you must comply with those licenses. Open-source licenses may grant you broader rights to the open-source components themselves; nothing in these License Terms restricts rights granted by an open-source license.

Images, videos, illustrations and sample data shown in live previews are for demonstration only and are generally not included in the download or are replaced by placeholders. Where demo assets are included, they may not be used in your End Product unless the Item documentation states that they are licensed for that purpose. You are responsible for obtaining licenses for any content you add to your End Product.

8. Attribution

Attribution to Coodes is not required in your End Product's user interface, and you may remove any "Built with Coodes" or similar footer credit from the visible design. However, you must retain copyright and license notices embedded in source code files where present, and you must keep any attribution notices required by third-party open-source licenses. We appreciate, but do not require, a credit or link to coodes.org.

9. Support and Updates

9.1 Included support

Each purchase includes six (6) months of support from the date of purchase. Support covers:

• answering questions about the Item's features and how to use them;
• assistance with reported bugs and issues in the Item's original code;
• help with included third-party components where they are integrated into the Item as supplied; and
• guidance on setup as described in the Item documentation.

Support does not cover customization, installation on your servers, development of new features, integration with services not included in the Item, issues caused by your modifications or third-party plugins, hosting or server configuration, smart contract auditing, or general programming training. These may be ordered as custom services on our services page.

9.2 Support extension

You may purchase an optional support extension, where offered, to continue receiving support after the included period. Extensions are priced as shown at the time of purchase and are tied to the specific license.

9.3 Updates

We may release updates to fix bugs, address security issues, maintain compatibility with new framework versions or add features. Licensees have access to available updates for the Item for as long as the Item remains available on the Site, independently of the support period. We are not obligated to release updates or to maintain compatibility with every future version of third-party frameworks or networks.

10. License Transfer

Licenses are personal to the Licensee and may not be transferred, except that: (a) when you create an End Product for a Client, the license for that End Product transfers with it to the Client; and (b) a license may be transferred as part of a sale or transfer of the End Product or of the business that owns it, provided that the new owner agrees to these License Terms and the previous owner stops using the Item. Please notify us at [email protected] of any transfer so that we can update our records and provide support to the new owner. Support and support extensions transfer with the license for their remaining duration.

11. Upgrading Your License

If your End Product changes and you begin charging End Users, you must upgrade from a Regular to an Extended License before you start charging. Contact us with your order reference and we will let you know how to upgrade by paying the difference in price applicable at the time of the upgrade, where this option is available.

12. Warranty and Liability

Items are provided "as is", subject to the support described above and any rights you have under our Refund Policy and applicable consumer law. The disclaimers, limitations of liability and indemnities in our Terms of Service apply to your use of Items and End Products. You are solely responsible for your End Product, including its content, security, compliance with data protection laws (for example, providing your own privacy and cookie notices) and compliance with any regulations applicable to Web3 functionality.

13. Termination

Your license terminates automatically if you breach these License Terms and fail to remedy the breach within fourteen (14) days of our written notice, or immediately for breaches that cannot be remedied, such as redistribution of the Item. Your license also terminates if you receive a refund or if a chargeback for the purchase is decided in your favor. On termination, you must stop using the Item, delete all copies in your possession and cease operating any End Product that incorporates it. Smart contracts already deployed to a blockchain may not be removable; in that case, you must stop promoting and developing the End Product based on them and must not deploy new instances. Sections relating to ownership, prohibited uses and liability survive termination.

14. License FAQ and Examples

I am building a free company website. Which license do I need?

A Regular License. Your website does not charge visitors for access, so the Regular License covers it, even though the website promotes your paid business.

I want to build a subscription-based SaaS dashboard using a Coodes Next.js template. Which license do I need?

An Extended License, because your End Users pay a subscription to access the End Product. One Extended License covers one SaaS product, including all its customers.

I am a freelancer building sites for five clients with the same theme. How many licenses do I need?

Five licenses, one per Client End Product. Each license should be purchased for the specific project and transferred to the Client with the End Product.

Can I build an online store that sells physical products with a Regular License?

Yes. Customers pay for your products, not for access to the website itself, so a Regular License is sufficient. If customers must pay to access the store or its features, you would need an Extended License.

Can I publish a Flutter app built from a Coodes template on both app stores?

Yes. iOS and Android builds from the same codebase are one End Product. If the app is free and has no paid features built on the Item, a Regular License applies; if the app is paid or offers paid subscriptions or in-app purchases for functionality built on the Item, you need an Extended License.

Can I use a Coodes NFT contract template to launch my own NFT collection?

Yes, as your one End Product. You may mint NFTs representing your own original artwork or content. You may not mint the Item itself, its source code or designs as NFTs. If collectors pay to mint through your dApp, we recommend an Extended License, since End Users are charged to use functionality built on the Item. You are responsible for audits and regulatory compliance.

Can I put my End Product's code on a public GitHub repository?

Not if the repository would make the Item's source code freely available for others to reuse. Keep repositories containing the Item private. Publishing verified source code of smart contracts deployed for your End Product on a block explorer is permitted.

Can I sell a modified version of the theme as my own template?

No. Reselling or redistributing the Item, or a derivative of it, as a template, theme, starter kit or UI kit is prohibited under both licenses.

What happens when my six months of support end?

You can keep using the Item under your license indefinitely and continue to access updates. To keep receiving support, you can purchase a support extension. For customization or other work, see our services.

Still unsure which license fits your project? Check our FAQs, or contact us at [email protected] or +2 (0100) 303-8807 before purchasing and we will be happy to help.