Kindly EditDocumentationTry the editor

License and update service

Understand activation seats, release selection, signed downloads, and immutable package publication.

Client protocol#

The plugin-facing service speaks the Easy Digital Downloads Software Licensing request shape. A POST to its root supplies an action such as activate_license, deactivate_license, check_license, or get_version, plus the product, site URL, plugin version, and license credentials as required.

License records and activations live in D1. Release package bytes live in R2. The plugin's public-rendering behavior remains separate from this service's availability.

Site identity and seats#

A site identity consists of the normalized hostname and installation subfolder, without scheme, port, or a leading www.. A move from HTTP to HTTPS therefore keeps the same seat. Two WordPress installations under different subfolders remain distinct.

Recognized local and staging hosts do not consume ordinary seats. Seat acquisition uses an atomic database operation so concurrent activations cannot independently claim the same remaining capacity. An already activated site retains its seat if the configured limit is later reduced.

Signed downloads#

The inspected service creates signed download links with a 48-hour lifetime. They identify the license record rather than embedding its key. During that lifetime they are bearer links, so keep them private.

A download still checks current license validity and site activation. Expiration, disabling the license, or freeing the site can revoke access before the link's timestamp expires. Re-activation can make a still-unexpired link usable again.

Release publication#

Publication validates the manifest version, channel, file name, product slug, SHA-256, optional size, ZIP structure, entry paths, expanded lengths, and checksums. The source bounds uploaded archives to 50 MiB and expanded content to 100 MiB. Archives must stay within their product root and contain the expected plugin or theme entry file.

A published version is immutable. Repeating the same bytes can refresh permitted manifest information; different bytes under the same published version are rejected. Each upload attempt has a distinct object key. If database publication fails after upload, cleanup removes only that attempt's unreferenced object.

Administration#

Administrative license and release operations require separate service authorization. They are not part of the ordinary editor API. License values such as expiration dates, site limits, status, and branding are validated rather than silently coerced.

The local fault-injection test wrapper is a development utility and must not be deployed. It intentionally simulates storage failures to test cleanup and race behavior.

About this page

Documents Kindly Edit 0.9.16. Source: server/updates-worker/src/index.js, server/updates-worker/README.md. Theme choices and account permissions can change which controls appear.

Type a word or phrase to search the full documentation.