Earth at night from high orbit: dark oceans, faint city glow, thin cold-blue submarine cable routes converging on one bright coastal city at the centre.
Earth at night from high orbit: dark oceans, faint city glow, thin cold-blue submarine cable routes converging on one bright coastal city at the centre.

01 — the road

The Cable Map

Sent away, this is the road. Several of the places it goes are excellent, and a great deal of good work goes down it. But a cable map does not show who is standing where it lands.

The count, from here: unknown.

A floodlit data-centre campus from a few hundred metres up, long halls in cold white light, roads between them.

02 — where it lands

The Halls

Where it lands there are two copies and you hold one. The other is readable by whoever can, not whoever would: staff under policy, systems under contract, anything a lawful order reaches. Every one of them contracted and competently run.

The count starts here, and it is never one.

An ordinary street at dusk and one building's front door, warm light in a window.

03 — the other choice

Your Street

Or it never leaves. The other choice is a building you already have the keys to.

The count, from here: whoever can get through that door.

A corridor on an office floor, one door at its end, lit from inside.

04 — the door

The Floor

A door on a floor you control. There is one way in that is ours while the system is being supported — the management path — and it can be removed. After that we reach it only when you let us: a visit, a network window you open on your own schedule, or media by post.

The count: whoever you let through.

A private AI under your own roof

A private AI that never leaves your building.

A private AI system installed in your building, on one machine on a floor you control. Chat, documents, generation and code happen there, and nothing it does needs the outside.

Where it runs
On one machine, in your building, on a floor you control. What it does
What leaves
Nothing. Cut the network and it carries on answering. What it doesn't do
Where it stands
We are early. The reference machine is the one that made this page. Trust

The limits page says, per capability and with a date, what is in daily use and what is still being built.

Garnet Workstation

One program, on one machine, and it does the work.

Garnet Workstation is a desktop application that opens on the machine. Everything below is a surface inside it, sharing the same models, documents and approvals.

The machine with one side panel removed: an aluminium frame, a tower cooler over the board, a three-fan graphics card below it with garnet hubs, the power supply at the floor and sleeved cables along the near side.
One machine, one program. Rendered from the machine's own design file.
Talk
Chat against models on your machine. Nothing is metered and nothing is sent anywhere to be answered.
in daily use
Read
Documents ingested, chunked, embedded and searched, with their sources shown.
in daily use
Make
Images, video, 3D, speech and music, on the same card that answers you.
in daily use
Build
A coding agent that reads the repository, proposes a change, and stops to ask before it writes.
in daily use
Ask first
Anything outward or irreversible — publishing, deploying, spending, mail — queues for a person. When you approve, the request is frozen by a digest checked at that moment and written to an audit trail.The approvals surface is real and in use. Acting without a person in the loop is not.
in build · scheduled action
Every object here was produced as a mesh by this system. Walk the three rooms →
The Garnet autonomy gate's status panel, disarmed: switches for Publish, Deploy, Spend and Outreach all off, with the master switch off beneath them.
The gate's status screen as it ships; arming lives one tab over.

Now cut the cable.

Everything above keeps working.

Chat, your documents, generation and code never reached out, so taking the network away changes nothing about them. The airgap is a firewall rule dropping outbound traffic at the machine itself — not a preference inside an application. Garnet Workstation reads the state and shows it for as long as it is on; anything that would have needed the outside says so plainly.

Goes on

  • chat
  • documents
  • generation
  • code
  • approvals

Stops

  • web search
  • fetching a page
  • pulling models or updates

You turn the airgap off to do them, deliberately, and turn it back on.

It is not airgapped unless you choose that.

It keeps one exception: the management path the system is reached on for support. That path can be removed.

Garnet Workstation with its airgap banner on. The bar reads: AIRGAP ON — outward surfaces degraded (queued/cached/needs-egress); local $0 core unaffected. Source: marker.
The banner, on the reference machine, with the airgap engaged.
Close on the graphics card inside the machine: three fans with garnet hubs under an aluminium fin stack, the frame and a panel edge in front.
The card that answers you. Nothing it does reaches past this case.

The machine

One machine. It is installed, and it stays.

A single workstation-class machine with a high-end GPU, specified to the work you actually do and built before it ships. 59.1 litres in a hexagonal prism, 420 millimetres across corners and 515.8 tall; twelve facets on a frame; six fans, three at the floor and three at the roof; one card. No tenancy, no region to choose, no per-token bill.

We don't publish part lists — ours or yours. The specification is part of the conversation about what you need it to handle.

The Garnet machine rendered from its own design file: a tall narrow case in charcoal printed panels on an aluminium frame, lit garnet from the left and gold from behind.

Rendered from the machine's own design file, in the materials it is designed in. The design is still being completed and the first has not been printed — read it as the design, not as a photograph of a product. Scroll it apart on the walk →

Before you ask

Three things are still in build, and we say so.

Standing agents to a schedule
The approvals surface is real and in use. Acting without a person in the loop is not.
in build
Garnet Mesh
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.
in build
Garnet Law
The same machine, for a law firm — matters, privileged documents, discovery, with citations shown and privilege enforced. It is not finished and we are not selling it. There are no deployments and no customers, and the screens we can show use synthetic matters.What Garnet Law is →
in build

It is not something you download

There is no public build, no trial, and no installer waiting behind an email form. A Garnet is specified for the work it has to do and built to fit it, which takes weeks rather than minutes. If you need something running this afternoon, this is not that. The catalogue at Products is not that — nothing there is a Garnet.

Measured 30 September 2026 against the reference machine. The full table, every capability →

Start

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. A personal reply from the person who would design it.

Walk the three rooms and the other way out → · the pricing, in full → · this page in prose →

Pictures on this page: the machine is rendered from its own design file; the forge is a render of meshes this system generated; the two application screens are screenshots of Garnet Workstation on the reference machine.