Public product portal
Electri City Site Optimizer
Licensing and scope

Licenses unlock bounded capability. They never override doctrine or safety limits.

The licensing layer exists to keep domains, scopes, releases and rollback profiles separated. It is not a shortcut around validation, protected delivery, commercial honesty or conflict logic.

One license maps to one defined domain contextAllowed scopes stay explicit and narrowChannels and rollback profiles remain domain-boundCommercial placeholders stay honest until confirmed
Prepare a commercial inquiry Review access request readiness
Reference Modeobserve_only
Portal Gateapproval_required
Homepage Status200
Response Time236.9 ms
HTML Size183,759 bytes
Sitemap Status200
Readiness summary

Portal-visible readiness without protected execution

Support readinessoperator input required

Contact: operator input required; Email: operator input required.

Commercial readinessoperator input required

Commercial inquiry path: operator input required; Pricing: operator input required; Packages: source not yet confirmed.

Access readinessapproval_required

Portal copy is request-ready, but live request handling remains protected.

Download readinessapproval_required

Portal gate: approval_required; no open download or private route exposure.

Domain binding

No vague multi-domain entitlement

Each license object is intended to bind to a specific domain and explicit scope set. That prevents accidental cross-domain effects and keeps future rollout decisions explainable.

  • Bound domain required
  • Wildcard or ambiguous domain sharing is out of scope
  • Reference site and customer sites stay separated
Who this licensing model is for

Best suited for operators who can define domain, scope and ownership clearly

A later license conversation makes sense when the target domain is known, the WordPress stack can be named and the requested scope can stay narrow enough for validation and rollback.

  • Homepage-only pilots remain possible
  • Template or module ownership should be explainable
  • Approval remains required for real execution
See the plugin execution constraintsCheck what support needs from you
Commercial preparation

Pricing and commercial packaging are prepared as placeholders, not promises

The portal now makes the commercial gap explicit in a cleaner way: the licensing model is ready for conversation, but pricing structure, commercial packaging and issuance terms remain open fields until operator confirmation exists.

  • Pricing model: operator input required
  • Commercial inquiry path: operator input required
  • Quoted package tiers: source not yet confirmed
What remains approval_required

No public licensing step can bypass the protected execution layer

Even a future commercial or licensing conversation does not create automatic delivery rights. Actual entitlements, domain activation, policy delivery and private downloads stay protected.

  • Final customer entitlements: approval_required
  • Protected release and policy delivery: approval_required
  • Any real domain activation: approval_required
Review protected delivery limitsSee why approval stays mandatory
What is not publicly available

Commercial preparation does not imply pricing completeness or checkout

This page can now show commercial readiness more clearly, but it still does not include public pricing tables, self-service purchase flows, activation buttons or domain entitlement issuance.

  • No public checkout or checkout link
  • No automatic license issuance
  • No hidden fulfillment path behind the CTA layer
FAQ

Frequently asked questions

Can one license safely control multiple unrelated customer domains?

No. The platform is modeled around domain-bound isolation and explicit scope separation.

Does licensing automatically publish plugin downloads?

No. Download delivery remains gated by license, entitlement, channel and protected access rules.

Does this page already include public pricing or a commercial checkout flow?

No. Pricing and commercial delivery details remain operator input required and are not invented on the public portal.

Next step

Use licensing to qualify fit before any later protected step

If the domain, scope and ownership picture is clear, continue to downloads and support to prepare the request path without overpromising delivery.

Go to access-request readinessOpen support and inquiry guidance