Source: https://divicake.com/license/ # License What you can do with our plugins, how site counts work, what a paid licence actually buys, and who owns what we build for you. Written to be read, not to trip you up. Last updated 2026-10-05 · A product of Karobar Solutions LLC ## On this page - [The short version](https://divicake.com#the-short-version) - [Site counts](https://divicake.com#site-counts) - [Yearly or lifetime](https://divicake.com#yearly-or-lifetime) - [The plugin code is GPL](https://divicake.com#the-plugin-code-is-gpl) - [What a licence actually buys](https://divicake.com#what-a-licence-actually-buys) - [Bundled assets](https://divicake.com#bundled-assets) - [Client sites](https://divicake.com#client-sites) - [Services work](https://divicake.com#services-work) - [Our name and branding](https://divicake.com#our-name-and-branding) - [If a signed agreement exists](https://divicake.com#if-a-signed-agreement-exists) ## 01The short version Every plugin is licensed the same way. You pick a site count from the ones its product page offers — 1 site, 5 sites or unlimited — and how you pay for it, yearly or once. Nothing else changes between tiers: every licence is the whole plugin. - Use a plugin on as many sites as your tier covers, and keep using it after the licence ends. - Edit and extend the code however a project needs it. - Hand a finished site to a client with our plugin installed on it. - Own outright anything we build for you as a service. What you cannot do: resell or re-bundle our plugins as your own product, share licence keys or downloads beyond the sites your tier covers, or use our name or branding to sell something that is not ours. ## 02Site counts A site is one live WordPress installation. Your own sites and your clients' sites count the same — we do not distinguish between them, because the plugin cannot tell the difference and neither should the pricing. - 1 site — one live installation. - 5 sites — up to five live installations at a time. - Unlimited sites — every site you build, with no count to track. Staging, local and development copies of a site you already licensed do not count against your total. Test freely. ## 03Yearly or lifetime The site count is the licence. The term is only how you pay for it, and it makes no difference to what the plugin does or which features you get. A yearly licence includes updates and support for twelve months. A lifetime licence includes them for as long as we sell the plugin, paid once. Moving up a tier later is a straightforward upgrade, not a repurchase: what you already paid is credited against the higher tier. ## 04The plugin code is GPL Our plugins are WordPress plugins, so their PHP is licensed under the GNU General Public License, version 2 or later — the same licence WordPress and Divi use. You can read the source, change it, and redistribute your changed version under the same licence. We say this plainly because it is true of every WordPress plugin sold anywhere, and a vendor who implies otherwise is either confused or hoping you are. ## 05What a licence actually buys A licence is a commercial agreement for updates and support over a period. It is not what makes running the plugin lawful — the GPL already covers that. When a licence lapses the plugin carries on working. What stops is new versions, security patches and our time. Exceeding your tier is a licensing matter, not a technical one — the plugin will not switch itself off. If you outgrow a tier, upgrade it. ## 06Bundled assets Images, icons, fonts and third-party libraries shipped inside a plugin may be under their own licences, which travel with them and are listed in the plugin's readme where they apply. Demo images used in screenshots and layout previews are licensed to us for demonstration. They are not always cleared for you to reuse on a live site, so replace them with your own. ## 07Client sites Building a site for a client and leaving our plugin on it is exactly what these plugins are for, as long as that site fits inside your tier. A client site is not a special category — it is one of your sites for licensing purposes. If the client later wants updates and support in their own name rather than through you, they need their own licence. Tell them that at handover rather than leaving them to discover it when an update stops arriving. ## 08Services work Anything we build for you as a paid service — a custom module, a child theme, a site build — is yours outright on final payment, unless the signed agreement says otherwise. We keep the right to reuse general techniques and non-specific code patterns in other work. We do not reuse your content, your branding or anything distinctive to your project. ## 09Our name and branding The GPL covers the code. It does not give anyone the right to use the Divi Cake name, logo or branding to market a product, a service or a fork as though it came from us. ## 10If a signed agreement exists This page is a plain-English summary of how Divi Cake is licensed. Where you have a signed agreement with us, that agreement governs and this page is context. Questions about this page? Email [our team](https://divicake.com/contact/) and we will answer plainly.