Local beta
Explore the implemented workflow on your own device.
- STEP and STL browser parsing
- Reference capability profiles
- Multi-profile fit matrix
- JSON and ZIP evidence exports
- Community-style beta support only
Commercial beta
The browser beta is free to evaluate. Paid engagements are deliberately pilot-led until the product passes its published qualification gates and proves measurable RFQ-rework reduction.
There is no self-service paid account, SLA, hosted collaboration, or enterprise identity layer in the current browser beta. Scope, data approval, support, and deliverables belong in a signed pilot agreement.
Pricing is anchored to a bounded outcome: fewer clarification loops and more traceable supplier-readiness decisions.
Explore the implemented workflow on your own device.
Validate the workflow against a labeled, non-production corpus.
Proposed annual term after a successful pilot and release qualification.
Proposed contracted deployment for broader supplier networks.
Targets are exit criteria, not current performance claims.
Zero independently labeled, implemented blockers represented as passed.
Sampled exports retain exact artifact hashes, passport, rule set, results, and claims boundary.
Measure hands-on preflight time and RFQ clarification loops against a frozen baseline.
A public sales inbox and automated checkout are not live. Request private pilot terms through the project owner or the channel that shared this beta. Do not send CAD, drawings, credentials, personal data, or restricted program information in an initial inquiry. Team and Scale terms are proposals pending successful qualification, contract review, and a deployment operator with published security and privacy contacts.
No. The current application has no user-file upload endpoint or usage billing. The host still receives ordinary static page requests.
No. Team and Scale are proposed post-pilot terms, not instantly purchasable subscriptions.
No. Every plan remains bounded by the same product scope and required human and supplier approvals.
Only after the operator and agreement explicitly approve the environment, data class, handling, retention, and incident route.
Run the included local sample and inspect the rule-level evidence, rescue actions, and blind spots.