Watch a Garnet get built.

Skip the demo, read what it is

The architect

Pick one of the briefs below. You’ll get the build plan and the rendered concept for that job — both produced by models running on our own machines, neither one bought from anybody else.

The plan was written by a language model running on a machine we own, reached over a local proxy that has no route to any outside provider. The image was rendered by an image model on that same machine. Both were produced once and are replayed here, and we would rather say so than dress a cached file up as something happening in the moment.

That is a deliberate choice, not a shortcut. Putting a public button in front of a private model means handing an anonymous visitor an open-ended claim on it. The whole proposition we sell is that your model answers to you and to nobody else — running ours as a free service for the internet would be a strange way to demonstrate it.

What the demo is honestly evidence of: these models run on ordinary hardware we control, with no account, no API key and no request leaving the building — which is the same arrangement we install for you, on your hardware, in your building.

A five-step sketch is a shape, not a system. A commissioned build is where the specifics live, and they are mostly the unglamorous ones:

• Your material, indexed. The demo has nothing to read. A build starts by taking your actual documents, mail, drawings or photographs and making them retrievable on your own machine — which is most of the work and all of the value.
• The hardware call. Which machine, and how much of it. That answer comes from your material and your people, not from a preset. Joining several of your existing machines into one system with Garnet Mesh is a later question: Mesh is in build — the services are written and installed on the reference machine and have never been started in service — so a build today is single-machine Garnet, and you should not buy a second machine for this yet.
• The sealed posture. Air-gapped where it should be, no telemetry, nothing phoning home, no standing access for us once it is yours.
• Handover. People who are not engineers have to be able to use it on a Tuesday without calling anyone. That is a design problem, and it is the one most private-AI projects lose on.

Design my Garnet →

Rather read than click? Walk the whole build in plain language →