Commercial Beta Terms and Scope

1. What "Commercial Beta" means

CROSSPAD is offered as a Commercial Beta: a paid, supported service with a deliberately limited scope. "Beta" describes the scope and the pace of change, not the seriousness of our commitments. Everything in the Terms, the Refund and Remediation Policy and the Security, File Retention and Deletion Policy applies in full during the Commercial Beta.

What it means in practice:

• The list of supported inputs and constructs (Section 3) is short and explicit. Anything not listed is Unsupported.
• Features, report formats and workflows may change between Orders. They will not change for an Order after Commencement.
• Some features described on our website as "coming later" (Section 6) are not part of any Order until they are published as available.

2. What you receive for an Order

For each Supported Input in an Order:

3. Supported Scope at launch

3.1 Unsupported at launch

The following are outside the Supported Scope. The Analysis will return Blocked, or the report will mark the item UNSUPPORTED. They are not Material Defects and are not covered by Remediation.

• An ASCII-format .PcbDoc whose conversion cannot be reconciled. We convert the ASCII text form and check the conversion against an independent count of the board; where the two disagree we do not migrate it — the Analysis returns Blocked or the report marks the file UNSUPPORTED, and nothing is charged.
• Files from Altium versions earlier than version 6 (pre-V6 binary format).
• Schematic documents (.SchDoc), project files (.PrjPcb) and libraries (.SchLib, .PcbLib) — on their own, and equally inside an accepted archive, where they are ignored rather than migrated. They are not converted, not validated under Section 4, and appear in no evidence category of Section 5 except UNSUPPORTED. Sending a project inside a .zip gets the board in it migrated; it does not get the project migrated.
• An archive holding more than one board that no .PrjPcb inside it resolves to a single one of. We do not choose your board for you: the Analysis returns Blocked and names every board found, so you can send the one you meant. The same applies to an archive we cannot open as a zip, one that holds more files than we unpack, and one that expands beyond the size we unpack. A member that would be written outside the archive is not a refusal: it is skipped, listed in the report, and the board is migrated without it.
• Proprietary rule engines and interactive-routing rule sets that have no KiCad representation (for example ActiveRoute rule sets).
• External assets not embedded in the Source File (for example external STEP models or external libraries), unless you provide them when requested.
• Embedded scripts, database links, version-control metadata, Altium "variants" beyond what the report states.
• Manufacturing outputs (Gerber, drill, pick-and-place) — the Deliverable is a KiCad design, not a manufacturing package.
• Any construct the report explicitly marks UNSUPPORTED.

4. Domains we validate

Within the Supported Scope, validation compares the Deliverable with the Source File for:

• components and designators;
• nets and pin connectivity;
• copper layers and layer mapping;
• board outline and geometry;
• footprints and pad geometry;
• tracks, arcs, vias, fills and zones;
• design rules and net classes (accounted for and mapped where a mapping exists);
• differential-pair naming and membership;
• 3D model references (presence, not visual fidelity).

The report states, per domain, which evidence category applies.

5. Evidence categories (how to read the report)

A Conforming Deliverable is one where every domain in Section 4 is VERIFIED, TRANSLATED_EQUIVALENTLY or REPAIRED_AND_REVALIDATED, with any remaining items disclosed in one of the other three categories.

We do not publish numeric "confidence scores" for a migration. We publish categories, counts, and the evidence behind them.

6. Not included (future features)

The following are described on our website as planned and are not part of any Commercial Beta Order until we publish them as available with their own terms:

• Expert Engineering Review by a human engineer (planned add-on).
• Schematic migration and full-project migration.
• Back-catalogue archive assessment and batch migration workflows beyond the multi-project tiers listed at checkout. (This is the other sense of the word: a library of many projects, assessed and quoted in bulk. A single .zip holding one board is a Supported Input under Section 3, not this.)
• API access, SSO, procurement features and enterprise data-residency options.
• Manufacturing output generation.

7. Beta limitations you accept

• Processing times vary with board complexity; we state target times in the Support and Remediation Commitments but do not guarantee them.
• Report wording, categories and formats may be refined; the meaning of the categories in Section 5 will not be weakened.
• We may limit the number of concurrent Orders per Account during the Commercial Beta.
• Feedback you give about the beta may be used to improve the service (Terms Section 11.5).

8. Changes to scope

We may widen the Supported Scope at any time. We may narrow it for new Orders with notice on this page; an Order placed before the change keeps the scope shown at its checkout.

Changes made under this clause