Is self-hosting automatically cheaper?

No. Include setup, hardware, maintenance, incident handling and team time.

Does a model name establish usage rights?

No. Verify the release and service terms for the intended use.

Wan and Kling: compare production and operation

Inspect the actual solution

Record version, supplier, access and terms. A model name does not establish local deployment, rights or costs; verify the specific release. General openness is not a licence assessment.

For self-managed infrastructure, assign installation, updates, incidents and storage. For hosted access, clarify support and feature-change handling. Both need ownership.

Run the complete ad task

Match product, action and acceptance criteria. Separate setup time from recurring variants and corrections, including realistic failure recovery.

Test whether a colleague can take over using saved information. Undocumented dependence on one machine matters. Generation price alone cannot settle operational suitability.

Separate setup from recurring operation

Split setup, access, documentation and the first accepted sample from recurring production, revisions, checks and changes. Generation cost covers only part of the latter.

Test a realistic interruption or missing-version problem, assigning recovery and distinguishing measured time from assumptions.

Inspect reference storage and access through actual settings and terms rather than model-name assumptions.

Choose an operable solution with clear ownership. Technical control may justify complexity; simpler access may reduce specialist dependency. Decide from actual needs.

Record the actual release, service and access method before judging operational costs or permissions. A general claim about open access does not establish the licence for the intended use. Specific storage, reference handling and support questions need answers from the relevant configuration and terms.

Separate one-time installation work from recurring production and revisions. Include realistic interruption recovery where that is part of the workflow. Then check whether a colleague can resume the task using saved settings and instructions. An undocumented dependency on a single machine or specialist should remain visible in the decision, even if the nominal generation price looks attractive.