Jobify

A self-hosted tracker for your job applications.

Jobify keeps your whole job search in one place: the postings you are interested in, where each application stands, upcoming interviews and follow-ups, and your notes. It runs as a single Docker container with an embedded SQLite database, so there is nothing else to set up.

Features

• Track everything that matters. Title, company, location, remote/hybrid/on-site, employment type, salary range, source, contact, tags, notes, an interest rating and the full description.
• Status pipeline. Saved → Applied → Screening → Interviewing → Offer → Accepted, plus Rejected, Withdrawn and Ghosted. Every status change is recorded on the job's timeline automatically.
• List, board and timeline views. Search, filter and sort a table of jobs, drag cards between columns on a full-width Kanban board, or chart your search: a Gantt-style timeline of every application coloured by status with interviews marked, and a flow (Sankey) diagram of how applications moved between statuses. Both can be saved as PNG or SVG.
• Timeline. Log interviews, notes and follow-ups against each job. Upcoming interviews, follow-up dates and deadlines show up on the dashboard.
• Dashboard. Active applications, response rate, offers, your pipeline at a glance and applications per week.
• Import from job sites. Paste a link and Jobify fills in the form. Dedicated importers for LinkedIn, Workday, Greenhouse, Lever, Ashby, SmartRecruiters, Workable, Rippling and Oracle career sites, plus generic importers that read the structured data, embedded job data and page content that most other career pages have. Pages pasted from Indeed, Glassdoor and other sites that block automated access are recognised too, and plain text works as well.
• Optional AI assistant. Connect Anthropic (Claude), OpenAI, Google Gemini, a local Ollama model or any OpenAI-compatible API to summarize postings, tidy up descriptions, draft cover letters, prepare for interviews and extract job details from any page.
• Your data, portable. Export everything as JSON (and import it again) or as a CSV spreadsheet.
• Multiple users. Everyone gets their own private jobs, timeline and profile. Admins add people or open sign-up, and manage the shared AI provider.
• A dark mode, and a layout that works on phones.

Quick start

Docker Compose

services:
  jobify:
    image: ghcr.io/esg450/jobify:latest
    container_name: jobify
    restart: unless-stopped
    ports:
      - '3000:3000'
    volumes:
      - ./data:/data
    environment:
      PUID: 1000
      PGID: 1000

docker compose up -d

Then open http://localhost:3000. The first person to open Jobify creates the admin account.

Docker

docker run -d --name jobify \
  -p 3000:3000 \
  -v /path/to/jobify-data:/data \
  -e PUID=1000 -e PGID=1000 \
  ghcr.io/esg450/jobify:latest

Unraid

A template is included at unraid/jobify.xml. Copy it to /boot/config/plugins/dockerMan/templates-user/ on your server, then choose Add Container in the Docker tab and pick Jobify from the template list. Data is stored in /mnt/user/appdata/jobify and the container runs as 99:100 (nobody:users) by default.

Build from source

git clone https://github.com/esg450/jobify.git
cd jobify
docker build -t jobify .

Updating

Images are published to the GitHub Container Registry for amd64 and arm64:

On Unraid, new releases appear as update ready in the Docker tab; click it to update. With Compose, run docker compose pull && docker compose up -d. Your data is kept across updates and database migrations run automatically. The running version is shown on the Settings page.

Configuration

All settings are optional environment variables.

AI settings can also be managed from the Settings page; settings saved there take precedence over the environment variables.

AI providers

Add your resume and what you are looking for under Settings → Your profile to get cover letters and interview prep tailored to you. Job details and your profile are sent to the provider you choose, and nowhere else.

Importing jobs

Paste a posting URL on the Add job page. Jobify tries the importer for that site first, then works through the fallbacks: the schema.org JobPosting data most career sites publish, the markup of well-known job sites, job data embedded in the page's scripts, and finally the page's title and the block of text that reads most like a description. Whatever was found, a last pass reads the salary, location, remote/hybrid and employment type out of the text. Company careers pages that embed their postings from Ashby, Greenhouse, Lever or Workday are followed to the real posting. You always get to review the result before saving.

Some sites block automated requests or require you to sign in (Indeed, Glassdoor and LinkedIn when signed in, for example). In that case switch to Paste and paste the page source (right click → View Page Source → Select all → Copy, or from the browser's developer tools) or just the posting text. A copied posting usually comes through with its title, company, location and salary; with an AI provider configured, Jobify can fill in anything that is still missing.

Want to support another site? Importers are small, self-contained classes; see CONTRIBUTING.md.

Users and accounts

The first person to open a new Jobify creates the admin account. After that, admins can add people under Settings → Users, or turn on sign-up so people can create their own accounts. Each user's jobs, timeline and profile are private to them. The AI provider is shared and only admins can change it.

Upgrading from a version without accounts? Your jobs are kept. On first launch, Jobify asks you to create the admin account and moves your existing jobs and profile into it. If you had set JOBIFY_PASSWORD, you'll need to enter it on that screen; this stops someone else from claiming your data first. You can remove the variable afterwards.

Forgot a password? Admins can set a new one for any user under Settings → Users. If you are locked out of the only admin account, reset it from the server:

docker exec jobify node apps/server/dist/cli.js list-users
docker exec jobify node apps/server/dist/cli.js reset-password <username>

Security

• If Jobify is reachable from outside your home network, put it behind a reverse proxy with HTTPS and leave sign-up turned off unless you need it.
• On a brand-new instance, create the admin account straight away: until you do, whoever opens Jobify first becomes the admin.
• The server fetches the URLs you import. Anyone with an account can make it request web pages.
• Passwords are hashed with scrypt, sessions are stored as hashes, and sign-in attempts are rate-limited. API keys are stored in the database in your data directory and are never sent to the browser.

Logs and troubleshooting

Jobify writes its log to logs/jobify.log in the data directory (on Unraid, /mnt/user/appdata/jobify/logs/), alongside the container's console output. Server errors, failed requests and errors from people's browsers all end up there. Admins can also download it under Settings → System. Set LOG_LEVEL=debug to record every request while you track down a problem. Log files roll over at 5 MB, and the three most recent old files are kept.

Backups

Everything lives in jobify.db in the data directory, so back up that directory to back up every user. Each user can also download their own jobs as JSON or CSV under Settings → Your data.

Development

Requirements: Node.js 24 and npm.

npm install
npm run dev        # API on :3000 and the web app on http://localhost:5173

The stack is NestJS with Drizzle ORM on SQLite for the API, and React with Vite, TanStack Query and Tailwind CSS for the web app. See CONTRIBUTING.md for how the code is organised.

License

Jobify is free software released under the GNU Affero General Public License v3.0. You can use, self-host, modify and share it. If you distribute a modified version, or run one as a service for other people, you must make your source code available under the same license.