Your whole day, on one quiet line.
Throughline folds your calendars, tasks, and tools into a single timeline you shape by talking. It answers one question, what do I do next, and holds everything else until it matters.
Zero-knowledge, end-to-end encrypted. The server can store your day and can never read it.
Everything lands on one line.
Google Calendar, Apple Calendar, GitHub, Canvas, and any MCP tool your work lives in. Each source keeps its color and its name, and the pile stops being a pile.
Connections are per-account and read through one guarded gate. Tokens are encrypted at rest, and every outbound call passes an SSRF guard.
Shape it by talking.
No grid to fill in. Tell it the morning went sideways, that you need slack before the deploy, that the essay matters most. The plan redraws around what's true, with breaks you'll actually take.
Wire up a key you bring and hold (Claude today), entered in-app. The assistant asks per tool, confirms before it writes, and no shared server key exists.
When it's time to focus,
the room changes.
One thing at a time. Truly.
In focus, Throughline holds a single card: the block you're in, how long it has, and nothing else asking for you. A pomodoro if you want it. If you go still, it checks in. That's all.
The server can store your day. It can never read it.
Throughline is zero-knowledge: your plans are encrypted in your browser before they leave it, and the key never does. This is not a policy promise. It is a property of the math.
The same rows, twice: as your browser renders them, and as the server actually stores them.
- Sealed in your browser
- Plans, notes, and goals are locked with keys only your password or a recovery code can unwrap. The server never holds a key, so there is nothing for it to lose.
- Messages + files, end to end
- DMs, group chats, hand-offs, and attachments travel device to device. The server is a blind relay for sealed data it cannot open.
- Fresh keys, always
- Direct messages use a fresh key for every message, and old keys are gone the moment they're used. Rooms re-key when someone is removed, so an old copy of a room key opens nothing new.
- Safety numbers
- Every conversation carries a number both sides can check. If it matches, there is no impostor in the middle.
- Deletion that deletes
- Deleting your account destroys the keys themselves, which turns every stored copy, backups included, into noise. Gone means gone.
- Your own assistant key
- The assistant runs on a Claude API key you enter and hold. There is no shared server key reading anyone's day.
Company that doesn't talk over you.
Sessions are shared rooms for working alongside. Drop onto a line with people doing the same kind of thing and they gather into a constellation, clustered by activity, computed on your device.
Kicking someone rotates the room key. Removed is cryptographic, not a checkbox.
When the day winds down,
it lets you go.
Some wants are longer than a day.
Arcs hold them: a destination plotted through a few nav markers, with exactly one next jump surfaced at a time. Pull it into today when there's room.
The heading stays true until you get there. A week away breaks nothing.
The day closes gently.
An evening card shows what got done and offers to carry the rest to tomorrow. One tap, and tomorrow already has its first draft.
Knowing the next step is what keeps you moving.
Start with one morning.
Throughline is in quiet early access. A person approves each account, not a funnel. Ask, and we'll open the door.
Sealed end to end · yours alone