We launched Ozu, a tool that lets you share local Markdown directly from your code editor and keep updating it at the same URL.

Ozu came out of a very real frustration within our own team.
We were writing more and more Markdown with AI, but the way we shared those documents afterward still felt clunky.

With tools like Codex and Claude Code, we now write Markdown documents far more often, not only for source code, but also for things like:

• Writing local notes
• Organizing specifications together with AI
• Drafting early project ideas
• Capturing research in progress
• Documenting operational procedures

We believe the number of local documents created through this kind of workflow will only keep growing. And this is not limited to engineers. Product managers, marketers, sales teams, and company leaders are also starting to open local editors and think together with AI.

For a while, we had been thinking that there should be a lightweight way to share these documents.

There are already many tools for sharing documents.

But:

• If you post it in Slack, it quickly gets buried
• If you move it to Notion, you end up managing it in two places
• If you share it through GitHub, it can feel heavier than necessary, with pull requests, reviews, and so on
• Every time you update it, you have to send it again

Writing documents has become faster, but the workflow after sharing is still centered around cloud-based tools.

We wanted to share something quickly from local files, but doing so often created duplicate management. That gap had always felt uncomfortable to us.

What Ozu Can Do

What Ozu does is simple.

• Share locally managed Markdown directly from your code editor
• Generate a fixed URL when you share it
• Keep updating the same URL afterward, while making the document viewable in a web browser

It is not trying to do something flashy.
But this small layer was surprisingly hard to find.

Ozu focuses on keeping local Markdown as the source, while adding a surface for sharing and continuous operation.

The Shape of Document Sharing in the AI Coding Era

In the AI coding era, the amount of text around code will grow significantly, not just the code itself.

• Specification notes
• Planning notes
• Research summaries
• Onboarding procedures
• Technical notes before sharing with customers
• Drafts that need team feedback

And many of these are not finished documents. They are works in progress.
That is exactly why it matters to keep updating the same URL, instead of sharing something once and letting it end there.

As AI makes it faster to create documents, we believe what teams need is not an even larger document platform, but a lightweight operational layer that lets locally created Markdown keep being shared as-is.

That is what Ozu is for.

Who Ozu Is For

Ozu is especially useful for teams like:

• Development teams that use Markdown every day
• Small teams where PMs and engineers work closely together
• Teams that increasingly write documents locally with AI
• Teams that share documents frequently and collaborate actively

We think this will feel very natural to those teams.

At events and exhibitions, engineers and people from tech startups understood the idea very quickly.
Even without much explanation, we often got the reaction: "Yes, we have had that problem."

Try It for Free

Anyone can try Ozu for free. We are also offering an early team adoption plan for the first 10 companies.

• Share Markdown from your code editor
• Generate a fixed URL
• Keep updating the same URL

We hope you try this seamless way of working.

Ozu
https://ozu.to/