# Regular vs Extended License: which AcelleMail license do you need? > Envato issues two Standard licenses for AcelleMail: Regular and Extended. One question decides which you need — do your end users pay? Here is the rule, what "one end product" actually means, and where your purchase code goes in the app. - Canonical URL: https://acellesend.com/kb/articles/regular-vs-extended-license-for-acellemail - Author: Daniel Reyes, Technical Editor - Category: Installation & Setup — Server requirements, deployment, Nginx/Apache, PHP config, SSL - Content type: reference · Difficulty: beginner - Tags: Acellemail, Self Hosted, Codecanyon - Published: 2026-07-15 · Last updated: 2026-08-15 - Reading time: 7 min - Publisher: AcelleMail Knowledge Base, https://acellesend.com/kb --- ## What this is for You bought AcelleMail on CodeCanyon and you want to know which licence covers what you're building — and what that purchase code actually does once it's in the app. This page answers both. One thing to be clear about up front: **the licence is Envato's, not ours.** AcelleMail is sold through CodeCanyon, so the licence you hold is an Envato licence and Envato's terms govern it. Everything below quotes Envato's own pages and links to them. Where Envato routes a question to its Help Team rather than publishing an answer, this page says so instead of guessing. ## The two Standard licenses Envato issues two *Standard* licences for code items like AcelleMail. Both grant you "an ongoing, non-exclusive, worldwide license to make use of the digital work (Item)". The features are identical — **you are not buying fewer features with Regular.** | | Regular License | Extended License | |---|---|---| | Features | All | All | | Scope | One single End Product | One single End Product | | Your end users | Are **not** charged | **May** be charged | Envato's own one-line summary: > The main difference is that under the Regular License, your end product is distributed for free, whereas under the Extended License your end product may be sold. Worth knowing: Regular and Extended are the two licences in Envato's **Standard** category — the pair that applies to code items. Envato lists other categories (Music, Sound Effects, Video, Photo, Specialty) that don't apply here. ## Which one do you need? One question decides it: **do your end users pay?** > If the end users need to pay to see the end product, you need an Extended License. The catch is that "Free" has a precise meaning in the Regular License, and it explicitly covers subscriptions: > No fee is paid by the end user to access the End Product. The End Product is not sold. > No fee is paid to subscribe to a service that includes the End Product (eg a website subscription fee). That second clause is the one people miss. A subscription that includes access to your AcelleMail install **is** a fee — so it isn't Free, and Regular doesn't cover it. It doesn't matter that they're paying for "the subscription" rather than "the software". | What you're doing | Licence | |---|---| | Sending campaigns for your own company | Regular | | Running an install for one client; nobody is charged to use it | Regular | | Charging customers for accounts on your AcelleMail (SaaS mode) | Extended | ### Extended is not a SaaS free pass Extended lets you charge for **one** end product. It does not let your users spin up their own copies: > No. The Extended License only allows for a single end product. By allowing your users to download their own customized versions, you're allowing the item to be used in multiple end products. Envato rules out made-to-order and on-demand copies too — even a multi-use licence doesn't cover letting each customer generate their own customised product. That would need a separate single-use licence per product created. So: Extended covers *your* SaaS. It doesn't cover a business whose product is handing out AcelleMail instances. ## What "one end product" actually means Both licences are limited to one End Product, so the term carries a lot of weight: > The item is what you purchase from Envato Market. The end product is what you build with that item. The unit is the **End Product** — not the domain, and not the installation. Envato is blunt that Extended isn't a multi-domain or developer licence: > If I purchase an Extended License, do I get a multi-use, multi-domain, multi-client or developer license? No. The Extended License is still limited to a single end product, but you can re-sell that product. And an End Product can legitimately be copied: > A single application means one unique end product (which can be copied and made available to end users of that product). This is why "one licence = one server" is a rule of thumb people repeat, but **it isn't what the terms say** — the limit is conceptual, not an install counter. Whether two domains are one End Product or two depends on whether they're genuinely the same product, and that judgement is one Envato routes to its Help Team rather than publishing a formula for. ## Where your purchase code goes in AcelleMail **During install, it's optional.** The site-config step has a *License Key (Optional)* field, and says so directly: "You can update this later in the settings page." Leave it blank and the install still completes. **Afterwards it lives in Settings → License:** - **Purchase Code** — paste the code and save. - **Refresh** — re-checks your code. Use it when the page shows stale details, typically after renewing support. - **Supported until \** — your item support window (see below), not a licence expiry. **Verification is a network call.** The app checks your code against a licence-verification endpoint over HTTPS. This trips up more fresh installs than a bad code does: a server with no outbound HTTPS will fail verification even with a perfectly valid purchase code. If your egress is firewalled, or you're on Rocky/RHEL with SELinux blocking outbound connections, fix that first before assuming the code is wrong. ## Item support is not the license These are two different things, governed by two different Envato documents. Conflating them causes a lot of needless worry. **Item support is time-boxed.** Envato's Item Support Policy: "A supported item includes item support for 6 months from the purchase date," and at purchase you can extend it "up to a maximum of 12 months from the date of purchase." It covers questions about the item's features and functionality — not modifying it beyond its original features, and not installing it on your server. **The licence is not.** Both Regular and Extended grant an **ongoing** licence, in the licence terms' own word. The Item Support Policy says nothing about the licence ending when support does, and support is nowhere made a condition of the licence grant — they're separate documents doing separate jobs. So when Settings → License shows *Supported until* a date that has passed, that's your **support window** closing, not your licence. Envato also describes items as royalty free: > You just need to pay for rights to use the item once per end product. You don't need to pay additional or ongoing fees for each person who sees or uses it. ## Common issues | Issue | Cause / fix | |---|---| | Verification fails on a fresh install | The server can't reach the verification endpoint. Check egress firewall rules; on Rocky/RHEL, SELinux blocks outbound HTTP until `httpd_can_network_connect` is enabled. The code is usually fine — the network isn't. | | Left License Key blank during install | Expected. The field is optional by design; add the code later in Settings → License. | | Licence details look stale after renewing support | Hit **Refresh** on the License page to re-check. | | You need to exceed your licence's limits | E.g. you hold Regular and are about to start charging. Contact the Envato Help Team with your Envato username/email and the item name. Envato handles this case by case and publishes no self-serve upgrade path — so don't assume you can simply pay a difference. | ## What to do next - **On Extended and running SaaS mode?** You're licensed for one product you charge for — not for letting customers spin up their own instances. Re-read the Q21 quote above if that's your model. - **On Regular and about to start charging?** Talk to the Envato Help Team *before* you flip the switch, not after. - **Not sure your code is registered?** Settings → License shows the licence type, the buyer, and the support window at a glance. ## Sources All quotes on this page come from Envato's own pages: - [Regular License terms](https://codecanyon.net/licenses/terms/regular) - [Extended License terms](https://codecanyon.net/licenses/terms/extended) - [Envato Market License FAQ](https://codecanyon.net/licenses/faq) - [Item Support Policy](https://codecanyon.net/page/item_support_policy) Envato's terms are the authority on licensing questions and can change; if this page and Envato disagree, Envato wins. ## Related articles - [Install AcelleMail on Ubuntu 24.04](https://acellesend.com/kb/articles/install-acellemail-on-ubuntu-2404) - [REST API authentication and endpoints](https://acellesend.com/kb/articles/rest-api-authentication-and-endpoints) --- ## Related articles - [Install AcelleMail on AWS EC2](https://acellesend.com/kb/articles/install-acellemail-on-aws-ec2): This guide has moved. The install walkthrough for any server, an AWS EC2 instance included, is Install AcelleMail and Get Started. - [Server Requirements and Hosting Options for AcelleMail](https://acellesend.com/kb/articles/server-requirements-and-hosting-options): The right server for AcelleMail is dictated by send volume, not subscriber count. A list of 5M subscribers mailed monthly needs less compute than a list of 100k mailed daily. This article gives concrete specs at four volume tiers, a current 2026 provider comparison, and the operational considerations that determine your real cost. - [Securing Your AcelleMail Install: A Post-Install Checklist](https://acellesend.com/kb/articles/post-install-hardening-checklist): Your AcelleMail install works the moment the web installer turns green — but two things now live on your server that didn't before: your subscribers' personal data, and your domain's sending reputation. This checklist secures both, in priority order, without turning you into a sysadmin. Most of it is config you set once. - [Docker Deployment Guide for AcelleMail](https://acellesend.com/kb/articles/docker-deployment-guide-for-acellemail): Containerised AcelleMail trades a small ergonomic cost (volumes, image rebuilds, patch flows) for dev/prod parity and clean image-tag rollback. This guide ships a production-ready Dockerfile (with all wizard-required PHP extensions baked in), a docker-compose.yml stack, and the operational recipes for patches, scaling, logs, and backups. - [Install AcelleMail on Ubuntu 24.04 LTS](https://acellesend.com/kb/articles/install-acellemail-on-ubuntu-2404): This guide has moved. The install walkthrough for any server, an Ubuntu 24.04 server included, is Install AcelleMail and Get Started.