Pilot terms

These terms explain the request, scope, commercial agreement, and evidence boundaries of a Mirage pilot.

Effective August 29, 2026

Request and acceptance

Submitting the form requests a fit review. It does not create a purchase, reserve capacity, or require Mirage to accept the work. A pilot starts only after both sides confirm the written scope and commercial terms.

Pilot scope

The written scope identifies the approved product release, bounded product surface, priority scenario, deliverables, timing, and commercial terms. A typical pilot includes an evidence-linked Hub report, PDF, and review call.

The current offer supports a public single-host website or a simple public endpoint in a dedicated private workspace. Authenticated or SSO flows, multi-origin journeys, uploaded builds, and shared-tenant production access are not part of the standard offer.

For a public site or endpoint, you declare the release SHA and Mirage does not independently bind it to the public bytes. Mirage discovers executable journeys on the approved surface; the priority-scenario brief guides planning and review but does not guarantee route execution.

Contracting party and governing law

The accepted written scope or order form identifies the contracting entity, business address, and governing law. Those accepted documents control if this public page differs from them.

Public contracting name: not configured on this public site; see the accepted commercial agreement. Governing law: not configured on this public site; see the accepted commercial agreement.

Authorization and safe inputs

You confirm that you own the target or have authority to request testing and provide the agreed materials. You must not submit credentials, personal customer data, malicious code, or material that violates another party's rights through the public form. Any sensitive transfer needed for an accepted pilot uses the path agreed during scoping.

Evidence and decisions

Mirage provides directional synthetic-user evidence within the measured scope. It does not validate market demand, predict real-customer behavior, certify compliance, provide penetration testing, or guarantee that every product issue will be found. The report is non-gating and your team owns every release and product decision.

Providers and data path

The written scope identifies the target, workspace, model-provider path, evidence handling, and any provider usage charges relevant to the pilot. Screenshots, rendered text, and task context may be sent to that model provider. Review the privacy notice before commissioning work.

Schedule, changes, and cancellation

The written agreement states the delivery schedule and any change, cancellation, or refund terms before work begins. Work outside the confirmed target, release, scan surface, or planning brief requires separate written agreement.

Product and report rights

You retain rights in your product and materials. Mirage retains rights in its engine, methods, and reusable tooling. You may use the delivered report and PDF internally. Mirage will not publish your name, product, screenshots, or results as a case study without separate permission.