FACTORY ZERO

FZ-016 · SECURITY

Sealbin

Sealed file and secret handoffs between AI coding agents.

In development VALIDATION FZ stackSealed sharingOpen source
Visit sealb.in Launched: NOT YET
Status
In development
Pipeline stage
VALIDATION
Sector
SECURITY
Autonomy target
LEVEL 4 · SELF-OPTIMIZING
Built with
3 live · 3 planned

The problem

Sharing files and secrets with another agent means pasting them into chats where they stay forever.

What it does

sealb.in is designed to encrypt files and context on the sender’s machine, then give one link that is deleted when opened.

How it works

  1. /seal ./context.tar in Claude Code, Codex or any agent with a shell
  2. The key stays in the link’s #fragment; the server only holds ciphertext
  3. /open puts the files on disk, burns the link, and leaves no copies behind

Open source under Apache-2.0; free to start, then priced per agent, not per seal.

Stop leaving tokens in chat history and pasting megabytes of context into prompts.

TodayThe site is live and early access is a waitlist. The CLI, MCP server, skill and hosted service are being built.

The film

The sealed handoff between agents.

Aims

Autonomous operation
The service runs itself: sealing, one-time opens, expiry and deletion are plain state in the hosted service with no human in the path. Signup, keys, billing and abuse handling are automated; a person steps in only for security reports and enterprise contracts.
Intelligence
No model ever sees a handoff: everything is end-to-end encrypted on the sender’s machine. Agents are the customers, not the operators. The skill teaches them when to seal and how to read a handoff index-first.
Growth
Developer-led: every sealed link one agent sends is a sealb.in link another agent opens. Growth is agents with a key, counted from the first seal, and paid plans when those agents run in CI or production.
The technical detail

The sealed handoff between AI agents. The sending agent encrypts files, context or secrets on its own machine and uploads only ciphertext; the key travels in the link’s #fragment and never reaches the server. The receiving agent opens the link once, the contents land on disk, and the ciphertext is deleted. Burn-after-read by default, or a TTL, with an optional password. A CLI, an MCP server with seal and open tools, an agent skill and a REST API; open source under Apache-2.0 with a hosted service. What exists today is the site and the early-access waitlist; the product is being built.

Related

From the same foundation.

All ventures