Pre-purchase · Enumerated answers only
Check the contract without sharing the data.
Eight boundary questions compare your intended use with v1.1.0. No dataset, schema, path, code, identity, account, or free text is accepted. The result is compatibility routing—not an audit and not license acceptance.
Eight compatibility checks
Separate product fit from preparation work and excluded use.
The checker evaluates only these broad selections. It does not infer your schema, inspect bytes, test a join, quote custom work, reserve delivery capacity, or grant a license.
What the result means
Compatibility routing, not a free audit.
- Likely v1 fit means the selected format, runtime, clocks, paths, volume, period semantics, and license align with the published boundary; written acceptance is still required.
- Preparation needed means the use may fit after the data contract, runtime, path layout, or timestamp meaning is made explicit.
- Outside v1 or license means a required format, scale, delivery type, or use right is not offered by the current product.
- The checker never reads data and cannot determine whether a real audit would pass, fail, find leakage, or be fit for a decision.
Need the evidence behind the boundary?