Public product portal
Electri City Site Optimizer
Pricing, scope and protected delivery

Choose the public annual plan before any protected delivery step begins.

This page explains the visible Single, Studio and Agency offer tiers, who each plan fits, what stays included, what remains outside the public offer and why protected delivery still stays deliberately gated.

Clear public tiers with explicit exact licensed domain countsNo open checkout, login, activation or package fulfillment hereProtected delivery, validation and rollback remain separate by design

Protected delivery stays deliberate

The public pricing model is visible on purpose. Delivery, activation, private download and customer execution remain protected because the Suite is designed around scope control, validation evidence and rollback 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: configured public tiers; Packages: configured public tiers.

Access readinessapproval_required

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

Legal readinessconfigured

Public legal pages are source-synced and remain presentation-level only; no protected function is opened here.

Download readinessapproval_required

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

Compare the public annual plans

Single, Studio and Agency stay visible, bounded and protected.

Each public plan keeps pricing, exact licensed domain scope, documentation and licensed download access visible while activation, delivery and execution remain gated.

Focused public entry

Single

EUR 199.00 / year

Annual commercial use for one exact licensed domain.

Includes documentation and licensed download access.

Single is the focused annual plan for one exact licensed domain. It is designed for operators who want a clear, protected entry into the Suite with documentation and licensed download access.

Portfolio public tier

Studio

EUR 499.00 / year

Annual commercial use for three exact licensed domains.

Includes documentation and licensed download access.

Studio is the annual plan for up to three exact licensed domains. It fits small portfolios, multi-site operators and tightly managed WordPress environments that need the same protected Suite model across a limited domain set.

Agency public tier

Agency

EUR 1490.00 / year

Annual commercial use for ten exact licensed domains.

Includes documentation and licensed download access.

Agency is the annual plan for up to ten exact licensed domains. It is built for agencies and advanced operators who need a stronger licensed footprint while keeping domain scope, protected delivery and Suite discipline clearly bounded.

Who this is for

Choose the plan that matches your real exact licensed domain scope

Single is the clearest fit for one operator and one exact licensed domain. Studio fits small, tightly managed portfolios. Agency fits larger but still explicitly bounded domain sets that need the same protected Suite model.

The public offer is therefore not just a price table. It is a scope filter that helps decide whether the next conversation belongs in licensing, downloads preparation or support clarification.

  • Single for one exact licensed domain
  • Studio for three exact licensed domains
  • Agency for ten exact licensed domains
Included across all public plans

What the public offer includes clearly and consistently

Every visible plan keeps the same basic public structure: annual commercial use within the exact licensed domain count of the selected tier, plus documentation and licensed download access.

That consistency keeps the public offer easier to compare without implying that lower-friction delivery, broader rights or deeper services are already included.

  • Annual commercial use within the selected exact licensed domain count
  • Documentation
  • Licensed download access
Not included under the public offer

What the public offer does not expand or silently promise

Not included under the public offer: open multi-domain rights beyond the licensed domain count, custom implementation, migration, development services, or any rights beyond the public license scope unless separately agreed in writing.

This keeps the page commercially honest. It shows a stronger public model, but it does not pretend that pricing automatically includes wider delivery, custom work or unbounded multi-domain rights.

Protected delivery

Why licensed download access remains protected and scope-bound

Licensed download access remains protected and scope-bound. Public pages describe the offer, but they do not open private delivery, login, activation, or customer execution flows.

That protection matters because the Suite is built around scope clarity, plugin coexistence, validation evidence and rollback readiness. Public visibility is allowed. Unbounded execution is not.

  • No anonymous production package delivery
  • No instant activation or customer execution path from this page
  • Protected delivery remains tied to domain, scope and later approval
Trust, safety and rollback

Why exact licensed domain counts and guarded delivery improve trust

Exact licensed domain and exact licensed domains stay visible because the Suite is not meant to leak across unclear site boundaries. The public pricing model is stronger when domain limits stay explicit instead of implied.

The same principle supports safer rollback: if scope stays bounded, validation and rollback decisions stay easier to explain and safer to reverse.

  • Domain counts stay explicit instead of implied
  • Rollback reasoning stays clearer when scope is narrower
  • Protected delivery reduces accidental cross-domain drift
What to prepare

What to prepare before requesting access or activation context

A serious next step starts with the exact target domain, current WordPress stack, source ownership for the homepage output and later rollback responsibility.

Commercial inquiry path: operator input required. Pricing model state: configured public tiers. Package tiers state: configured public tiers.

  • Exact licensed domain
  • Theme, builder and active SEO plugin inventory
  • Rollback owner and validation owner
What remains approval_required

What remains protected after this public offer page

Any real license activation, package delivery, private download, protected customer access or live execution step remains approval_required.

  • Access readiness: approval_required
  • Download readiness: approval_required
  • Customer authentication: approval_required
  • Protected execution routes: non-public
FAQ

Frequently asked questions

Can I buy and download directly from this page?

No. This page explains the public offer and the guarded next steps only. Open checkout, customer login, activation and package fulfillment are not exposed here.

Why are exact licensed domain and exact licensed domains stated so explicitly?

Because the product stays safer when domain scope is explicit. The public offer is intentionally bounded to one, three or ten exact licensed domains instead of vague multi-domain rights.

What does licensed download access mean on a protected offer page?

It means the licensed plan includes download eligibility, but delivery remains protected and scope-bound. Public pages describe the offer without opening private download, login or execution routes.

Which plan usually fits which operator?

Single fits one exact licensed domain, Studio fits a small tightly managed domain set, and Agency fits agencies or advanced operators who need up to ten exact licensed domains without relaxing scope discipline.

Next step

Use terms, licensing, downloads and support as the public preflight path

Review the public terms, confirm domain fit, inspect guarded access preparation and clarify support context before any protected delivery step is considered.