For SRE + incident response
Stable URLs for public postmortems.
Postmortems belong to the community, not to your blog platform. Publish from a markdown file, get a URL that survives your next CMS migration.
What a permanent postmortem URL needs
Human-readable slug
yourorg/incidents/2025-09-12-database-outage beats docs.google.com/d/1xKz... every time you paste it into a runbook.
Markdown-native
Postmortems are written in markdown. No copy-paste reformatting into a block editor. Run one command, the file publishes as-is.
Versioned history
Update the postmortem as the RCA is finalized. Every save snapshots the previous state. The URL stays the same.
Not tied to your CMS
The URL lives on Anchorify's infrastructure, not your blog platform. Change your CMS next year and the postmortem link still works.
Versus company blog and GitHub Gist
| Anchorify | Company blog | |
|---|---|---|
| URL survives acquisition | ✓ | ✗ |
| URL survives blog migration | ✓ | ✗ |
| Markdown-native | ✓ | Varies |
| Human-readable slug | ✓ | Varies |
| Search-indexed | Yes (public shares) | Yes |
| Versioned history | Yes (all plans) | No (usually) |
| Per-visitor analytics | ✓ | ✗ |
| Free to publish | ✓ | Varies |
FAQ
What happens if Anchorify shuts down?
The markdown source lives on your machine and in your git repo. Anchorify does not hold the only copy. If the service shuts down, you can republish the file anywhere markdown is accepted. Anchorify is pre-launch beta, so this is a fair question to ask.
How is this different from a GitHub Gist?
Gists use a random opaque ID with no human-readable slug, render in a dev-tool aesthetic, and have no version history UI or per-visitor analytics. Anchorify gives you a human-readable slug, a document-shaped render, and version snapshots.
Can I redact details and re-publish?
Yes. Edit the local markdown file and re-run the CLI command. The URL updates in place and the previous version is snapshotted in the dashboard version history so you can see exactly what changed and when.
Can I have multiple authors?
The share is published by whoever holds the org token. Multiple team members can edit the markdown file in git; the person with the Anchorify token runs the publish command. Org invites let a second team member co-manage the share from the dashboard.
Publish your next postmortem at a URL that lasts.
Free during beta. One command from markdown to public URL.