One encrypted drive. Every machine. Everyone you trust.

An encrypted shared drive

One drive that all your machines share, stored on disks you own.

• Files are encrypted on disk with AES-256-GCM. The key is wrapped separately for each of your machines.
• Every device also gets a personal folder that only that device can open.
• Sync keeps one folder identical on every machine, with a trash that holds deleted files for a while before they go.
• Backup sends the drive to your own cloud storage account, encrypted before it leaves. A restore works on a machine that has never seen it.
• When you set up the drive you write down a 12-word recovery phrase. With it, a new machine gets the shared drive back.

A device's personal folder can't be recovered by anyone, including you, if that device is lost. That is the price of a key nobody else holds, and FrameBuff tells you so plainly.

Your machines, from anywhere

Pair your computers once. After that they find each other, at home or across the internet.

• Pairing is a short code, or a QR code your phone scans. A machine you haven't approved gets nothing.
• The Network page shows every machine, how it is connected and what it is doing.
• The terminal manager lists everything FrameBuff started on every machine: shells, installs, jobs. Open any of them from one place.
• Share one mouse and keyboard across the screens on your desk.
• Android phones join through Termux and run the same program as your desktop.

Lend your GPU

The card in your desktop sits idle most of the day. Let your family use it.

• Family members send render jobs to your card while you're away.
• When you come back, FrameBuff notices: your own job, or the card getting busy with your game or app. Their work pauses and the card is yours again, typically within half a second.
• Their jobs continue when you're done.
• Each job is metered by the time it actually spent on the card, so everyone can see who used how much.
• The people borrowing see that the card is busy, never what you're doing on it.

Local models and agents

AI that runs on your hardware and works on your terms.

• Run language and image models on your own machines. What you type stays on them.
• Start AI agents from the Agents page. They work in containment, inside limits you set.
• Anything that would post, spend money or delete waits on an approval card for you.
• Every action an agent takes shows up as a card you can read afterwards.

Render while you sleep

Queue it at dinner. Watch it at breakfast.

• Describe a video or an image, pick a length, and choose to render now or tonight.
• The renderer is ComfyUI with LTX-Video, running on your own GPU.
• The overnight butler works through the queue in the hours nobody uses the card, and still steps aside if somebody sits down.
• Results land in your drive. Nothing is uploaded anywhere.

Family and guests

Your household gets its own shared space. Guests get only what you hand them.

• Invite family members' machines into a family group with its own encrypted space.
• Choose how sharing works: you pick a folder for each person, or they ask and you approve.
• Guests scan a QR code on the TV and join for the evening. FrameBuff forgets them when the evening ends.
• The family space has shared to-dos, reminders and birthdays.
• Every request to join or share waits for your answer. A request that runs out its countdown is a no. Silence is never a yes.
• Removing someone changes the family key, so they lose access to what comes after.

Couch, party, game night

The living-room TV is just another machine in your fleet.

• Send a playlist, a film or a game to the TV from whatever device is in your hand.
• Couch mode splits one TV between up to four people, each with their own corner of the screen.
• Game night has games built in, such as a quiz. Players join from their phones with a code shown on the TV.

Chat, inbox and notes

The small things, kept on your machines.

• Messages between your machines keep their history. Read one on your laptop and it's read on your phone.
• An inbox collects what needs your attention: approvals, requests, finished jobs.
• Notes and a calendar live next to them, in the same drive.
• The command chat lets you run any FrameBuff tool by typing. It follows rules you can read, with no AI in between.

Modules and an app builder

Everything in FrameBuff is a module, and you can write your own.

• A module brings its own page, tools, settings and storage. It slots in without changing FrameBuff itself.
• Wrap any command-line tool from GitHub or Hugging Face with a single framebuff.json, and it becomes a FrameBuff tool.
• Tools chain into pipelines: the output of one step feeds the next, and jobs wait in a queue instead of failing when a machine is busy.
• New modules wait for your approval before they install.

An MCP server built in

Your AI client can use your fleet.

• Run framebuff mcp and every FrameBuff tool appears as an MCP tool.
• The same tools the web page and the command line use. One list, three ways in.

A community library

Share what you build, and install what others built.

• Try any app in a sandbox first, sealed off from your files.
• Each app lists what it wants before you install it: which machine, which folder, whether it may use the network.
• The same limits stay on after you install.

The library is planned, not built yet.