Silo

Your vault stays local.

Encrypted on your machine. Unlocked for one session. The browser only gets what you approve. Silo keeps credentials on your machine and makes every release of a secret an explicit action.

  • Local-first
  • Encrypted data
  • Explicit actions

Three objects,
kept separate.

The close-line field marks the point where access narrows. It is the same visual rule everywhere because it describes the same event everywhere.

A

The file is the place

A vault you can locate, move, back up, and inspect.

B

The session has a lifetime

Unlock for the work in front of you. Inactivity closes it.

C

The browser asks

One approved field crosses the gate. The vault does not.

Less interface.
More intention.

Search, inspect, copy, leave. Silo’s shell keeps the useful path short and makes sensitive actions visible.

Navigation
Arrow keys or j / k
Copy password
c · clears after 20s
One-time code
o · generated locally
Silo unlocked
/ Search authentications

3 entries · ↑↓ move · ↵ open

Authentication / github

github

Usernameoctocat
Password••••••••••••••••••
One-time code284 519 18s

Four parts.
One boundary.

Built like the object it borrows its name from: a clear exterior, repeated structural ribs, a narrow access point, and a protected center.

Silo architectureA corrugated grain silo with four selectable layers for core, CLI, broker, and native host.01020304

Start with one file

Brng your vault
closer to home.

Silo is an open-source CLI tool for local development. Read the code, run it locally, and understand every boundary before you trust it.