Three kinds of add-on, three ways to reach the network
| Kind | What it is | Reaching the License API | Notes |
|---|---|---|---|
Script (.jsx) |
ExtendScript run from the Scripts menu or a panel | Plain TCP only, so call curl through the system |
Needs the preference that lets scripts write files and access the network |
| CEP or ZXP panel | HTML and JavaScript in a panel | The panel’s own fetch |
The License API allows cross-origin calls |
Native effect (.aex) |
C++ plugin built with the After Effects SDK | An HTTP library such as libcurl, or the OS API | Runs in the render path |
A script’s Socket object speaks plain TCP, not TLS, and the License API is HTTPS only. A script therefore calls the system’s curl through ExtendScript’s system call, parses the JSON, and requires the user to turn on the scripting preference for file and network access. That works, but write it with care: a missing curl, a path with spaces and a user who forgot the preference are all failures you will see in support. If you ship scripts, say in your install guide which preference to switch on.
A panel is the easiest: a web page with fetch. A native effect is the hardest, because the check cannot slow a render.
Where to sell
Adobe’s Developer Distribution FAQ says the portal lets plugin developers list “UXP and ZXP” packages, and non-plugin items, in the Creative Cloud Marketplace. For paid products it uses FastSpring, and the FAQ says “for any paid product you offer for sale, you will take 90% of the sales revenue”. If your add-on is a CEP panel, that is a real option. See the Photoshop page for how that path works, since it is the same portal.
The FAQ does not describe native .aex effects or plain .jsx scripts. This page could not confirm that either can be listed, so ask Adobe before you build your plan on it. Either can be sold from your own site with Stripe and a license key, which is the case Clavem covers.
What is specific to After Effects
Renders run apart from the interface. Renders can run in processes that have no interface, for example with aerender, and studios send jobs to other machines. A check that waits for a click in the user interface stops a headless render. In a render process, read the stored token, verify it with no network, and carry on. Never open a dialog from a render.
Render nodes are devices. A studio with 12 render machines either buys 12 seats or a license policy for nodes. Options:
| Approach | How it works | Trade-off |
|---|---|---|
| One key per node | Each node activates, and uses one device slot | Simple; the studio buys keys in bulk through a Stripe quantity |
| A render license as a separate product | Priced for nodes, with a high device limit | Clear to the buyer; a second SKU to explain |
| Verify the token only, on nodes | Copy the signed token from a workstation to nodes; verify it offline | No seat per node, but it lapses after refresh_by and is not bound to a machine |
A token is not tied to a device, so it verifies the same way on every machine until refresh_by. That is convenient for a farm and loose as protection. Choose it knowingly.
Studios are often behind firewalls. Adobe’s FAQ gives guidance for people who work offline or in restricted settings, noting that scripts typically need neither the internet nor the Creative Cloud app. The same people will not reach the License API from every machine. Offline verification fits them.
The effect runs many times. An effect is called for every frame and every instance. Initialize once per process, keep the state in a shared object and read a flag. A check on each call is both slow and too many requests: the License API allows 60 a minute per key.
Recommended setup
| Setting | Suggested value | Why |
|---|---|---|
| License type | Perpetual with paid major versions, or annual | After Effects projects are reopened years later |
| Device limit | 2 for freelancers; extra keys for render nodes | A workstation and a laptop |
| Trial | 7 to 14 days, or watermarked output | A trial that watermarks lets people judge the result |
| Updates | Installer or script checks the releases endpoint; files labelled macos and windows |
One download per platform |
Doing this with Clavem
Create a product, connect Stripe, map the price. A buyer gets a key and an order page with the installer or ZIP. Activate once from the panel or a menu command, validate at startup, and store the token in a folder that all of your add-on’s pieces can read. For a native effect, the C++ guide shows the HTTP call and the Ed25519 check. A panel can follow the Node.js guide. Both the guides and the offline page use the same token format.
Guides to follow
- License key validation in C++
- Offline license verification in C++
- Device activation in C++
- License key validation in Node.js
Questions
Can I list an After Effects plugin on Adobe's marketplace?
Adobe's Developer Distribution FAQ says the portal distributes UXP and ZXP (CEP) packages, and non-plugin items, into the Creative Cloud Marketplace. It does not describe native effect plugins, so check with Adobe whether yours can be listed before you plan around it.
Should a render check the license every frame?
No. Check once when the plugin or render process starts, keep the result in memory, and read the stored token on each later load. A per-frame network call slows the render and can exceed the License API's limits.