Upstream
Code reviewed, merged, expanded, and shipped by an independent project.
Deployments
Work running today.
Our standard is excellence. Our reputation is built on speed and reliability. Millions of people around the world already rely on our code in Windows and JRuby. Millions more will rely on what we release next. For all of them, there are no acceptable compromises.
Independent proof
Systems adopted beyond Valen Systems.
A deployment belongs here when the work has crossed into a customer system, an operating environment, or an upstream project with public evidence attached.
Upstream deploymentShipped
Valen Systems code ships worldwide in JRuby 10.1+.
Co-founder Troy Mallory’s builtin-tracking architecture was merged upstream, expanded by JRuby maintainer Charles Oliver Nutter, and carried across core runtime fast paths.
Read the JRuby deployment →- System
- JRuby
- Layer
- Core runtime infrastructure
- Status
- Shipped upstream
- Release
- JRuby 10.1+
What qualifies
One standard across every deployment.
The commercial setting can change. The proof standard doesn’t.
Customer
Permissioned customer systems with the delivered result and operating boundary attached.
Operating
Valen Systems systems running in a real environment with current-state evidence.
Proof earns its own route.
This library will grow only when a deployment has enough independent evidence, technical depth, and commercial meaning to stand on its own. Research explains how the work was developed. Deployments show where it crossed into use.
Working through a hardware or runtime decision? Explore compute evaluations