Setyenv · Docs
  • English
  • Español
  • 中文
  • 日本語
  • العربية
  • Deutsch
  • Français
  • हिन्दी
  • Bahasa Indonesia
  • Italiano
  • Nederlands
  • Português
  • Русский
  • Türkçe

Plugin downloads

How the plugin .zip gets from our server into your hands.

Who can download

Anyone with a Setyenv account. Registration is free; once logged in, the customer dashboard lists every published release of each plugin with a Download button. No licence is needed: the download is the standard build, and a site running it without a key is a Community Edition site.

What differs by what you hold:

You holdYou download
An account, no licenceThe standard build (Community Edition)
An Enterprise licenceThe standard build — the key is what makes it Enterprise
An Enterprise licence with the source add-onThe clean-source build as well

WP-PFAgent is free software and is always served as source.

The download flow

  1. In your customer dashboard open Downloads and click Download on a release.
  2. The portal asks an out-of-band worker to issue a signed, single-use URL: the link encodes the product, the version, an expiry and an HMAC-SHA256 signature over them, plus a nonce that is consumed when the download completes.
  3. Your browser follows the link. The portal validates the signature (timing-safe), re-checks that the release is still published and, for a licensed download, that the licence is still in good standing, then streams the .zip from private storage outside the public docroot.

A link is valid for 24 hours and for one download; generate a fresh one whenever you need it.

What is inside the .zip

Exactly the files that ship to every other customer of that version. There is no per-customer fingerprinting in the zip; the site is identified at activation time, by its fingerprint, never by the artefact.

Updates

Installed plugins update through the Setyenv update channel (updates.setyenv.com) using WordPress's standard update mechanism: the update shows on Plugins like any other, and auto-updates work if you enable them. Both editions receive updates. Our Docker image updates the same way — the plugins live in the container's volume, and the image is only their first copy.