TandemWith the box

Ask. It stays home.

A household assistant that runs inside. It knows your calendar, files, photos and home, answers in under a second², and asks before anything crosses the Gate. Try it: give the approval yourself.

AskInside

…

Reserve a Core See what leaves

The demonstration above is scripted. On a Core today the assistant answers by rules over what the box holds and says so on the screen; the model that reads a sentence, and the voice that speaks to it, need the box.¹³

Context

It knows the household, not the internet.

Tandem reads what is on the box: the shared calendar, each person's files and photos, device state, routines, and the memories you have chosen to keep. It does not need a search engine to tell you when the dentist is.

Every person has their own namespace. Maya's notes are not Sam's context, and a guest sees only the lights they were given.

Per-person memory you can read, edit and delete
Household, private, security and guest namespaces
No implicit sharing between people or between work and home
Provenance on every answer: which calendar, which file

Calendar

Shared · 3 people

Files

1.2 TB · 3 devices

Photos

48,210 · indexed

Home

24 devices · 6 rooms

Memory

Per person · editable

Cameras

4 live · inside

How an action happensAvailable now

The model suggests. The policy decides. The device confirms.

Tandem is an orchestrator, not a single model with a key to the house. Every request that could change something passes through the same nine steps. This part is built and running today: the permission engine, the approvals bound to the exact parameters, and the receipt at the end.⁵

01Ask
Text or voice, from any room.
02Understand
Typed intent, with a confidence score.
03Retrieve
Only the context this person is allowed to see.
04Plan
Steps, tools, and any irreversible side effects, named.
05Check
A deterministic policy engine decides, not the model.
06Approve
Sensitive steps become a card you can read.
07Execute
Idempotent, bounded retries, timeouts.
08Verify
Read the device back. A 200 is not a locked door.
09Receipt
Who, what, where it ran, what it sent.

PermissionsAvailable now

Eight classes of action. You set the line.

Built and running. The engine is a pure function of the request: same request, same answer, every time, and five thousand random requests are checked against these rules on every change.⁴

Class	For example	Default
A	Read a temperature	Automatic
B	Lights, media	Automatic
C	Thermostat within bounds	Automatic within bounds
D	Unlock a door, disarm	Presence or approval
E	Place an order	Approval above your limit
F	Move money	Not supported
G	Robot uses a dangerous tool	Not supported
H	Keys, ownership, factory reset	Strong auth

Classes F and G are not supported in the first release by design. Money moves through your bank, and robots keep their own safety controls.

AgentsWith the box

Where your agents are allowed to run.

Personal agents are arriving with shell access, browser control and your inbox. On a laptop they run as you. On Woven they run as themselves: sandboxed, with their own identity, scoped credentials, and a receipt for everything they do.

Install an agent the way you install an app. Give it the calendar and not the camera. Revoke it in one tap and the tokens die with it.

OpenClaw-compatible agent runtime, sandboxed per agent
Scoped, short-lived credentials issued by the box
Every action passes the same permission engine as Tandem
A discoverable endpoint on the LAN for robots and devices

Developers

TandemHousehold assistant

Calendar · Files · Home · Photos

active

GrocerReorders staples under $50

Shopping list · Approved merchants

active

SweepRobot vacuum planner

Rooms · Occupancy · Robot API

active

LedgerBills and budgets, read only

Financial namespace

paused

Inside and across the Gate

Most of the work never leaves. The rest asks.

Tandem chooses by data class first, then latency, capability and your setting. Keeping things inside is policy, not a cosmetic toggle.

Workload	Runs	Rule
Wake word, speech	Inside	No always-on audio leaves the house.
Home control	Inside	Works with the internet unplugged.
Files, photos, memory	Inside	Indexed and searched on the box.
Summaries, planning	Inside first	Crosses the Gate only if policy allows and you say so.
Deep research	Crosses the Gate, by permission	Minimal context, recorded.
Video generation	Crosses the Gate, by permission	Outside everyday use.

Planning target: more than sixty percent of ordinary supported requests complete without a crossing. Measured in the pilot, shown on your screen, never promised in marketing.

Tandem ships on every Core.

No subscription for the assistant inside. Ever.

Reserve Woven Core+

What stands behind this page

1With the boxNot built. Today the assistant is a rule engine over what the box already holds, and it says so on every screen: it can find a file by name, count your photos, switch a light and read the receipts. There is no language model on the box and no calendar yet. The 20B to 70B class models on the specification sheet need the box's memory.
2Engineering targetNot measured. There is no model on the box to measure. The figures on the rendered screens throughout this site are illustrations, not measurements.
3With the boxNot built. There is no microphone path, no wake word and no speech model in the software today.
4Available nowBuilt and tested. The Core has no network egress of its own: a separate Gate process is the only way out, it holds an allow list, it can be closed, and each crossing writes a receipt naming the host, what was sent and who approved it. On the box the Gate is also a hardware boundary; on a Mac it is a process boundary.
5Available nowBuilt and tested. Receipts form a hash chain; changing or removing one breaks the chain, and the box checks it nightly and on demand.
6With the boxNot built. There is no agent runtime. The permission engine, the receipts and the Gate that agents would run inside are built and tested; the sandbox is not. The dashboard's Agents page says so when it is connected.
7Engineering targetNot measured. The share of work that stays inside will be measured during the pilot and published. Any percentage shown on a screen here is drawn, not counted. Your own box counts the real figure and shows it on the Privacy page.

Every claim on this site is listed with what stands behind it on the what is real page.

It knows the household, not the internet.

Every person has their own namespace. Maya's notes are not Sam's context, and a guest sees only the lights they were given.

Per-person memory you can read, edit and delete

Household, private, security and guest namespaces

No implicit sharing between people or between work and home

Provenance on every answer: which calendar, which file

Class

For example

Default

Read a temperature

Automatic

Lights, media

Automatic

Thermostat within bounds

Automatic within bounds

Unlock a door, disarm

Presence or approval

Place an order

Approval above your limit

Move money

Not supported

Robot uses a dangerous tool

Not supported

Keys, ownership, factory reset

Strong auth

Where your agents are allowed to run.

Install an agent the way you install an app. Give it the calendar and not the camera. Revoke it in one tap and the tokens die with it.

OpenClaw-compatible agent runtime, sandboxed per agent

Scoped, short-lived credentials issued by the box

Every action passes the same permission engine as Tandem

A discoverable endpoint on the LAN for robots and devices

Developers

Workload

Runs

Rule

Wake word, speech

Inside

No always-on audio leaves the house.

Home control

Inside

Works with the internet unplugged.

Files, photos, memory

Inside

Indexed and searched on the box.

Summaries, planning

Inside first

Crosses the Gate only if policy allows and you say so.

Deep research

Crosses the Gate, by permission

Minimal context, recorded.

Video generation

Crosses the Gate, by permission

Outside everyday use.

What stands behind this page

1With the boxNot built. Today the assistant is a rule engine over what the box already holds, and it says so on every screen: it can find a file by name, count your photos, switch a light and read the receipts. There is no language model on the box and no calendar yet. The 20B to 70B class models on the specification sheet need the box's memory.

2Engineering targetNot measured. There is no model on the box to measure. The figures on the rendered screens throughout this site are illustrations, not measurements.

3With the boxNot built. There is no microphone path, no wake word and no speech model in the software today.

4Available nowBuilt and tested. The Core has no network egress of its own: a separate Gate process is the only way out, it holds an allow list, it can be closed, and each crossing writes a receipt naming the host, what was sent and who approved it. On the box the Gate is also a hardware boundary; on a Mac it is a process boundary.

5Available nowBuilt and tested. Receipts form a hash chain; changing or removing one breaks the chain, and the box checks it nightly and on demand.

6With the boxNot built. There is no agent runtime. The permission engine, the receipts and the Gate that agents would run inside are built and tested; the sandbox is not. The dashboard's Agents page says so when it is connected.

7Engineering targetNot measured. The share of work that stays inside will be measured during the pilot and published. Any percentage shown on a screen here is drawn, not counted. Your own box counts the real figure and shows it on the Privacy page.

Every claim on this site is listed with what stands behind it on the what is real page.