For enterprises
Run frontier-scale models on hardware you own, inside your own walls. Fewer accelerators per model means lower capital cost, and keeping sensitive data on-site stops being a trade against model quality.
The Technology page covered how M16 works. This page is about why it matters. Almost every demanding workload in computing, from AI to film to forecasting the weather, comes down to the same two things: storing enormous amounts of numbers, and moving them fast enough to multiply them. Those are exactly what a stit changes.
0111001011110000100101001100000100111011011011100000100001011010Every application below benefits from the same property. A stit is a single unit that can be in any one of sixteen states, where a bit can only be in one of two. It is not a package of bits. But because one stit can hold one of sixteen values on its own, any number needs far fewer of them, so the same chip stores more and moves less. This improves data transfer rates and bandwidth.
A stit is one physical unit that settles into any one of sixteen states. It is a new kind of unit, not four bits bundled together.
Telling apart the 256 possible values of a byte takes eight binary cells, or two stits. The same chip area holds more.
Moving data costs far more energy than computing on it. Fewer units per value means less to move.
M16 is in development. The figures on this page are stit-for-bit comparisons that follow from the architecture, not benchmarks of finished hardware.
A large language model is mostly a very large pile of numbers, its weights, plus a fast way to multiply them. A 70-billion-parameter model stored at 16 bits per weight is about 140 GB. That is more than any single consumer graphics card holds, so today it gets split across several expensive accelerators or squeezed down until it loses quality.
A binary cell can only hold one of two values. A stit can hold one of sixteen, so the same number needs far fewer of them: a 16-bit weight takes sixteen binary cells, or four stits. Weights that fill about 1.1 trillion binary cells fit in about 280 billion stits. A model that needed a rack can need a server. A model that needed a server can fit in a workstation.
70B weights at 16-bit precision ≈ 140 GB
One weight: 16 binary cells, or 4 stits
Binary: 1.12 trillion cells (2 states each)
M16: 280 billion stits (16 states each)Run frontier-scale models on hardware you own, inside your own walls. Fewer accelerators per model means lower capital cost, and keeping sensitive data on-site stops being a trade against model quality.
Models that live in a data center today could run on a desktop or laptop: private, offline, and without a subscription. Your notes, code and photos never have to leave your machine to be useful to an assistant.
A model remembers a conversation in its KV cache, which grows with every token. A 70B-class model with a 128,000-token context can need roughly 40 GB just for that memory. Denser storage lets the same hardware hold far longer documents, codebases and conversations.
Each new word a model writes means reading every weight from memory again, so generation speed is mostly limited by how fast data moves. Each stit sent is one of sixteen states rather than one of two, so every weight takes a quarter as many transfers to move.
Data centers are limited less by how much they can calculate than by how much power they can draw and how much heat they can remove. In modern chips, fetching a number from memory can use hundreds of times more energy than the arithmetic done on it. Most of the electricity goes into moving data around.
M16 attacks that cost directly. Fewer units per value means fewer units to charge, read and carry across a wire. That compounds up the whole stack: fewer chips per model, fewer servers per workload, less cooling per server.
Serve the same models from fewer racks, or serve more users from the racks you already have, without building a new facility.
Less data movement means less power drawn and less heat to remove. Cooling is a large share of a facility’s bill, and it scales with every watt saved.
New AI facilities are now limited by how much power the local grid can supply. Doing more work per watt stretches every megawatt already connected.
When a model fits on fewer accelerators, each response costs less to serve. That makes AI cheaper for everyone downstream.
Ray tracing follows paths of light as they bounce through a scene. Each ray asks the same question millions of times per frame: what does this ray hit? Answering it means searching a tree of the scene’s geometry stored in memory, and the rays scatter in every direction, so the search jumps all over that memory. Ray tracing is held back as much by memory as by math.
Render distance hits the same wall. Everything you can see, every mesh, texture and shadow, has to sit in the graphics card’s memory or stream in fast enough to avoid pop-in. Distant scenery gets cut or blurred because there is no room left for it.
Denser storage keeps more of the scene’s geometry tree close to the cores, so rays find what they hit with fewer slow trips to memory. That means more rays per pixel, more bounces and cleaner lighting at the same frame rate.
When every value needs a quarter as many units, the same memory holds far more of the world at full detail. Mountains, cities and forests can stay sharp to the horizon instead of popping in.
Higher-resolution textures fit in the same memory, and assets stream from storage faster when each value takes fewer transfers to move.
Upscaling, frame generation and ray-tracing denoisers are all small neural networks. They run on matrix multiplication, the exact workload M16 is built for.
Computational fluid dynamics (CFD) splits air or water into a grid of tiny cells and solves for pressure, velocity and temperature in each one, step after step. It is how aircraft wings, turbines, engines, heart valves and race cars are designed before anything is built.
When each pressure and velocity value needs a quarter as many units, a mesh that once needed a cluster can run on a single node, and a cluster can resolve turbulence it previously had to approximate.
The core of most physics solvers is huge, mostly-empty matrices multiplied again and again. That work is limited by memory speed, which is exactly where moving fewer units pays off.
When each run finishes sooner, engineers test more shapes per day. Better wings, quieter fans and more efficient engines come from more iterations, not just bigger ones.
Structural analysis, electromagnetics, molecular dynamics and plasma physics share the same grids and the same matrix math, so the same gains carry over.
Digital audio is a stream of samples, often 96,000 per second per channel at 24-bit depth. Almost everything done to those samples, including EQ, compression, convolution reverb and amp simulation, is multiply-and-add: the same operation at the heart of AI.
In a recording session, all of it has to happen in the few milliseconds between a musician playing and hearing themselves back. When the computer can’t keep up, engineers raise the buffer size, which adds delay, or freeze tracks so they can no longer be adjusted.
More multiply-and-adds per cycle lets sessions run at smaller buffer sizes, so performers hear themselves with effects and no noticeable delay.
Hundreds of tracks, each with a full chain of plugins, without freezing, bouncing or rationing effects to save processing power.
Convolution reverb, room modeling and immersive formats multiply every sample by thousands of stored values. Denser, faster math makes these practical everywhere, not only on the biggest machines.
Stem separation, noise removal and voice restoration are neural networks. On M16 they can run in real time during a session instead of as a slow offline render.
A single uncompressed 8K frame with full 10-bit color is about 124 MB. At 24 frames per second, that is roughly 3 GB of data every second, before any effects. Editors work around this with low-resolution proxy files, long renders and waiting on the progress bar.
Video codecs, color grading and effects are math applied to every pixel. Codecs are built on block transforms, color grading is matrix math on every pixel, and modern tools like masking and upscaling are neural networks.
7,680 × 4,320 pixels × 3 colors × 10 bits ≈ 124 MB per frame
124 MB × 24 frames ≈ 3 GB every secondScrub through full-resolution, high-bit-depth footage with grades and effects applied, without generating proxies first.
Encoding and rendering are throughput problems. Moving and multiplying more information per cycle shortens the wait between finishing an edit and delivering it.
Object masking, rotoscoping, frame interpolation, upscaling and noise reduction are all neural networks, the workload M16 was designed around.
More frames cached in the same memory means smoother playback and more room for layered, multi-camera edits.
The applications we have discussed are single examples that are hit daily by enterprises and consumers alike. However, there is a problem that no matter who you are, it will impact you in some way... price.
Even multi-billion dollar companies are struggling to source hardware to keep up with timelines and budget for compute. Binary hardware that is designed to tackle modern day applications is expensive and some is completely inaccessible to the average consumer. Multistate hardware is designed to handle these complex tasks with less energy, less hardware, and less headache.
Price matters to everyone:
·Enterprises can report less quarterly spend on compute and more profit to shareholders.
·Research groups can start new projects with less funding and more confidence in their computational resources.
·Individuals can run larger models locally, maximize their gaming experience, and just get more out of their personal computersThese are solutions we are working towards and we are excited to see the impact of multistate computing!
Gressus is young and small, we are currently prototyping our first multistate hardware but, this is costing us essential developmental runway.
We encourage you to reach out to us about anything. If you are a researcher, engineer, enthusiast, investor, or skeptic, we would love to hear from you at [email protected]
We want to grow a community of people who are interested in multistate computing and a future where technology benefits everyone. Following us on socials, spreading the word, and even just a quick message to keep it up help us in more ways than you know!
If a field runs on large grids of numbers being multiplied together, it is a strong candidate for multi-state compute.
See it for yourself. The Matrix Lab steps through matrix multiplication on a systolic array and counts the digits binary and M16 each have to process.