Versume
Version your resume like code — every save is a git commit.
Details
- Role
- Author
- Started
- June 2026
- Language
- TypeScript
- Platform
- Web
- Licence
- MIT
Overview
A CV is a document people rewrite constantly and version badly — cv_final_v3_actually_final.docx is a genre. Versume treats it the way you would treat code: as structured data in a git repository, where every save is a commit and nothing is ever really lost.
You sign in with GitHub and Versume creates a private cv-store repository in your own account. Your CV lives there as JSON — one file per variant, so a backend-flavoured CV and a full-stack one are separate files rather than separate documents you forget to keep in sync.
Because the storage is just git, version history comes free. Every save is a commit you can inspect and restore. The data is in your GitHub account, not in someone else's database, which means the tool going away does not take your CV with it.
Highlights
- GitHub OAuth sign-in; data stored in a private cv-store repo you own
- Every save is a real git commit — restore any previous version
- Multiple CV variants as separate JSON files (e.g. backend, fullstack)
- Structured editor for Personal, Experience, Projects, Education, Skills, Languages
- Live preview that renders as you type, and PDF export
- Unsaved drafts survive a page refresh via localStorage
Built with
- Next.js
- TypeScript
- GitHub API
- NextAuth