Skip to content
woven
CoreTandemHomePrivacyOn a MacShop
SupportSign in

The box

  • Woven Core
  • Woven Core+
  • Woven Core Pro
  • Compare
  • Tech specs
  • Reserve

What it does

  • Tandem
  • Home and TV
  • Privacy and the Gate
  • Run it on a Mac
  • For developers

Honestly

  • What is real
  • Founding Homes
  • Support
  • Privacy and legal

Woven

  • Press
  • Careers
  • Contact
woven

Woven © 2026

The box is not built. Prices, dates, specifications and performance figures on this site are engineering targets for a reference design, not shipping specifications, and the figures drawn on the phone and television screens are illustrations rather than measurements. What the software does today, and what it does not, is listed claim by claim.

This site sets no cookies and runs no analytics.

Privacy

Where your data goes, and doesn't.

This is the Privacy tab from the app. Four categories are pinned to Inside. Move the other two and watch the week change.

This week
99.6% inside
4 crossings · all approved by you
  • Voice & conversationsInside
  • Home control & automationsInside
  • Cameras & clipsInside
  • Files, photos, memoryInside
  • Deep research & big jobs
  • Video generation

Every crossing is recorded with what was sent and why. Voice, home and camera data never cross the Gate. The four pinned categories cannot be changed, even by you.

Reserve a CoreMeet Tandem

Four things never leave.

Your files, photos and memory are processed on the box today, and voice, home control and cameras will be when the box exists. These categories are pinned to Inside in the software, not in a settings page.

Everything else asks first.

A crossing is a card you approve. It names the task and exactly what will be sent. Approve once, or keep it inside and let Tandem do its best from what it already knows.

Every crossing is written down.

The front screen and the app keep a log: time, task, what left, who approved it. Tap any line for the full record. Nothing is summarised away.

One tap stops all of it.

Close the Gate from the screen, the app, or by voice. The box keeps working. Jobs that need the Outside wait or fail clearly. Nothing is silently queued.

How it is built

Two computers. One Gate.

Privacy here is not a setting. The Inside, where everything of yours lives, has no route to the internet. The Outside is your router, on its own processor. The Gate between them forwards only what you approve, and writes it down.

Inside
no internet

Has no path to the internet.

  • Your files and backups
  • Photos, indexed by what is in them
  • Cameras and their clips
  • Lights, locks, sensors, routines
  • Tandem and its memory
  • Woven on your TV
The Gate

Only what you approve crosses, and it is written down.

  • Crossings you approve, one at a time
  • Signed updates, verified before they cross
  • Your key, when you reach home from away
Outside
internet

Is your router.

  • Wi-Fi 7 for the whole house
  • 10 GbE to the internet
  • A guest network that sees nothing inside
  • Per-device rules and schedules

The Outside runs on its own network processor. The Inside has no route to it except the Gate. This is wiring, not a setting.

Anatomy of a crossing

What actually leaves the house.

A crossing is a task, not a transcript. Tandem builds the smallest package that can answer the question, strips names, identifiers and history, and shows you the package before it goes.

The answer comes back through Tandem. Any action it implies still passes the permission engine and is verified on the device.

  • Task text, written by Tandem, not your raw words
  • Minimal context: the fields the task needs and nothing else
  • No household names, files, photos, device names or history
  • Provider, model and time recorded in the receipt
How Tandem decides
ActivityInside · 21:42
Where your data went today
98% stayed inside · 1 crossing (deep research, approved by Alex)
21:40TandemAnswered Maya: “When is the dentist?” · from the household calendar
18:12CamerasPackage at the front door · clip saved inside
14:05BackupSam's laptop · 4.1 GB synced · 312 photos indexed
09:30CrossingDeep research: “compare heat pumps” · 1 task sent, no personal data
Crossings: ask me
Cameras: inside
Voice: inside
Close the Gate

Security

Built to the consumer IoT baseline, then past it.

Woven Core maps its controls to the NIST consumer IoT baseline and the 2026 manufacturer guidance. The model is never a security boundary. Four of the six below are built and tested today4; the hardware ones wait on the box5.

Encrypted at restAvailable now

The database, every file and the box's private keys, under a household key. On a Mac that key is in your login Keychain.

Signed updates, with rollbackAvailable now

A release is verified before anything in it is used, the previous one is kept, and it comes back on its own if the new one does not start.

No inbound portsAvailable now

Remote access is one outbound connection, and every frame through it is encrypted end to end under a key only your browser and your box hold.

One switch stops itAvailable now

Off closes the Gate, drops the connection and refuses everything until you switch it on. It survives a restart.

Secure element and attestationWith the box

Per-device identity in hardware, and storage that unlocks only for an attested compute module.

Locked debug, disclosure programmeEngineering target

Production debug ports disabled, audited service access, a published security contact and a support window.

How we talk about it

Inside first. Not “everything stays inside.”

We say
  • Inside first. A crossing when needed and permitted.
  • Here is exactly what is stored on your box, and what a Woven service would hold if one existed.
  • The share that stayed inside, counted by your own box and shown on your own screen.
  • A published security support period and end-of-life policy.
We do not say
  • “Fully private.”
  • “No cloud, ever.”
  • “Runs a 70B model” as if it were a permanent feature.
  • Anything a lawyer would not let us put on the box.

Every performance, privacy and security claim on this site has an owner, evidence and a review date. Prototype targets are labelled as targets.

Privacy you can glance at.

From the kitchen, on the front of the box.

ReservePrivacy policy

What stands behind this page

  1. 1Available 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.
  2. 2Available nowBuilt and tested. Receipts form a hash chain; changing or removing one breaks the chain, and the box checks it nightly and on demand.
  3. 3Available nowBuilt and tested. Off closes the Gate, drops the relay, stops every scheduled job and refuses every request but the switch itself. It survives a restart.
  4. 4Available nowBuilt and tested. The database, every stored file and the box's private keys are encrypted under a household key. On a Mac that key lives in the login Keychain; on the box it will live in a secure element. A copied drive is unreadable without it.
  5. 5With the boxNot built. Encryption at rest is real and running; the secure element, the attestation and the module that would hold them are hardware that does not exist yet.
  6. 6Available nowBuilt and tested. The box holds one outbound connection to a relay; a browser you paired at home encrypts every request end to end. The relay carries ciphertext and keeps nothing. The relay service is not deployed yet, so this needs one you run.
  7. 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.