September 11, 2026 Built Supanote for devs who share more than plain text

I share code, logs, and markdown all day — bug reports, runbooks, API payloads, stack traces, internal docs.

Most tools treat everything like a flat text file: wrong preview, weak formatting, dead-end links with no way to follow up.

So I built Supanote.

Core flow is simple: paste → clean link → proper preview

But I wanted it to feel like a real dev tool, not a generic note app:

Rich markdown primitives — beyond basic headings and code blocks:

  • :::note / :::warning / :::tip callouts

  • :::tabs for multi-section docs

  • :::terminal, :::request, :::file blocks

  • :::checklist, :::progress, :::stat for runbooks & status updates

Paste a technical doc and it renders like one.

Threaded replies — follow-up on a shared snippet? Reply with a linked note. Full thread view, reply policies (open link / signed-in only / disabled). Lightweight discussion around shared content, not a one-way dump.

Also: auto format detection (JSON, logs, code, HTML…), optional encryption, burn-after-read, REST API + MCP for AI workflows.

Still early, but I use it daily.

Honest feedback welcome:

https://supanote.app

What’s missing from your snippet-sharing workflow?

1 Comment

  1. 1
    Daily personal use is a good signal. Have other developers started using Supanote repeatedly for real bug reports, runbooks, or API payloads, or are people mainly trying it once because the richer formatting looks useful?

About

Sharing dev snippets shouldn't be ugly or broken. Supanote: paste anything, get a clean link with the right preview.