An inference engine built from scratch for the Mac. Custom kernels optimised for Apple silicon push speed to the limit. Our own quantisation runs models light while keeping accuracy close to the original. Inference happens on your Mac, and conversations are never sent to the cloud.
Many local AI apps run models through a Python runtime or a local server. Q.E.L.V.A.R.I. is a native engine written only for the Mac, and it runs models directly inside R.E.V.I.S.
Built for Apple silicon
Built on MLX, with custom Metal kernels that tighten the computation. It turns the design of Apple silicon, where the CPU and GPU share the same memory, directly into speed.
Light and faithful
Our own quantisation (Q4T, Q3T) makes models smaller and lighter while keeping accuracy close to the original model's output.※1
There's no network traffic for inference. Your conversations, your files, and the context the model has read all stay on your Mac.
Speculative Decoding
Draft ahead. Check in one pass.
With MTP (Multi-Token Prediction), a small draft model writes a few words ahead, and the main model checks them all at once. Only words the main model has confirmed are kept. The answer moves forward in fewer steps than writing one word at a time.
When the draft misses, the main model rewrites it. The speedup varies with the model, the context length, and how many run at once.
DECODE / MTP
DRAFT
VERIFY
OUTPUT
I've put the decisions and owners from the meeting minutes into a table.
Context Memory
Continue without rereading.
The context the model has finished reading (the KV cache) is encrypted and kept on your Mac's SSD. When you resume a conversation, it doesn't have to read everything again from the start.
Encrypted, kept local
Saved context is encrypted, and the next turn of the conversation picks up from there.
Several at once
Conversation replies and generation for background tasks can run side by side on a single Mac.
Semantic search, in the same place
The same engine also runs the embedding models that turn the meaning of words into vectors. It's the part that supports K.E.C.H.I. search.
Measured
By the numbers.
It doesn't re-read everything on every turn of a conversation. It keeps the context it has finished reading, reads only what has just been added—your message or a tool's output—and writes the answer. We therefore measured the speed of reading new input and the speed of writing the answer across five Macs, at different lengths of context already read. Every one of these speeds was achieved without sacrificing computational precision.※2
How Macs compare.
We compared them using Qwen3.6 35B and Gemma 4 26B, which run on every Mac. These are the speeds when the context already read is 16K (a typical length in everyday use).
Qwen3.6 35BGemma 4 26B
Prefill (speed of reading new input)tok/s
M5 Ultra1,4431,505
M5 Max1,2381,284
M4 Max664628
M5 Pro783815
M4 Pro390372
Decode (speed of writing the answer)tok/s
M5 Ultra239241
M5 Max196170
M4 Max172144
M5 Pro123106
M4 Pro10386
A guide to writing speed.
This plays back the speed of writing an answer (decode) in real time. It shows the speed for Qwen3.6 35B with a 16K context. Choose a Mac and press Play.
0.0 s
People read silently at about 4 words a second.
0.784words/s259
Expense claims go through three stages: submission, approval, and payment.
First is submission. Within one month of the expense, enter the date, amount, and purpose into the claim form, attach a photo of the receipt, and send it off. For public transport, you do not need a receipt as long as you fill in the route taken and the fare. However, receipts are required for taxis and the Shinkansen.
Next is approval. Once your claim arrives, your line manager will check the details and approve it. Claims over 50,000 yen also require approval from the head of department. If any details are missing, the claim will be sent back, so it is best to state the purpose specifically—including who it was with and what it was for.
Finally, payment. After the finance team has checked your claim, anything approved by the 20th of the month is paid into your account with your salary on the 25th. Claims approved after the 20th are paid the following month.
If you are unsure about anything, please check 'How Expense Claims Work' on the company portal first. If you still have questions, contact the finance helpdesk and they will usually get back to you the same day.
Context length and speed.
As the context the model has already read grows longer, both reading speed and writing speed come down. The horizontal axis shows context length (1K to 128K tokens), and the vertical axis shows speed. Choose a Mac.
Qwen3.6 35BOrnith 1.5 35BGemma 4 26BQwen3.8 27B
Prefill (speed of reading new input)tok/sDecode (speed of writing the answer)tok/s
Prefill (speed of reading new input)tok/sDecode (speed of writing the answer)tok/s
Prefill (speed of reading new input)tok/sDecode (speed of writing the answer)tok/s
Prefill (speed of reading new input)tok/sDecode (speed of writing the answer)tok/s
Prefill (speed of reading new input)tok/sDecode (speed of writing the answer)tok/s
※2 Measured with the same settings as the R.E.V.I.S. release build. Speeds vary depending on the model, the Mac, and the input. tok/s is the number of tokens (word units) processed per second.
Models
Models you can run.
Only models confirmed to work with Q.E.L.V.A.R.I. can be loaded. Support for new models will be added over time.
Model
Size (Q4T / Q3T)
Gemma 4 26B MoE
15.6 GB / 12.7 GB
Qwen3.6 35B MoE
19.4 GB / 15.6 GB
Ornith 1.5 35B MoE
19.4 GB / 15.6 GB
Qwen3.8 27B
20.1 GB / 17.6 GB
Sizes include the MTP draft model (GiB). Models can be loaded within roughly your installed memory minus 7GB. As a guide, a Mac with 24GB of memory runs the Q3T of Gemma 4, Qwen3.6 and Ornith 1.5, and 32GB or more runs the Q4T of every model.
※1 Accuracy refers to how faithfully the original model's output is reproduced; it does not mean performance beyond the original model. Speed varies with the model, the Mac and the input.
※ The animations on this page are illustrations and differ from the actual product screens.