Open source · MIT licensed
A home for your specs
Turn a Git repository of Markdown documents into a fast, searchable website. Write a spec, open a pull request, discuss, merge — Dossiers tracks every change and gives everyone a clean, read-only view of the current state.
$ cargo install dossiers
$ dossiers serve ./specs
🚀 Serving at http://localhost:8080Why Dossiers?
General documentation tools want a book. Your organization writes a stack of independent, inter-linked documents. Dossiers is built for exactly that.
Purpose-built for specs
Designed for collections of independent, inter-linked specifications — not books or wikis. No configuration needed: just add your Markdown files.
Full-text search
Find what you need instantly with built-in search across all documents — in the hosted service and in self-hosted deployments alike.
Built-in authentication
Limit access to your Google Workspace domain or GitHub organization. Keep internal specs private with zero infrastructure setup.
Beautiful rendering
Clean, responsive pages with automatic tables of contents, syntax highlighting, diagrams, and cross-document links. Dark mode included.
Pull request integration
Drafts in progress are detected automatically and shown alongside published specs, so reviewing proposals before the merge is effortless.
Host anywhere
Use the hosted service at dossie.rs, or generate a static site for GitHub Pages, Netlify, Vercel, or your internal CDN. You own your data.
From Markdown to published in minutes
No new tools to learn — Dossiers plugs into the Git workflow your team already uses every day.
-
1
Write specs in Markdown
Plain files with YAML frontmatter for status, authors, and dates — stored in the repository you already have.
-
2
Review in pull requests
Discuss changes the same way you review code. Every revision and every decision stays in the history.
-
3
Publish everywhere
Run
dossiers servefor a live site ordossiers buildfor static hosting — or let dossie.rs handle it for you.
Use cases
Product specifications
Feature proposals, PRDs, technical designs
Company policies
Employee handbook, security policies, data governance
Process documentation
Release workflows, incident response playbooks, onboarding guides
Architecture decision records
Document why technical decisions were made
You're in good company
Storing specifications in Git isn't new — it's a proven pattern used across the industry.
Rust, React, Python
Use Git-based RFC/PEP processes with pull request reviews for language and framework changes.
Joyent
Pioneered the RFD (Request for Discussion) process for internal specifications.
Oxide Computer
Built sophisticated RFD tooling with web frontend, API backend, and CLI that inspired Dossiers.
Ready to get started?
Try Dossiers with your own specification repository today.