3SWAI
Accelerate everything

Fewer GPUs for the same AI.

3SWAI builds a quantization format and GPU kernels that cut the bytes a GPU streams per generated token – so operators serve the same models with fewer GPU-hours, inside the serving stack they already run.

−16.4 %mean KL vs the best open 4-bit format, Llama 3.1-70B, equal bits
−15.0 %mean KL vs the same baseline, Qwen3-32B, equal bits
0.5–8.7bits per weight, adjustable per tensor

Internal measurements, August 2026, against GGUF Q4_K_M with importance matrix at matched bits per weight. Independent validation by the Jožef Stefan Institute scheduled for September 2026.

Inference is now the bill – and it is bound by memory, not maths.

Inference outspends training

Gartner forecasts 2026 inference spending on AI-optimised infrastructure at $23.3 bn, ahead of training at $19.0 bn – the first time inference leads.

Decode streams every weight

Generating each token means streaming the whole model through the GPU. Throughput is governed by bytes per weight, not by arithmetic.

Everyone is already at 4-bit

AWQ, GPTQ and GGUF Q4 are standard practice. The open question for every operator is how few bits you can use before quality visibly drops.

Unleash every chip

A better format – not a new stack.

Our quantizer converts a BF16 checkpoint into a packed format with continuously adjustable precision per tensor. Our read kernels multiply on that format directly inside your runtime. You keep vLLM, TensorRT-LLM or ROCm; you change the weights, not the stack.

Per-tensor precision

0.5 to 8.7 bits per weight, chosen per tensor. You pick the operating point on the quality–memory curve per model instead of a fixed 4 / 6 / 8-bit grid.

Read kernels, not a runtime

Consumed the way AWQ or GPTQ checkpoints are. NVIDIA (CUDA) first; ROCm path for AMD to follow. Vendor-neutral by design.

Quantize once, serve anywhere

The quantizer runs once per checkpoint on a single server. Serving needs only our read kernels in your existing stack.

BF16 checkpoint
→
3SWAI quantizer + kernels
→
Your vLLM / ROCm stack

Measured, filed – and disclosed.

We publish only numbers from logged runs with a named model, machine, baseline and bits per weight. Baseline: GGUF Q4_K_M with importance matrix, the strongest widely used open 4-bit recipe. Reference: BF16.

−16.4 %mean KL divergence, Llama 3.1-70B at 4.86 BPW
−15.0 %mean KL divergence, Qwen3-32B at 4.81 BPW
−23.8 %median KL, Llama 3.1-70B
=MMLU unchanged on Qwen3-32B (0.8198 vs 0.8152, within noise)

Patent filed

US utility patent application filed November 2025, assigned to Ainnovyze S.à r.l.; response to the first office action submitted. PCT extension and a second filing in preparation.

Independent validation

LOI with the Jožef Stefan Institute for independent testing and benchmarking; validation package delivering September 2026. Nothing has been independently verified yet – and we say so.

What we do not claim

No speed-up multiple, no "10×" of anything, no saving we have not measured. Open items: the fewer-bits-at-equal-quality point and GPU tokens/s are being measured now. Full benchmark reports available under NDA.

Where fewer bytes pay off.

Bytes per weight govern decode throughput while the GPU is memory-bound. That is most real deployments – and we say where it is not.

Large open-weight models

32B–70B and above, long contexts, moderate concurrency. On-premises and private deployments where the model must fit and stream on your own GPUs.

Memory-bound accelerators

AMD Instinct and LPDDR-based inference cards, where memory – not compute – is the binding constraint and vendor formats offer no native low-bit path.

Not hyperscale batch serving

At very high batch sizes on H100 / Blackwell with native FP8 / NVFP4, decode becomes partly compute-bound and the benefit of fewer bytes shrinks. Prefill is not where our advantage lies.

Three effects follow from fewer bytes: fewer GPUs for a fixed load, a model that needed two GPUs fitting on one, and more memory left for KV cache – more concurrent requests, lower energy per token.

A four-to-six-week pilot on your GPUs.

One question, answered on your hardware: how many tokens per second per GPU, at what quality, on your model.

We quantize your model

One open-weight model you already serve, at two operating points.

You run our kernels

Inside your existing serving stack, on your NVIDIA or AMD GPUs. An engineer for two to three days over the period is enough.

We both log the result

Quality (KL, perplexity, a task benchmark of your choice) and throughput against your current 4-bit deployment under one protocol.

You get the measured saving and first-customer pricing. Commercial model: a per-GPU annual licence installed on your own hardware, priced against the saving delivered – or native support through a silicon vendor licence.

Book a pilot

Any data centre. Any silicon. Your infrastructure.

Vendor formats are fixed-grid and hardware-specific. Ours is per-tensor continuous and hardware-agnostic, delivered as read kernels for the accelerator you run. Nothing leaves your network: the quantizer runs on your server, the kernels run in your stack. Engineered in Europe, deployed anywhere.

Vendor-neutralOn-prem onlyNo stack changeNVIDIA now · AMD next

Ten years of building together.

Nataša and Uroš have built together for a decade – from graphene production technology to satellite thrusters. In 2025 they focused on 3SWAI; Anže and Jan completed the founding team.

Nataša Magister

CEO & co-founder. 30+ years leading teams across South-East Asia and Europe; prior exit. Business, go-to-market, investors.

Uroš Kejžar

CTO & co-founder, primary inventor. Mathematics and engineering across welding equipment, space technology and data compression; architect of the quantization method and inference engine.

Anže Kejžar

Co-founder, lead developer, co-inventor. Quantization toolchain, runtime, GPU kernels, benchmarking and integration.

Jan Martinšek

Co-founder and first investor. Capital and business development.

Prove the saving on your GPUs.

Book a 30-minute call. We scope a four-to-six-week pilot on one model you already serve.

Book a pilot

Backing vendor-neutral AI infrastructure.

We are raising a round to reach one milestone: a GPU serving product an operator can deploy without changing its stack, and the first customers paying for it. Request the brief and benchmark reports.

Investor enquiries
3SWAIQuantization format and GPU kernels for fewer GPU-hours per token.
3SWAI d.o.o., Koliška ulica 2, 1230 Domžale, Slovenia
Part of Ainnovyze S.à r.l., Luxembourg
hello@3swai.com
LinkedIn
Privacy
© 2026 3SWAI. All rights reserved.