Stop rewriting your Obsidian notes for your team.

The problem

Sharing an Obsidian note today means rebuilding it in Notion, Docs or Gamma

The Q4 plan is finished in Obsidian, with headings, three tables and your callouts. To get it in front of the team you paste it into Google Docs or Notion. The tables break, the callouts turn into plain text, and you spend 30 minutes copying something you already finished.

Then the comments land in the Doc, not in your note. By week two there are two plans, and Claude, which reads your vault when you ask "what did we decide?", reads the stale one.

How it works

Share an Obsidian note with your team, and their edits come back into it

Think of a shop window. People on the street see what's inside, and with myone.page they can also write on the glass. Whatever they write goes straight through to the note behind it, which stays in your vault. There's no export, no second document, and nothing to merge by hand.

1. Write. Add myone.page: true to any note and it opens as a styled page. Or start from a template in the plugin, or let AI write it.
2. Share. Add share: new and list who may edit or read: emails, a whole @company.com, or anyone with the link. The link is copied for you.
3. Round trip. Your team clicks into the text and types. Within 60 seconds the edit is in your note. Edits to different lines merge automatically. If you both changed the same line, their version is saved next to your note, so nothing is ever overwritten.

Why nobody else does this: on 7 Oct 2026 we checked all 8,500+ Obsidian community plugins. Not one turns a note into a shared page whose web edits come back into the note.

Security

End-to-end encrypted: we can't read your pages

• The key is in the link. It sits after the #, and browsers never send that part to a server. We store and serve ciphertext only, including the page history.
• Every page is private unless you open it up. A page that isn't shared with someone looks exactly like one that doesn't exist.
• Nothing leaves your vault without share:. Delete the line and the page goes offline. If a link leaks, set share: new again and the old link stops working.
• A standard you can check. AES-256-GCM through the browser's built-in Web Crypto, no home-made cryptography. Each page's address is sealed into its ciphertext, so one page's text can't be passed off as another's.
• What we can still see: who you share with, when a page changes, and how big it is. Never titles or text.

Write it with AI

Let Claude or ChatGPT turn your rough notes into a one-pager

1. Make a page with AI on any note copies a request: the page format and your note.
2. Paste it into Claude, ChatGPT or Gemini, then paste the answer back.
3. It's a page, as a new note next to yours. Yours stays as it is.

Or give Claude the format once, as a skill, and just ask for a one-pager. Claude Code, Codex and Cursor can write pages straight into your vault. How it works, or read the step-by-step guide to writing a one-pager with AI.

See it first

Open seven finished one-pagers. No sign-in, nothing to install.

Each one is a single Markdown note, written once in Obsidian. This is exactly what your team opens from a link. Here they're read-only; the people you share with can edit them. Six of them are also free templates in the plugin, and there are five more: a project status report, a weekly update, a project brief, a one-page business plan and a company one-pager. Use this template on a page opens it in Obsidian as a new note. New to the format? Start with what goes on a one-page report.

For foundersMonthly investor update

MRR, burn and 18 months of runway in four numbers, highlights and lowlights, three asks and last month's goals scored, in the format YC recommends. One link to every investor, instead of an email they skim.

For founders with a boardBoard pre-read

The big picture, every number against plan and one pricing decision, laid out the way Sequoia suggests. Sent two days ahead, so the meeting is spent on the decision.

For agencies and consultantsClient proposal

A $96K checkout project with the funnel, an 8-week timeline and three prices. Make the client an editor and they change the scope on the page, not in a reply-all.

For agenciesClient results report

A quarter of results against the goals, spend and return by channel, what worked and the next 90 days on a timeline. The client sees it live, not as a PDF in their inbox.

For CEOs and boardsStrategy memo

Diagnosis, guiding policy and four actions, with a lean canvas and the 2027 plan. The page the board reads before the meeting, not during it.

For product managersProduct brief

A Shape Up pitch: the problem in four numbers, a six-week appetite, the solution, rabbit holes and no-gos. Engineering edits the spec on the page, and it stays in your vault.

For researchThe Obsidian plugin market

8,566 plugins and 156M downloads: the top 20, the fastest risers and the seven patterns behind the winners. Claude drafted it from public data in one sitting.

In seven themes, each light and dark

Pick one in the plugin's settings and every page takes it: its own corners, borders, shadows, spacing, fonts and headings. Minimal, GitHub, Things, Cupertino and Claude Warm follow the Obsidian themes of those names; Paper reads like a printed report. ☀ / ☾ in a page's bar switches light and dark, and your readers can switch it for themselves.

Will your notes look like this? Yes. These use the same blocks as the free plugin. Add one line to a note and it renders the same way, in Obsidian and on the web.

Who builds it

Built by a three-time CTO, held to production standards

“In September I had a Q4 plan and two town-hall pages to get in front of my team. I'd already written all three as notes, and I wasn't going to rebuild them in Notion.

So I built a renderer that runs on the note itself. Then the team wanted to edit, so I made their edits come back into my vault.

Every strategy page we use now starts as a note, usually one Claude drafted, and it stays a note.”

• Tested end to end, in real apps. Before a change to sharing ships, 100+ automated checks run a real Obsidian and a real Chrome against a fresh copy of the server: the first share, edits syncing both ways, conflicts, sign-in, the free limit, restarts.
• Open code where your notes live. The plugin's source is public on GitHub under the MIT license, so you can read exactly what gets encrypted and what gets sent.
• No silent overwrites. Every save carries the version it started from, and a save made over someone else's is refused instead of replacing it.
• Checked on every release. Type-checked, linted with Obsidian's own review rules, and the release built by GitHub from the tagged code.

FAQ

Questions people ask before they share