Enterprise qualification
Prove release-control value before production rollout.
DatumRelay starts with a controlled six-to-eight-week engagement: frozen evidence, independent labels, adversarial testing, and live shadow mode against a measurable RFQ-rework baseline.
Contract-ledShadow modeNo file-metering
QCommercial ranges do not imply general availability.There is no self-service paid account, production SLA, or enterprise identity/control plane in this qualification release. A customer-specific qualification remains NO-GO until its signed record names the operator and sponsor, monitored private incident contacts, and authorized data class; support, deliverables, and stop conditions also belong in that agreement.
A qualification-led path
Pricing is anchored to a bounded outcome: fewer clarification loops and more traceable supplier-readiness decisions.
Technical evaluationLocal assessment
No charge
Inspect the bounded workflow with synthetic or approved non-sensitive data.
- STEP and STL browser processing
- Reference capability profiles
- Exact material/finish/CAD route tuples
- Buyer/supplier export and offline verifier
- No support, SLA, or production authority
Open qualification client
Recommended entryQualification
$25k–$50k fixed engagement
Six to eight weeks of controlled evidence, replay, and live shadow mode.
- Claims, security, and data workshop
- Controlled supplier capability routes
- Frozen corpus and independent labels
- Adversarial bench plus shadow mode
- Evidence-backed stop, extend, or candidate decision
Review pilot access
Post-qualification rangeDepartment
$60k–$120k ARR + implementation
One controlled business unit or process family after successful qualification.
- Named deployment and governance
- Controlled rule/schema updates
- Release and regression evidence
- Operator runbook and enablement
- Contract-defined support
Availability notes
Post-qualification rangePrivate enterprise
$150k–$350k ARR
Multi-team or private deployment; typically $50k–$150k implementation.
- Multiple controlled cohorts
- Identity, audit, and integration scope
- Custom qualification corpus
- Named change and incident owners
- Contracted security, recovery, and support
Availability notes
What a pilot must prove
Targets are exit criteria, not current performance claims.
Safety of in-scope blockers
Zero independently labeled, implemented blockers represented as passed.
Traceable evidence
Sampled v3 exports retain exact artifact hashes, canonical capability-profile digest, exact rule set/results, and claims boundary.
Workflow value
Measure hands-on preflight time and RFQ clarification loops against a frozen baseline.
How to request a pilot
A public sales inbox and automated checkout are not live. Request private pilot terms through the project owner or the channel that shared this qualification release. Do not send CAD, drawings, credentials, personal data, or restricted program information in an initial inquiry. Department and Private enterprise terms are proposals pending successful qualification, contract review, and a deployment operator with published security and privacy contacts.
Common questions
Does the local assessment upload or meter files?
No. The current application has no user-file upload endpoint or usage billing. The host still receives ordinary static page requests.
Is Department available self-service?
No. Department and Private enterprise are proposed post-qualification terms, not instantly purchasable subscriptions.
Does paid access certify a release?
No. Every plan remains bounded by the same product scope and required human and supplier approvals.
Can a pilot use sensitive production data?
Only after the operator and agreement explicitly approve the environment, data class, handling, retention, and incident route.
See the product before the proposal.
Run the included local sample and inspect the rule-level evidence, rescue actions, and blind spots.
Run the sample