BETA

FrameBuff docs

How FrameBuff works, one topic per page. Start with what FrameBuff is, then read the parts you plan to use.

Beta

FrameBuff is in beta and there is no download yet. These pages describe how it works today, and details can change before the beta opens. Join the waitlist to hear when it does.

Getting started

The ideas everything else uses

What FrameBuff is

One program on every machine you own, one encrypted drive, and modules for the rest. Start here.

Pairing machines

Join a machine to your fleet with a code or a QR. Approving it also hands it the keys to your drive.

Data & machines

Your files and computers, in one place

Sync and backup

One folder kept the same on every machine, a drop folder for quick handoffs, and encrypted backup to your own cloud account.

Shared mouse and keyboard

Slide your pointer off one screen onto the next machine. Off by default, always visible, two kill switches.

AI & GPU

Models, agents and your graphics card

Agents and approvals

Agents work in one folder, inside containment, step by step. Anything that posts, spends or deletes waits for your yes.

Lend your GPU

Lend your card to family while you're away. It pauses when you sit down, and both of you see the same usage.

Home & family

Share it with the people you live with

Family

A family folder, calendar, birthdays, notes and to-dos, shared by every family machine. Phones can join too.

Guests and game night

Phones as controllers, guests let in by QR for one evening, and everything they had revoked when it ends.

Screens and the couch

Any browser becomes a display. Split the TV so four people each get their own tile, input and headset.

Builders

Make FrameBuff do more

Writing a module

Wrap any tool with one manifest file, framebuff.json. You approve it before anything runs.

The MCP server

Every FrameBuff tool is also an MCP tool. Connect the AI client you already use to your files, jobs and machines.