PILOT PROGRAM
The 90-Day Pilot
Your infrastructure. Your workloads. Your sealed receipt.
A pilot engagement produces a SHA-256 sealed benchmark receipt against the licensee's own infrastructure. Not a demo environment. Not a sandbox. Not a proof-of-concept on synthetic data. The production stack, governed by the Omni-Compass law, benchmarked with the four-arm isolation protocol, sealed with SHA-256, and delivered as a cryptographically verifiable receipt.
Start a conversationThe proof is the pilot.
If the governing law does not hold on the licensee's infrastructure, the engagement ends there. The mathematics are either true or they are not. The benchmark determines which. This is not a sales process. It is a scientific determination.
HOW IT WORKS
Four Phases. 90 Days.
Infrastructure Assessment
The founder reviews the licensee's infrastructure profile — stack composition, workload types, hardware configuration, and deployment topology. A pilot scope document is produced and agreed upon before any engagement begins.
Baseline Benchmark (Arm A)
The four-arm isolation protocol is deployed against the licensee's production-adjacent environment. Arm A establishes the unmodified baseline. Every measurement is recorded. The baseline is sealed before the governing law is applied.
Governed Benchmark (Arms B, C, D)
The Omni-Compass governing law is applied to the stack. Arms B and C measure direct resource gain and whole-system composition. Arm D (cloud/GPU) is added when the licensee's stack includes GPU workloads. Every run is recorded. Every number is live.
Sealed Receipt Delivered
The complete benchmark output is sealed with SHA-256. The receipt includes the methodology report, raw JSON files, the fingerprint, and the gain numbers. The receipt belongs to the licensee's infrastructure record permanently.
WHAT YOU RECEIVE
The Sealed Receipt Package
SHA-256 Sealed Benchmark Receipt
A cryptographically sealed record of every benchmark run against the licensee's infrastructure. Verifiable in-browser. Fingerprint on record. Permanently attributable to the specific infrastructure stack it was produced against.
Methodology Report
A complete written record of the four-arm isolation protocol as applied to the licensee's stack. Includes arm definitions, workload categories, hardware configuration, and statistical parameters.
Raw JSON Output Files
Every benchmark run produces structured JSON output. The raw files are delivered in full. No aggregation. No smoothing. The complete record of every measurement taken during the engagement.
Monte Carlo Validation Report
Monte Carlo validation run against the licensee's benchmark data. The statistical confidence interval is computed and reported. The validation methodology is the same as the published V26 engine.
Gain Analysis
A structured analysis of the governing law's contribution to the licensee's infrastructure performance. Expressed as percentage gain per category, per arm, and as a whole-system number. The $-value translation is included at the licensee's stated cloud spend.
Licensing Recommendation
Based on the pilot results, the founder produces a licensing recommendation. If the governing law held, the recommendation includes the appropriate license structure, scope, and terms for production deployment.
FEE SCHEDULE
Pilot Engagement Fees
Pilot fees are structured by the licensee's annual cloud spend. The fee is a one-time engagement fee, not a recurring charge. It is credited against the first year of an enterprise license if the pilot proceeds to licensing.
| INFRASTRUCTURE SCALE | PILOT FEE |
|---|---|
| Under $10M annual cloud spend | Contact for terms |
| $10M – $50M annual cloud spend | Contact for terms |
| $50M – $250M annual cloud spend | Contact for terms |
| $250M+ annual cloud spend | Contact for terms |
Full pilot fee schedule and terms are available on the Licensing page. Operative documents — mandate, licensing agreement, schedule, and deployment phases — download here.
COMMON QUESTIONS
Before You Engage
The proof is the pilot.
Start a conversation. The founder will review your infrastructure profile and determine whether a pilot engagement is appropriate. No automated responses. No sales team.
EXTERNAL REFERENCES
© 2026 DUBRA SOFTWARE INC. / THE OMNI-COMPASS LLC · ALL RIGHTS RESERVED · CREATED AND DEVELOPED BY THE OMNI-COMPASS LLC / DUBRA SOFTWARE INC.