Professional, privacy-first, and open-source career document engineering platform.
✨ Main Application · 📖 Documentation · 📰 Official Blog · 🗺️ Product Roadmap
VeriWorkly is a privacy-first career workspace: a resume and cover letter builder, a public portfolio/website builder, and the AI and career tooling (ATS scoring, AI rewriting, GitHub/LinkedIn import) that connects them — all built around one shared Master Profile so your career facts live in one place and flow into every document and every portfolio. It challenges the surveillance-heavy, login-first SaaS resume builder model by operating on a local-first principle: no account is required to start.
- ⚡ Real-Time Rendering: Edit details and see your ATS-optimized resume, cover letter, or portfolio update instantly with pixel-perfect live previews.
- 🌐 Portfolio Builder: A separate public website/portfolio product (
apps/portfolio) — template gallery, a three-pane editor, analytics, and publishing to a shared path or your own*.veriworkly.comsubdomain. - 🧠 Master Profile: One canonical career-facts record that auto-seeds new resumes, cover letters, and portfolios — editing a document never writes back to it.
- 🤖 AI & ATS Tooling: AI-assisted rewriting (Anthropic Claude and OpenAI GPT, credit-metered, cost shown before you generate) and a deterministic + AI-layered ATS checker.
- 🔒 Local-First Storage: Your data stays on your machine first. No mandatory account, tracking cookies, or remote server lock-in to start building.
- 📥 Universal Exports: PDF, DOCX, HTML, Markdown, plain text, and JSON — all client-rendered via
react-pdf, no headless-browser dependency. - ☁️ Optional Cloud Sync: Secure, cross-device sync for logged-in users, with per-document conflict detection.
- 🔧 API Extensibility: A self-serve developer API with scoped keys — see docs.veriworkly.com/api-reference for what's currently documented (auth, API keys, GitHub stats, health, roadmap, and core user endpoints; broader route coverage — documents, profiles, ATS, AI, portfolios, billing — is in progress).
Precision ATS |
Executive Clarity |
Professional |
VeriWorkly Special |
VeriWorkly uses a type-safe monorepo layout to ensure clean service isolation and high developer velocity.
veriworkly-resume/
├── apps/
│ ├── site/ # Marketing & Landing Site (Next.js)
│ ├── studio/ # Document Builder App & Workspace (Next.js)
│ ├── portfolio/ # Portfolio/Website Builder — gallery, editor, published sites (Next.js)
│ ├── server/ # Express API & Sync backend (NodeJS)
│ ├── docs-platform/ # Technical Documentation Hub (Fumadocs)
│ └── blog-platform/ # Official Product Blog (Next.js)
└── packages/
└── ui/ # Shared UI Design System & Component Library
| Layer | Technologies Used |
|---|---|
| Frontend Applications | Next.js 15 (App Router), React 19, Tailwind CSS 4 |
| Backend API | Node.js, Express, TypeScript |
| Data Persistence | PostgreSQL (Prisma ORM) |
| Rendering Pipeline | react-pdf (Client-side high-fidelity generation) |
| Authentication | Better-Auth (Passwordless OTP) |
| State Management | Zustand (with localStorage persistence) |
To run VeriWorkly locally on your system, follow these commands:
-
Clone the Repo & Install Dependencies
git clone https://github.com/VeriWorkly/veriworkly.git cd veriworkly-resume npm install -
Configure Environment Variables
cp .env.example .env cp apps/server/.env.example apps/server/.env
-
Deploy Local Database migrations
npm run db:push -w @veriworkly/server
-
Launch Dev Environment
npm run dev
Deploy the complete ecosystem (database, backend server, and frontend client) instantly via Docker Compose:
docker compose --env-file .env.docker up -d --build| Resource | Description | Location |
|---|---|---|
| Technical Documentation | Monorepo architecture, API Reference, deployment. | docs.veriworkly.com |
| User Support & Guides | Walkthroughs for editing, building and templates. | User Guides Hub |
| Manual Setup Guide | Standard local environment installation. | README.Local.md |
| Docker Operations | Configuration, environment variables, orchestration. | README.Docker.md |
| Contributing Guide | Repository protocols, standards, and git guidelines. | CONTRIBUTING.md |
VeriWorkly is built on open-source principles, and we welcome community contributions!
Important
Before checking out a branch or creating a pull request, please review our full Contributing Guidelines.
- 🌟 Star the repository to show your support.
- 📋 Claim an issue by commenting on it and waiting to be assigned before starting work. PRs submitted for unclaimed/unassigned issues will not be merged unless claimed. Authors have a 7-day grace period to claim them, otherwise they may be closed. Priority always goes to the contributor who officially requested the claim.
- 📝 Ensure your PR titles follow the standard naming convention.
- Code: Implement new features, performance improvements, or address open issues.
- Design: Build and submit new ATS-optimized resume templates.
- Docs: Refine explanations, fix typos, or add code setup examples.
- Feedback: File bugs or suggest future features on our product roadmap.
We take security and user data privacy very seriously:
- Local-First Architecture: Your resumes reside locally in your browser storage.
- No Third-Party Tracking: No mouse tracking, heatmaps, ad trackers, or sale of user data. We do run first-party, aggregate-only product telemetry (e.g. counts of resumes created or exports) to understand usage — never individual behavioral tracking.
- Vulnerability Disclosure: If you discover a security issue, please do not file a public GitHub issue. Email us privately at
info@veriworkly.comwith steps to reproduce. Read SECURITY.md for more info.
VeriWorkly is released under the MIT License.