gitt.pub
Write it in Git. Share it with anyone.
GittPub turns files in your repository into clean pages with private links. Choose the files, send the link, and keep committing. Every push updates the page, and your readers never need a GitHub account.
Free for one repository and 50 files. GittPub never changes your code.
Illustration: RFC 0042 shown twice, as raw Markdown in a Git host and as a clean GittPub page with a private link.
3e1f0a2 the gap
Your docs live in Git. Your readers don't.
Teams write RFCs, reports, and notes in the repository because review and history already live there. The trouble starts when someone outside the repository needs to read one.
Sharing one file means sharing everything.
To show a PM one RFC, you add them to the repository, where they can see every other file. Or you export a PDF that is out of date by Friday.
GitHub is built for reviewing code.
Readers land on file trees, branch menus, and commit hashes before they reach the first paragraph.
Your readers don't have GitHub accounts.
A client, an editor, or your legal team won't create a developer account to read a three-page document.
a1b2c3d how it works
Pick the files. Send the link. Keep committing.
Connect a repository.
Install GittPub on the repositories you choose, from GitHub, GitLab, Bitbucket, or any Git host. It reads your files and never changes your code.
Write a rule.
A rule is a list of patterns, like
docs/rfcs/*.md. Before anything goes live, a preview shows every file that matches.Try a rule
One pattern per line. Start a line with ! to exclude.
- .env, skipped
- README.md, skipped
- docs/rfcs/0041-auth-tokens.md, published
- docs/rfcs/0042-incremental-sync.md, published
- docs/rfcs/0043-webhooks.md, published
- docs/rfcs/drafts/0044-billing.md, skipped
- docs/guides/onboarding.md, skipped
- reports/2026/q3-board.pdf, skipped
- reports/2026/q3-metrics.csv, skipped
- secrets/prod.key, skipped
- src/server/sync.ts, skipped
- src/server/sync.test.ts, skipped
- design/exports/logo.svg, skipped
3 files will be published
Share the link.
Each file gets its own unguessable URL. Send it to anyone, or only to the people you name.
After that, you work in Git as usual. Push a change and the page updates. Rename the file and the link keeps working.
4f2a91c sync
The page follows the file.
GittPub watches the branch you choose. When a commit changes a published file, the page changes with it. When a commit renames the file, the URL stays the same.
a1b2c3d
Draft incremental sync RFCThe page is published.
4f2a91c
Address review commentsThe page updates. Readers who watch it get an email listing what changed.
9c0e7b2
Move RFCs into docs/rfcs/acceptedSame link, new path.
e81d5aa
Remove superseded draftThe link shows that the file is no longer published.
9c0e7b2 reading
Pages people want to read.
Readers get the document without the repository around it: clear type, a table of contents, dark mode, and a layout that prints well and works on a phone.
Markdown with diagrams and math
PDF with page thumbnails
CSV you can sort and filter
Jupyter notebooks
Code with line links
3D models you can orbit
Excalidraw and draw.io
Images, audio, and video
See what changed.
Readers can compare any two versions. In Markdown, changed paragraphs are highlighted in the rendered page, down to the word.
Illustration: a paragraph where the words “once an hour” are struck through and “on every push” is inserted.
b7d41e9 access
You choose who reads it.
Anyone with the link.
For release notes and public specs. Add a password, an expiry date, or a view limit.
Only the people you name.
Grant access to ana@acme.com, to everyone at @acme.com, or to your workspace. Readers sign in with email, Google, or GitHub. Anyone else sees a sign-in page that reveals nothing about the file: no title, no repository, no owner.
Rotate, expire, or revoke any link without touching the file.
Illustration: the share dialog for RFC 0042, restricted to ana@acme.com, everyone at acme.com, and the workspace. Ana viewed it 3 minutes ago.
deny list
Keys, .env files, and credentials are blocked before a rule can match them.
secret scan
Content is checked for secrets before it publishes.
audit log
Every publish is recorded.
c55a210 feedback
Feedback lands where the work is.
Readers select a paragraph and leave a comment. Turn any comment into a GitHub issue with one click; it carries the quoted text and a link to the exact version.
Illustration: Maya from Legal comments on a highlighted sentence about data retention, and the comment becomes issue #214, “Clarify data retention in RFC 0042”.
d02f8c1 who it's for
For documents that live next to code.
Design docs and RFCs.
For teammates, PMs, and vendors without repository access.
Client deliverables.
Reports, PDFs, and slide exports for a client's stakeholders.
Release notes and roadmaps.
One public page from a public repository.
Notes from Obsidian or Foam.
A handful of notes out of hundreds, for an editor or a reviewer.
Design exports.
PNG, SVG, and PDF files for a client who should not see the rest of the repository.
e81d5aa pricing
Start free. Pay when it's working.
Free
$0$0
- One repository
- 50 published files
- Email grants
- 30 days of history
- View totals
Pro
$12/month$120/year
Everything in Free, plus:
- 10 repositories
- 2,000 published files
- Domain grants
- Full history
- One custom domain
- Full analytics
- No GittPub footer
Team
$20 per seat/month$200 per seat/year
Everything in Pro, plus:
- Unlimited repositories
- 20,000 published files
- Workspace grants
- Five custom domains
- Analytics export
- Watermarking
- SSO