Skip to content

Spike documentation

Spike is TU/e’s shared environment for research that needs serious GPU computing. It brings hardware, scheduling, project storage, and reusable container environments together so research teams can spend less time assembling infrastructure and more time running experiments.

Select your team profile to understand the architecture, storage, and onboarding route for your workloads before exploring the documentation:

Academic Research Track

Spike 1 for TU/e Researchers & Students

For TU/e researchers conducting high-performance AI research. Containing state-of-the-art GPU resources for training, high-performing storage & interconnects between nodes and hosted frontier Large Language Models.

●Compute:Academic NVIDIA B200 Partitions
●Storage:250 TiB High-Performing Project Space (DDN) with S3 Option
●Services:Dedicated AI engineering support, NVIDIA AI Enterprise & hosted frontier LLMs

Spike is a shared university investment, made possible by EAISI and six TU/e departments: Mathematics and Computer Science, Electrical Engineering, Mechanical Engineering, Biomedical Engineering, Industrial Design, and Industrial Engineering & Innovation Sciences.

For commercial and industry computing on Spike A, dedicated NVIDIA Blackwell B300 systems are provided through Supercomputing Brabant and hosted and operated by TU/e as a founding major partner.

That mix matters. Spike supports work across disciplines, from medical imaging and scientific machine learning to design and engineering research. The TU/e Supercomputing Center operates the shared platform and helps turn that collective investment into computing researchers can use.

Spike provides shared GPU systems and scheduling, project-scoped data sources, and container-based environments. Access is organized through projects: the project you work in determines which data, environments, and compute resources you can use.

This site covers the researcher-facing path, from getting access to running and troubleshooting workloads. Credentials, internal identifiers, quota decisions, and project-administration procedures stay out of the public documentation.