01
Package
Pinned source, dependencies and build instructions resolve into a known artifact.
Reproducibility at every layer
Compose packages, services, nodes and clusters into one declarative, idempotent system—ready to reproduce from a laptop test to a production platform.
Explore the layersREVYC / HPC DEFINITION
revyc-deployment
name "lab-hpc"
targets : ' hetzner
login-node "login-01"
compute-node "compute-01"
compute-node "compute-02"
ONE DEFINITION COMPLETE CLUSTER
About Revyc
Reproducibility should not stop at the package boundary. Revyc carries the same model upward through services, machines and clusters until the entire platform can be versioned, reviewed, tested and rebuilt as a whole.
The abstraction stack
01
Pinned source, dependencies and build instructions resolve into a known artifact.
02
Software, configuration, users and lifecycle become one deployable unit.
03
Operating system, policy and workload are produced from one definition.
04
Compute, control, identity, networking and storage connect without manual glue.
05
The complete platform becomes one versioned, reviewable blueprint.
First vertical
HPC and system platforms depend on compute, storage, identity, scheduling and workflows moving together. Revyc provides those parts as one platform instead of a collection of procedures.
Test the complete definition at small scale. Review the code. Deploy as package, container or full system. Reproduce it on-prem or in the cloud without changing a line.
The Revyc promise
Define it. Compose it. Reproduce it.
Build with Revyc
We have started with reproducible HPC infrastructure, more to come. Talk to us about the system you cannot afford to lose—or fail to recreate.
Reproducible infrastructure, from package to complete platform.
TALK TO REVYC