What FrameBuff is
One program on every machine you own, one encrypted drive, and modules for the rest. Start here.
How FrameBuff works, one topic per page. Start with what FrameBuff is, then read the parts you plan to use.
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.
One program on every machine you own, one encrypted drive, and modules for the rest. Start here.
How FrameBuff runs anything: tools in a pipeline, each run a job you can watch, on a schedule or from one typed line.
Join a machine to your fleet with a code or a QR. Approving it also hands it the keys to your drive.
Files encrypted on your own disks, a personal folder per machine, and a 12-word phrase that brings it all back.
One folder kept the same on every machine, a drop folder for quick handoffs, and encrypted backup to your own cloud account.
Slide your pointer off one screen onto the next machine. Off by default, always visible, two kill switches.
Install models after a review, run them on your own CPU or GPU, and queue renders for tonight.
Agents work in one folder, inside containment, step by step. Anything that posts, spends or deletes waits for your yes.
Lend your card to family while you're away. It pauses when you sit down, and both of you see the same usage.
A family folder, calendar, birthdays, notes and to-dos, shared by every family machine. Phones can join too.
Phones as controllers, guests let in by QR for one evening, and everything they had revoked when it ends.
Any browser becomes a display. Split the TV so four people each get their own tile, input and headset.
Wrap any tool with one manifest file, framebuff.json. You approve it before anything runs.
Every FrameBuff tool is also an MCP tool. Connect the AI client you already use to your files, jobs and machines.