It is specified, then built for you
Every Garnet is specified for the work it has to do and built to fit it, which takes weeks rather than minutes. Come to us when your timeline is weeks.
Before you ask
Where Garnet stops
You were going to go looking for this page. It is quicker if it exists, and it costs us nothing to be the ones who wrote it.
The airgap is yours to switch on
The airgap is a capability built into every machine and switched on at your discretion. How the machine is then maintained and updated is settled with you: a visit, a network window you open on your own schedule, or media sent to you by post. A standing connection is one option among several. Under every one of them your material stays with you for processing. We would rather set the options out than let “airgapped” carry more than the word can.
It is early, and so is everyone else's
Parts of the system are in daily use. Parts are still being built. The table below says which is which for every capability of a Garnet build — published here rather than offered on request, because we would rather be exact and lose the sale.
It is an instrument, and you are the one using it
It reads, drafts, summarises, searches and organises, extremely fast, on material that otherwise stays in a locked drawer. The judgement stays with you, and we sell it as an instrument rather than as someone's replacement.
It is equipment and an engagement
This is equipment and an engagement rather than a seat licence. For teams whose material genuinely has to stay with them, that maths usually works. For everyone else it may well be the wrong shape, and a short conversation will establish which you are.
We keep our own internals in, as we will keep yours
Our infrastructure inventory, our service topology and our machine telemetry stay off this website, for the same reason we are asking you to trust us with yours. If you need that depth for due diligence, ask, and we will take you through it properly.
Which is which
What is in daily use, and what is still being built.
The card above says we will tell you which is which. Here it is, for every capability of a Garnet build, without waiting for you to ask.
| Capability | State | What that means |
|---|---|---|
| Chat, against models running on the machine | in daily use | The everyday case, and the one the rest is built on. |
| Your documents, read and searched, with citations | in daily use | Retrieval over your own material, on the machine in your building. |
| Image generation | in daily use | The generator runs on the reference machine and has produced several thousand images; every photograph on this website is its output; the pictures of the machine are rendered from its design file. We do not claim it runs every day. |
| Video generation | in daily use | Short loops, from a prompt or from a still. The loops on this site are its output. As with images, that is a statement about what it has made, not about how often it runs. |
| Speech — reading aloud | in daily use | Text to speech, locally. The audio sample on /app/ is the output of this. |
| Transcription — speech to text | in daily use | Proven by round trip: a sentence spoken by the speech model was transcribed back verbatim in about a second, on this hardware, with nothing leaving it. The model loads on first use rather than at boot, which is why we briefly had this listed as unbuilt — an unloaded model and an absent one look identical from outside. |
| 3D objects and meshes | in daily use | Twelve distinct meshes ship on this website, twenty-two files once the lighter mobile versions are counted. Eight of them furnished the three rooms of the walkthrough retired on 2026-10-23; the rest are on the facility pages. Each was generated from a single image and is delivered as GLB. As with images, that is a statement about what it has made, not about how often it runs. |
| Music | in daily use | Three sub-genres were generated and one seventy-five-second arrangement was chosen for this site. Scored here rather than licensed. Same caveat as the rest: what it has made, not how often it runs. |
| A coding agent that edits your codebase | in daily use | A workbench on the machine that reads and writes your real files. Every command it runs is checked a part at a time rather than by its first word, anything it cannot parse is refused rather than allowed, and it stops to ask before a write even where its own rules would permit one. What it allowed and what it refused are both recorded, with the rule that decided. It is the newest thing in this table by a wide margin, and two faults were found and fixed in it on the day it shipped. |
| Standing agents that act to a schedule | in build | The approvals surface is real and in use. Acting without a person in the loop is not. |
| Garnet Mesh — several machines answering as one | in build | The services are written and installed on the reference machine and have never been started in service. Single-machine Garnet is what works today. Do not buy a second machine for this yet. |
| Garnet Law | in build | Said on its own page too. We are not selling it. |
Measured 30 September 2026 against the reference machine — running services, loaded models and what each one has actually produced — not against a roadmap. Three rows were corrected the same day they were published, after checking the services themselves rather than the descriptions they advertise: transcription turned out not to be loaded, and two rows claimed a daily cadence nobody had measured. It is re-checked by hand, and the date above is the date to judge it on. If something you need is not on this list, ask, and you will get the same two-state answer for it.
The other half
And what happens to work that goes somewhere else.
Everything above is what this does not do. The other half of the same question is walked rather than listed: the passage turns at the vault door and follows a chain of custody out into the dark. It names no company and alleges nothing — the instant work leaves a machine you control, a copy exists on one you do not, and that is arithmetic rather than an accusation. It ends on five questions you can put to any vendor, this one included.
If that hasn't put you off
Then the rest is a conversation.
Tell us what the material is and who is not allowed to see it. That is usually enough to know within one call whether this is worth either of our time.