Bringing a new model to a new accelerator typically takes weeks to months of engineering effort.
On Tuesday, October 6, at 5 p.m. PT, we put Ignition, our hardware enablement agent, to work on the d-Matrix Corsair.
By Sunday, October 11, at 5 p.m. PT, five days later, Ignition had built and extended a custom compiler, surrounding tooling and verification pipeline to enable 39 models spanning language, vision, speech and image generation.
With that infrastructure in place, bringing a new model to the Corsair now takes hours.
15 language-model families. Vision. Speech. Image generation.
Across tested Corsair configurations, Ignition achieved performance comparable to our hand-tuned reference implementation, previously accepted by the d-Matrix team.
33 Text Models
Language
Language
Language
Language · MoE
Language
Language
Language
Language · MoE
Language · MoE
Language
Language
Language
Language
Language
Language
Language
Language
Language
Language
Language
Language
Language
Language
Language
Language
Language
Language
Language
Language
Language
Language
Language
Language
6 Models Across Modalities
IGNITION ON CORSAIR
THE INITIAL ENABLEMENT
Tue, Oct 6, 5 p.m. → Sun, Oct 11, 5 p.m. PT
Ignition built and extended a custom compiler, tooling and verification pipeline, achieving the coverage above.
A NEW MODEL, NOW
Ignition uses and extends that infrastructure to bring up the next model.
Ignition does the engineering. The compiler is one of its tools.
Ignition builds the infrastructure to map models onto the Corsair, run them on cards and check their outputs.
When a new model or model family needs additional capabilities, Ignition extends the compiler and tooling automatically, verifies the changes on hardware, and checks that existing models still work. Each improvement carries forward.
Hardware Enablement Agent
Builds, extends and operates the toolchain below.
1 / START
Hugging Face
Checkpoint + target configuration
2 / COMPILE
Custom Compiler
Place work. Split layers. Move data.
3 / RUN
Corsair Cards
Execute the compiled program on hardware.
4 / VERIFY
Check the Outputs
Bit-exact execution + original-model comparison
Give Ignition a Hugging Face checkpoint and a target: batch size, context length and card count. It uses that infrastructure to bring up the model in hours.
Ignition adapts models to different deployment goals. Depending on the model, tested configurations include:
Compressed weights trade some accuracy for capacity: larger models on fewer cards, or longer contexts on the same hardware.
Hardware execution matches the compiled program's software model bit for bit.
Quantization and numerical data types introduce differences from the original Hugging Face model. Ignition measures those differences separately.