How it works
Three steps, no servers, nothing to babysit.
-
01
Install the plugin
Add the Shard plugin to Obsidian and paste the Connect code from your account. That's the whole setup — no server, no config file, no terminal.
-
02
Your vault gets an always-on copy
Your notes stay on your devices. We keep a copy in sync and awake around the clock, so there's something to reach when you aren't there.
-
03
Connect your tools
Claude connects through a standard MCP connector. Everything else — schedulers, scripts, no-code tools — reaches the same vault over a plain HTTP API. Whatever they write shows up in Obsidian like you typed it.
Things your vault can do now
We're the always-on half; the automation is still yours — point Claude, a scheduler, or whatever tool you already use at it. These are the things Obsidian could never be part of, because it was only awake when you were.
-
Inbox that fills itself
Starred email, saved article, forwarded receipt — appended to a note before you've thought about it.
-
Meeting notes that file themselves
Call ends, transcript lands in the right folder with the right links, tagged and dated.
-
An assistant that actually remembers
Claude reads and writes your real notes — ask it anything you've ever written down.
-
A daily note that's ready first
Today's calendar, yesterday's leftovers, the weather — drafted before your coffee is.
-
A weekly review you didn't write
Every Friday: what you added, what you finished, what you keep putting off — summarised into one note.
-
Capture from anywhere
A form, a shortcut, a bot — anything that can reach the web can drop a thought into your vault.
Still your notes. Actually yours.
-
Plain files, on your devices
Your vault stays exactly what it is: markdown files you can open, move, or back up yourself. Cancel any time and every word is still right there.
-
One credential per connection
Claude gets its own credential, and every device you sign in gets its own — so one can be cut off without disturbing the rest. Self-serve revocation is the next thing we're building; until it lands, you email us and we do it.
-
Encrypted at rest, and honest about the edges
Note bodies are encrypted where they're stored, under a key held in a managed KMS. Attachments aren't encrypted yet. And this is encryption at rest, not end-to-end — the server can read a note in order to serve it. We'd rather you knew that than assumed otherwise.
Fair questions
-
Does Obsidian need to be open for this to work?
No — that's the whole point. Your automations run against the always-on copy; Obsidian catches up the next time you open it.
-
What happens if I stop paying?
Your notes are already on your devices, in plain files. You lose the always-on connection, not a single word.
-
Do I need to know how to code?
For the Claude side, no — you connect it once and then just talk to it. Scheduled automations need something that can make an HTTP request; most no-code tools have a step for exactly that. There's no native Zapier or Make app yet.
-
Can something I connect mess up my vault?
Yes. Anything that can write can also delete — Claude included, though its delete tools are flagged destructive so your client asks first. We'd rather say that than sell you a guarantee we don't have. Each connection has its own credential, so one can be cut off without touching the others, and your own backups are still worth keeping.