Reactive Resume

[!IMPORTANT] Reactive Resume now lives at reactive-resume/reactive-resume on GitHub.
GHCR images publish to ghcr.io/reactive-resume/reactive-resume.
Docker Hub stays at amruthpillai/reactive-resume.

Create a free account, import an existing resume or start fresh, and see the finished page as you write. Download a PDF, Word, Markdown, or JSON file, or share your resume with a public link. You can also run the whole application on your own infrastructure.

You own your data. The codebase is open source under the MIT license, with no tracking, no ads, and no paid tier. Optional AI features use a provider you connect; hosting and provider usage may have their own costs.

Build a better resume, together

Join the Reactive Resume community on Discord to exchange resume feedback, get help using or self-hosting the app, and share ideas with other users and contributors.

• Resume feedback: post a redacted resume and one specific question, or help someone improve theirs.
• Help: find troubleshooting discussions and ask questions in dedicated forum threads.
• Contribute: discuss ideas, translations, and code with the people building Reactive Resume.

Feedback comes from fellow community members. Remove contact details and other private information before posting.

Features

Write, Design, and Check

• Redesigned editor with inline content editing and click-to-select on the page
• Live PDF preview and browser downloads powered by Forme, rendered in a background worker
• Rich text, custom sections, drag-and-drop ordering, and structured dates with consistent formatting
• Autosave, local recovery of unsaved resume drafts, and up to 200 undo steps
• Phone and tablet layouts, keyboard shortcuts, and a searchable command bar

Templates and Customization

• 18 templates, including the new Porygon and Smeargle, previewed with your own content
• One-column, two-column, and ATS-safe template filters
• Font presets, custom fonts, colors, spacing, A4 and Letter paper, and left or right sidebars
• Fit overflowing content by adjusting density, margins, and text size
• Custom Styles written as Semantic CSS, with an element picker on the page

Resume Checks

• Readability checks with findings pinned to the relevant lines
• Job-posting keyword matching and a view of the text hiring software reads
• Checks on the exported PDF, plus an optional AI writing review
• A public ATS checker that reads PDFs in your browser without an account

Documents and Cover Letters

• One searchable library for resumes and letters, with tags, sorting, and grid or list views
• Standalone cover letters with their own editor, exports, and version history
• Link a letter to a resume to keep its sender details and design in sync, or customize it independently
• Automatic and named versions you can preview and restore
• Trash with Undo and a 30-day recovery window

Job Applications

• List, Board, Insights, and Calendar views for tracking applications from Saved to Offer
• Save jobs from a URL or pasted posting; optional keyword search through Firecrawl, Tavily, or Exa
• Tailor a resume and draft a cover letter for a saved job
• Track contacts, notes, follow-ups, application outcomes, and the documents you sent
• Schedule interviews, export calendar events, and import or export applications as CSV

AI Assistant

• Assistant beside your resume or letter, with conversations tied to that document
• Proposed edits show what changes and why; accept or reject each suggestion
• Improve selected text, review writing, and draft letters from a resume and job posting
• Connect OpenAI, Anthropic, Google Gemini, OpenRouter, Ollama, or other supported providers and compatible endpoints
• Optional web search and page reading; self-hosters can configure shared AI and web-access providers

Import, Export, and Sharing

• Import Reactive Resume JSON, JSON Resume, LinkedIn data exports, PDF, and Word files
• JSON, LinkedIn, and readable PDF imports work without AI; Word imports require a connected provider
• Export resumes and letters as PDF, Word (DOCX), Markdown, or JSON
• Share resumes through public links with optional password protection and view/download statistics
• REST API and MCP server for document management, imports, exports, checks, and application workflows

Privacy and Control

• Self-host with Docker, Vercel, Cloudflare Workers, or a 1-click deploy on Hostinger
• No tracking or ads; export your account data or delete your account
• Passkeys, two-factor authentication, and linked sign-in providers
• Multiple interface languages, light/dark/system themes, and reduced-motion support

Templates

Quick Start

Use the hosted app to start writing, or build this checkout locally with Docker and Docker Compose:

# Clone the repository
git clone --depth=1 https://github.com/reactive-resume/reactive-resume.git reactive-resume
cd reactive-resume

# Create your local configuration
cp .env.example .env
# Edit .env: set AUTH_SECRET and a separate ENCRYPTION_SECRET.
# Generate each secret with: openssl rand -hex 32

# Build the app and start PostgreSQL, Redis, and SeaweedFS
docker compose up -d --build

# Open http://localhost:3000 in your browser

This builds the checked-out source. For a deployment using published images, follow the Docker guide. For source development, see the development setup guide.

Tech Stack

Documentation

The full documentation lives at docs.rxresu.me:

Self-Hosting

Reactive Resume runs the same application everywhere: PostgreSQL for data, plus storage for uploads. Pick the option that fits how much you want to manage.

PDF generation in v6 uses Forme in the browser and on the server. No Browserless, Chromium, or external print service is needed. Legacy PRINTER_* and BROWSERLESS_* environment variables can be removed.

Hostinger

The quickest way to get going is a 1-click deploy on Hostinger, starting at $6.49/month. Their VPS plans include a ready-made Reactive Resume template that provisions the Docker environment and brings the app up for you, with weekly backups and a Docker manager UI included — so you can skip the setup entirely.

See the Hostinger guide for what the template sets up and what to configure afterwards, such as email, your own domain, and turning off sign-ups.

Vercel

Vercel provisions Neon PostgreSQL, private Blob storage, and Upstash Redis through its deployment wizard. Supply two persistent secrets and use the Services framework preset. Static assets run in the frontend service, and Hono serves the application routes and APIs from the backend service. See the Vercel guide for setup, limits, and optional SMTP/OAuth configuration.

Cloudflare Workers

Cloudflare deployment requires Workers Paid and uses Static Assets, private R2 storage, SQLite Durable Objects, and PostgreSQL through Hyperdrive. Supply an existing PostgreSQL database and apply migrations before deployment. See the Cloudflare guide for setup and runtime limits.

Docker and Kubernetes

The application needs:

• PostgreSQL — Accounts, documents, applications, and assistant conversations
• Upload storage — A persistent local directory or an S3-compatible bucket, such as SeaweedFS
• Redis (optional) — Shared coordination across instances and resumable assistant replies
• SMTP (optional) — Verification and password-reset emails

Published releases are available from Docker Hub and GitHub Container Registry (latest tracks the latest stable release):

# Docker Hub
docker pull amruthpillai/reactive-resume:latest

# GitHub Container Registry
docker pull ghcr.io/reactive-resume/reactive-resume:latest

See the Docker guide or Kubernetes guide for complete instructions. Running on a NAS? See the Synology and UGREEN guides.

Configuration

Every setting is listed in the environment variables reference. Self-hosters can also configure shared AI and job-search services and single sign-on.

Upgrading from v5

Back up your database and uploads and stop all v5 instances before applying v6 migrations. Old visual style rules require a manual conversion; API and MCP integrations also have changes. Follow Migrating from v5.

Support

Reactive Resume is and always will be free and open source. If it has helped you land a job or saved you time, please consider supporting continued development:

Other ways to support:

• Star this repository
• Report reproducible bugs and suggest actionable features
• Help other users in GitHub Discussions
• Improve documentation
• Help with translations

Star History

Contributing

Every contribution helps, whether it is a typo fix or a new feature.

1. Fork the repository
2. Create a feature branch (git checkout -b feature/amazing-feature)
3. Commit your changes using Conventional Commits (git commit -m 'feat: add amazing feature')
4. Push to the branch (git push origin feature/amazing-feature)
5. Open a Pull Request

See the development setup guide for how to run the project locally.

Maintainers review the status: needs triage queue weekly. Triaged bugs become status: confirmed; feature proposals become status: accepted; reports that need details become status: needs info.

License

MIT — do whatever you want with it.