The portal now prepares a clearer access-request path, but it still does not expose a public plugin package, license API, account login or customer execution channel.
Contact: operator input required; Email: operator input required.
Commercial inquiry path: operator input required; Pricing: operator input required; Packages: source not yet confirmed.
Portal copy is request-ready, but live request handling remains protected.
Portal gate: approval_required; no open download or private route exposure.
Open anonymous delivery would bypass the domain, scope, channel and rollback checks the product is built around. That would weaken the doctrine instead of reinforcing it.
A useful later access request starts before any protected workflow exists. The portal now explains what support and licensing logic will need from the requester before any real entitlement can be reviewed.
Later access will depend on license state, entitlement, release channel fit and protected delivery. Stable, pilot and rollback artifacts are designed to remain tied to the licensed domain context.
The portal can now qualify interest better, but it still does not expose a live request form, a customer login, a public package URL or a release activation workflow.
The readiness layer is now configuration-driven. Operators can later populate visible request context, but the portal still cannot submit, approve or fulfill anything by itself.
No. This page is informational. Production downloads remain gated and protected.
No. Domain binding, entitlement, scope control and protected delivery remain core constraints.
No. The page is request-ready in content only. Live request submission and fulfillment remain approval_required.
The next useful step is support-side clarification plus license-fit review. The actual download path stays non-public.