Write in a real markdown editor, organize on a board, and publish straight to GitHub as clean commits. No database to sync, no webhooks to babysit, no lock-in — your repo stays the source of truth.
Open Source · MIT · BYO keys · No credit card
Everything you ship is a commit
Write
Markdown with live preview, schema-driven frontmatter, and AI polish on your own keys. The kind of editor you'd actually choose to write in.
Frontmatter
Most developers write in markdown — but publishing still means committing, pushing, and waiting on a deploy to finish.
Wryte changes that. One click from editor to your repo.
Organize
Every article is a card. Drag it from Draft to Published, schedule it for later, edit tags inline — and move through it all with vim-style keys.
API Reference
Migration Guide
Getting Started
Shipping Faster
Changelog v0.19
How it fits together
The editor, the board, and the scheduler all feed a single publish engine. It writes plain markdown straight into your repo — so GitHub, not Wryte, owns your content.
01
Markdown + live preview. Auto-save on every keystroke.
02
Kanban columns track status. Drag, tag, schedule.
03
Durable scheduling, diff-before-sync, conflict detection.
04
The single source of truth. Real markdown, clean commits.
Wryte never becomes a place your content gets trapped. It's a writing and publishing layer on top of your repo. Delete your account tomorrow and every word still lives in GitHub as version-controlled markdown.
Wryte compares against the file SHA in your repo and only writes what actually changed — no noisy commits.
Edited the same file on GitHub directly? Wryte spots the drift and lets you resolve it before publishing.
Scheduled publishes run on a workflow engine with retries — they fire even if you're offline.
Where Wryte stands
Payload, Sanity, and Contentful keep your content in their own database and treat git as an export problem — so you wire up webhooks and pray they fire. TinaCMS gets closer, but you have to wrap your whole site in its config. Wryte points at any GitHub repo and writes plain markdown commits. Nothing to install in your codebase.
| Capability | Payload | TinaCMS | Sanity | Contentful | |
|---|---|---|---|---|---|
| Source of truth | Its own database | Your git repo | Hosted dataset | Hosted cloud | Your GitHub repo |
| Content stored as | DB rows | Markdown / MDX | Proprietary docs | Proprietary entries | Plain .md files |
| Git-native workflow | None — export first | Tied to its config | None | None | Every change is a commit |
| Infra to run | DB + app to host | Self-host or Tina Cloud | Hosted SaaS | Hosted SaaS | Zero — commits to your repo |
| Works with any repo | Build around its schema | Wrap your site in Tina | Fetch via GROQ/API | Fetch via API | Point it at a repo + path |
| Editorial kanban board | — | — | — | Enterprise add-on | Built in |
| Scheduled publishing | Custom / plugin | Roll your own | Add-on | Native | Durable cron + retries |
| AI assistance (BYO keys) | — | — | Paid add-on | Paid tier | BYOK, never proxied |
| Vendor lock-in | Your DB, OSS app | Low–medium | High | High | None — your repo, your keys |
Take Payload. It's a great code-first CMS — but you stand up a database, model collections in code, host the app, and your content lives in Postgres or Mongo. Getting it into a git-backed static site means an export step and a build hook. Wryte skips all of it: the markdown files are the content, and the commit is the publish.
Comparison reflects typical out-of-the-box setups. Every tool here is capable — Wryte just optimizes for one workflow: markdown in a repo.
Desktop App
The full Wryte experience as a cross-platform desktop app. Built with Electron — same editor, same board, same git-native workflow. No browser tab required.
One command, always up to date.
brew install rafay99-epic/apps/wryteNative shortcuts
Full keyboard-driven workflow. System menus.
Auto-updates
Seamless background updates. Latest features.