Licensing model

The commercial platform is sold as one subscription — the Setyenv PF Pack — a single, per-customer license that covers both proprietary plugins together, WP-PFManagement and WP-PFWorkflow. WP-PFAgent is included free. One key activates and updates the whole pack; you do not buy or track the plugins separately.

Plain English:

• You receive the running plugins as .zip files. They are normal PHP — they install and update through WordPress the same way any other plugin does, and the one license key entitles updates and downloads for both.
• You can deploy on as many domains as your subscription covers. Plans are monthly or annual (annual saves 20%), and licensing two or more domains earns an automatic multidomain discount on the whole subscription. Running several separate subscriptions (multi-license) is 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. 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 purchases are refundable — one refund per subscription.

Source access (annual add-on). On an annual plan you can add clean source access to the pack: you receive the PHP source in the clear (unobfuscated) for every version of both plugins published while you are subscribed. The source add-on is a single flat yearly fee for the whole pack, billed once a year, 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 licenses. This is shown in red at checkout before you confirm.

Either way you cannot use the plugins to build a competing product. The legally binding terms are in the EULA. This page is a plain-English summary.

How the license itself works

Your license is verified online and refreshes automatically while your subscription is active. For installs that cannot reach the internet (localhost, air-gapped), the license carries its own signed expiry, so the plugin knows its status offline; when you need to extend it you download an updated license from your portal account.

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 with per-customer license keys. That puts us outside the wordpress.org distribution channel and removes the GPL inheritance requirement. We chose a proprietary, per-customer licence because we need to keep selling the plugin 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 companion that IS open source

wp-executor is the remote execution agent for the Workflow platform. It is open source, MIT/Apache-2.0 dual-licensed, and lives on GitHub. You can read it, build it from source and run it without buying anything — only the WordPress side that publishes work to it needs a Setyenv licence.