Licensing model

The two commercial plugins, WP-PFManagement and WP-PFWorkflow, ship together as one suite in two editions that run the same code:

Community Edition — free, for personal and non-commercial use. Every feature, no key. Register on setyenv.com, download, install.
Enterprise Edition — for commercial use, as a monthly or annual subscription. One key, entered once in either plugin, licenses both on that site. WP-PFAgent is free software and needs no key in either case.

The Setyenv suite on the pricing page — one subscription for WP-PFManagement + WP-PFWorkflow, monthly or annual, multi-domain

Plain English:

You receive the running plugins as .zip files — or as our Docker image. They are normal PHP: they install and update through WordPress the same way any other plugin does, in both editions.
An Enterprise subscription covers as many domains as you choose at checkout; two or more earns an automatic multidomain discount on the whole subscription. Several separate subscriptions are fine too — each is independent.
The public extension surface — WordPress action / filter hooks, REST routes, capability strings, public PHP classes you would call from a child plugin — is preserved exactly so you can integrate, theme and automate around it.

Two ways to get the code

Standard (obfuscated) — the default, and the Community download. The plugins ship with their developer comments stripped and the names of internal (private / protected) classes and methods obfuscated. They behave normally on your server; the implementation stays ours. Standard Enterprise purchases are refundable — one refund per subscription.

Source access (Enterprise annual add-on). On an annual plan you can add clean source access: you receive the PHP source in the clear (unobfuscated) for every version of both plugins published while you are subscribed, as a single flat yearly fee for the whole suite, independent of how many domains you license.

With source access you may modify the code for your own purposes, but redistribution is expressly prohibited — modified or unmodified, to anyone.
Source access waives all refunds. Once your account has taken source access, no refund is available on any of your licences. This is shown in red at checkout before you confirm.

Either way you cannot use the plugins to build a competing product, and the Community Edition cannot be used commercially. The legally binding terms are in the EULA; this page is a plain-English summary.

How the key itself works

The Enterprise key is a self-contained token that carries its own expiry and the edition it confers. The plugin verifies it against setyenv.com once a day and shows the result under Setyenv → License; a site that cannot reach the portal keeps working, and only after 60 days without a successful check does the key stop counting — the site then runs the Community Edition until it reconnects. Nothing is ever paused. Details in Community & Enterprise.

Why not GPL?

WordPress itself is GPL. Plugins distributed through wordpress.org must be GPL-compatible. We do not distribute through wordpress.org — we distribute through our own portal, our own update channel and Docker Hub. That puts us outside the wordpress.org distribution channel and removes the GPL inheritance requirement. We chose a proprietary licence with a free Community Edition because we need to keep selling the Enterprise Edition to fund development.

What you can still audit

Even with internal naming obfuscated, you can verify in your own environment exactly what the plugin does:

Every action it takes against your DB: workflow executions, agent actions, record changes are logged with the user who triggered them and the arguments used.
Every outbound HTTP call the plugin issues — to LLM providers, the licence portal, your remote executor — is surfaced through the relevant trace / telemetry surface.
Every REST and admin endpoint is enumerable: the agent's /contract endpoint and the workflow's /catalog endpoint publish the typed contract the plugin exposes.

Static code audit is intentionally limited; behavioural audit is not.

The companions that ARE open source

WP-PFAgent (GPL-2.0) and wp-executor (MIT/Apache-2.0, the remote execution agent for the Workflow platform). You can read them, build them from source and run them without buying anything.