One format with a fidelity dial
A single package, served at the fidelity the hardware allows.
- CompactEdge GPUs
- BalancedClusters
- Bit-exactHigh-memory servers
Lab phase · Benidorm, Spain · Founded 2026
SpiralThink builds a model format and runtime that turns a large model into a verifiable unit you can move, shard and serve on heterogeneous hardware — from legacy servers to current datacentre GPUs — with proof that what runs is exactly what was shipped.
This is the original thesis behind SpiralThink. It describes where the work is heading, not what has been demonstrated. Measured results are listed separately under Milestones.
A universal geometric representation of model weights that allows exact reconstruction, at ratios that grow with model scale.
Very large models served on whatever machines are available — edge devices, legacy servers, compute farms, cloud — distributed like files over a peer-to-peer network, but with verification.
Fine-tunes and derived models shipped as compact, verifiable recipes, so a model's lineage can travel with it at almost no extra cost.
Making full use of the hardware Europe already has and will have, across vendors and generations, so serving large models does not depend on a single class of machine.
Efficiency measured in the memory and energy freed per token served — a quantity that can be checked, not a headline.
How to read this section: everything above is aspirational. Figures we publish elsewhere on this site are labelled MEASURED, DECIDED or PROJECTED.
This section is aspirational and does not describe current results. See the disclaimer in the legal notice.
The same model package adapts to the machine it runs on, and carries what is needed to prove it is intact.
A single package, served at the fidelity the hardware allows.
Integrity is part of the format, not an add-on.
During execution the weights remain compressed in GPU memory. The same package can therefore be served on machines with very different memory budgets.
We label every number we publish, so it is always clear what kind of claim it is.
The three are never mixed in the same figure.
A dated record of results. Each entry is labelled with its status.
The research thesis is written up as preprint v0.9 and becomes the basis of our patent work.
Signed builds (sigstore) and 99% test coverage. Open decoder (CC-BY) and open encoder (Apache-2.0).
Verified block by block on real models. TinyLlama: 156 of 156 blocks.
One kernel build running from NVIDIA Pascal (P40) to Hopper (H100).
Perplexity 0.25% lower (better) than native bf16, on WikiText-2.
4 model families, from 117M to 27B parameters, with no calibration data.
2.58 GB GPU memory peak in an isolated Gemma-27B layer benchmark, with weights kept compressed on the GPU (the full model in bf16 needs ~54 GB).
Production kernels integrated into the runtime for Hopper and single-stream decode.
A fine-tuned GPT-2 shipped as a 121 KB verifiable recipe (0.008 bits per weight). 50 of 50 tensors verified against a Merkle root.
Figures refer to the specific models, hardware and benchmarks stated in each entry.
These are lab measurements, not product commitments or performance warranties. See the disclaimer in the legal notice.
Compression built around verifiable protocols: efficiency without losing auditability.
Serving large models is limited by memory and energy. Using the hardware already deployed matters as much as buying new hardware.
Organisations want to run models on infrastructure they control, across vendors and hardware generations.
Regulation such as the EU AI Act raises the bar on documenting which model runs where. The format is designed to support these traceability and documentation requirements.
Multi-platform. Multi-model. Multi-capacity.
Not another agent — the layer agents, models and auditors rely on.
The reference decoder (CC-BY) and encoder (Apache-2.0) are open, so anyone can verify a package independently.
The industrial encoder and the GPU kernels are available under licence.
We are open to research partners, public R&D programmes and teams that distribute or serve large models.
Selective, scoped engagements:
For research collaboration, R&D programmes, technical reviews or pilot discussions, write to us.