A personal AI system

Your AI team.
On your machine.

Not a chat window and not a browser tab. A system with a voice, a memory that compounds, and a team of specialists that do real work — running on hardware sitting in your building. Your files never leave it.

Every other AI assistant

Your work, your files and your clients — sitting on somebody else's computer, under somebody else's terms of service.

This one

The same team, the same memory, the same voice — on a machine you own, in a room you can walk into.

What it is

A system, not a subscription to a chat box.

You talk to it. It routes the job to whichever specialist should have it, and they get on with it while you do something else.

01

It speaks and it listens

One continuous conversation that survives restarts, knows your voice from anyone else's, and does not make you start again.

02

It remembers

Every correction and every decision is written down and read back at the start of every session. It gets sharper; it does not reset.

03

It does the work

Not summaries of the work. Sites deployed, mail triaged, books checked, reports written, things watched overnight.

04

It refuses things

Every specialist has something it will not do, and it says so out loud. That is the part that makes the rest safe to leave running.

What's inside

The parts you would otherwise spend a year building.

01

A team of specialists

Configured for your work, not generic. One reviews. One verifies. One watches the inbox. One tests with the wrong password on purpose.

02

A board you can see

What is running, what is waiting on you, what finished overnight. One screen, answerable at a glance.

03

Local models

The routine work runs on your own graphics card. Nothing leaves the building unless there is a reason, and you can see when it does.

04

Guardrails that bite

Real refusals at the tool layer, not instructions in a prompt. The system stops itself doing the dangerous thing.

Who it's for

People who cannot put client files in a chat window.

If your work is confidential by obligation rather than by preference, every cloud assistant is a conversation with your compliance officer waiting to happen. This one never starts that conversation.

Law firmsPrivileged material that cannot sit on a third party's servers, and a duty to know exactly where it does sit.
AccountantsClient financials, and a professional obligation that does not care how good the vendor's security page looks.
Medical and dental practicesPatient records, and rules with teeth about where they are allowed to travel.
Anyone who has read a terms of serviceAnd noticed what it says about how your data may be used.

What it costs

You buy it once. You keep it.

There is no seat, no per-user, and no usage meter. It runs on your hardware, so what it costs to run is your electricity.

Installed

One fee

Quoted after one conversation

Set up on your hardware. Specialists built for your work. Your tools and files connected. A day of training. Yours — it keeps working whatever happens to us.

Looked after

Monthly

Optional, cancel any time

Updates and new capabilities. New specialists as the work changes. Someone to call when it breaks. Watched, so you do not have to.

The build is quoted after the first conversation, not before. What it takes depends on what is being connected, and a number invented before looking is a guess with a price tag on it. You hear it once and it does not move.