Licensing that understands how WordPress is actually used.
Production, staging, development, multisite and domain moves are different realities. Key now has a WordPress-native way to describe them without creating a second licensing engine.
Staging, multisite and domain moves belong in the product—not in support-ticket folklore.
Production, staging, development, multisite and domain moves are different realities. Key now has a WordPress-native way to describe them without creating a second licensing engine.
Live license changes remain disabled until Key becomes authoritative.
A WordPress installation can keep the same identity even when its domain changes.
Production, staging, development, preview and local environments are classified separately.
Network context travels with the installation description instead of being flattened into one URL.
A stable installation identity plus a changed host is treated as a probable move, not automatically as abuse.
Developers can inspect how Key sees a site before live licensing actions are enabled.
Verified purchase events can be translated into a rights preview without giving WooCommerce licensing authority.
That is expected at this stage. The adapter and site-intelligence rules are ready first; live activation and update traffic comes only after the authority and delivery gates are proven.