TypeSafe's customer agreement forbids publishing benchmarks of its decision model

Section 2.3 lists what a customer will not do. Clause (f) is that customers will not "publish benchmarks or performance information about the Services." Clause (c) separately bars reverse engineering or deriving the underlying ideas, algorithms or structure. Two other sections give that restriction force. Section 6 lets TypeSafe suspend a customer's access immediately on a Section 2.3 breach. Section 12.3 puts a Section 2.3 breach outside the liability cap, which otherwise limits each party to the greater of twelve months of fees or fifty dollars. TypeSafe sells Jev as a System One model for fast, typed, confidence-aware decisions in software, meaning a component that sits inside a pipeline.

Why it matters: Customers can benchmark Jev against alternatives, but the contract prevents them from publishing the results for outside scrutiny. A breach of that restriction sits outside the agreement's liability cap. Teams should account for that clause before putting Jev into a harness.