Who it's for
WhyMark for developers
Docs, issues, gists, Stack Overflow threads — you save them for a bug, then lose them by Friday. WhyMark keeps the bug with the link: “for the cache bug” finds it weeks later.
Save the bug with the doc
Your note — the error, the ticket, the project — is indexed. Search the symptom, get the page. No more re-googling solved problems.
Keyboard-first
Command palette on ⌘K, search on /, done without the mouse. Built for hands that live on keys.
Snippets and threads count too
Anything with a URL is fair game: docs, PRs, issues, gists, blog posts. One library instead of ten open tabs.
An example save, from capture to recall
- 1. Paste a source URL and add a note: “For the cache bug in the Next.js project”.
- 2. Keep it in your “Current project” collection; add a tag if it spans projects.
- 3. Later, search “cache bug” to match the words in your note.
Illustrative workflow for the web app. Public sign-ups are not open yet; pricing has not been announced. Join the waitlist for launch news.
How developers use it
Tag by stack (#react, #postgres), collect by project, and let the triage queue absorb the daily flood of tabs.
When the same bug returns, your past self already left the answer — with the reason attached.
Honest limits
WhyMark is pre-launch and web-only: no extension, no IDE integration, no API yet. If one-click saving is essential today, join the waitlist for the extension.
Questions
Is there an API?
Not yet. The web app comes first; integrations follow the launch.
Where does my data live?
In the cloud, on our servers — reachable from any browser you sign into. No local files to lose.