freehire

Every IT job, straight from the source.

2.9M+ live postings pulled directly from company career pages — no recruiters, no reposts, no dead links. Fully open source.

Try it live → · Sources · API · Add a source · Contributing

Why freehire?

• Straight from the source. Every listing is crawled directly from a company's own ATS — Workday, Greenhouse, Lever, Ashby, iCIMS and a long tail of others — and links to the original posting. No recruiter reposts, no aggregator middlemen, no dead links.
• One schema, deduplicated. The same role posted to three boards collapses into one entry: every posting is normalized into a single shape and deduplicated on a stable key.
• Search that understands jobs. Faceted full-text search over region, work mode, seniority, skills and salary — derived from curated dictionaries, never guessed.
• Actually open. MIT-licensed and self-hostable, pipeline and data both in the open. Adding a company is one line of YAML.
• Yours to build on. A clean HTTP API, a CLI, Telegram digests, and per-user application tracking — use the hosted site, run your own, or build on top.

Aggregating 2.9M+ live postings from 120,000+ companies across 50+ ATS platforms and a long tail of aggregators and direct feeds — see Sources for the full breakdown.

Stack

• Go + Fiber v2 — HTTP server
• PostgreSQL — storage and filtering
• sqlc — type-safe DB access from SQL (no ORM)
• Meilisearch — full-text and faceted job search
• langchaingo — LLM access over any OpenAI-compatible endpoint (no vendor baked in)
• Docker Compose — local development

Quick start

make up        # build + start app, postgres, and meilisearch in Docker
curl localhost:8080/health
curl localhost:8080/api/v1/jobs

Migrations are applied automatically on first Postgres volume init (the migrations/ folder is mounted into /docker-entrypoint-initdb.d). Changing a migration does not re-apply to an existing volume — recreate it with docker compose down -v && make up, or apply pending files manually with make migrate.

If port 8080 is already taken, pick another host port:

HIRE_HOST_PORT=8090 make up

Local development

docker compose up -d db   # database only
make run                  # server on host, reads DATABASE_URL

Copy .env.example to .env and adjust as needed. JWT_SECRET is required for the server to start; OAuth and LLM credentials are optional (the features they gate stay disabled when unset).

Commands

make help      # list all commands
make sqlc      # regenerate code from SQL (via Docker, no local sqlc needed)
make tidy      # go mod tidy
make psql      # psql inside the DB container
make reindex   # rebuild the Meilisearch index from Postgres
make migrate   # apply migrations manually to an existing DB volume

Workers

The server only serves the API. Ingest and enrichment are standalone, run-once workers meant for cron — each crawls or drains its queue and exits.

go run ./cmd/ingest sources/greenhouse.yml  # crawl one board file and upsert jobs (path also via SOURCES_FILE)
go run ./cmd/enrich        # drain the enrichment queue (LLM); needs LLM_* config
go run ./cmd/tg-ingest     # crawl the Telegram channels in sources/telegram.yml
go run ./cmd/tg-extract    # LLM-extract vacancies from crawled Telegram posts
go run ./cmd/reindex       # rebuild the Meilisearch index from Postgres
go run ./cmd/backfill-derive  # re-derive all six dictionary facets on existing jobs (follow with make reindex)

Layout

cmd/                 entry points: server + the standalone workers above
sources/             board files, one per provider (e.g. greenhouse.yml = company + board id),
                     plus a mixed custom.yml and telegram.yml (Telegram channels to crawl)
internal/
  config/            env configuration
  database/          pgxpool connection pool
  db/                generated sqlc code + queries/*.sql
  handler/           HTTP handlers
  auth/              auth primitives (JWT cookie, API keys) + OAuth sign-in
  sources/           ATS source adapters (greenhouse / lever / ashby) + registry
  linksource/        resolves outbound job links found in Telegram posts
  telegram/          Telegram-channel crawl + LLM vacancy extraction
  pipeline/          ingest runner (fetch → normalize → dedup → upsert)
  enrich/            typed AI-enrichment contract + queue-draining runner
  search/            Meilisearch indexing and query
  location/          geography parsed from free-text ATS location strings
  jobview/           the single public wire shape of a job
  normalize/         slug normalization
migrations/          SQL schema (source for both sqlc and initdb)

API

All responses use {"data": ...} (single), {"data": ..., "meta": {...}} (lists), or {"error": msg}. Jobs and companies are addressed by their public slug.

Method	Path	Auth	Description
GET	/health	—	Service and DB status
GET	/api/v1/jobs	—	List jobs (limit/offset)
GET	/api/v1/jobs/search	—	Full-text + faceted search
GET	/api/v1/jobs/:slug	—	Job by slug
GET	/api/v1/companies	—	List companies
GET	/api/v1/companies/:slug	—	Company by slug
POST	/api/v1/jobs/:slug/view	✓	Record a view
POST	/api/v1/jobs/:slug/apply	✓	Mark applied
POST	/api/v1/jobs/:slug/save	✓	Save (bookmark)
DELETE	/api/v1/jobs/:slug/save	✓	Unsave
PATCH	/api/v1/jobs/:slug/track	✓	Set application stage / notes
GET	/api/v1/me/jobs	✓	The caller's tracked/saved jobs
POST	/api/v1/me/api-keys	🍪	Create an API key (returns it once)
GET	/api/v1/me/api-keys	🍪	List API keys
DELETE	/api/v1/me/api-keys/:id	🍪	Revoke an API key
POST	/api/v1/auth/register	—	Register
POST	/api/v1/auth/login	—	Log in
POST	/api/v1/auth/logout	—	Log out
GET	/api/v1/auth/me	✓	The current user
GET	/api/v1/auth/oauth/providers	—	Enabled OAuth providers
GET	/api/v1/auth/oauth/:p/start	—	Begin OAuth sign-in
GET	/api/v1/auth/oauth/:p/callback	—	OAuth callback (sets the session cookie)

Auth legend: ✓ session cookie or API key · 🍪 session cookie only.

Sources

Live catalogue snapshot — 2,935,357 open postings across 120,907 companies (4,052,148 total incl. closed), crawled from 54 ATS platforms plus a long tail of aggregators, job boards, and direct company feeds. Counts are open postings unless noted.

Each ATS platform below is one adapter serving many companies; everything that is not a company's own ATS — third-party aggregators and job boards (mycareersfuture, himalayas, justjoin, jobtech, usajobs, reed, remoteok…), direct single-company feeds (amazon, apple, google, sber, mts, epam…), Telegram, and bulk imports — is collapsed into the final Other row.

Source	Companies	Open jobs
workday	4,057	438,478
oracle	511	330,299
smartrecruiters	2,698	329,376
greenhouse	6,943	204,034
ukg	1	177,272
icims	3,896	164,287
paycom	5,906	132,722
jibe	13	112,483
apploi	2,957	88,980
gupy	1,430	78,880
lever	2,146	71,446
bamboohr	9,303	64,808
ashby	3,618	58,062
jazzhr	3,742	53,267
recruitee	1,741	41,597
phenom	40	39,612
personio	3,981	37,797
paylocity	2,534	31,695
hireology	2,475	29,241
applicantpro	1,922	21,129
isolvedhire	2,161	19,954
zohorecruit	1,076	18,582
pinpoint	608	18,226
teamtailor	1,247	16,766
solides	1,155	15,774
workable	537	15,305
join	4,100	11,921
breezy	805	11,506
eightfold	35	11,176
careerplug	5,579	9,346
inhire	348	8,343
taleo	11	8,315
trakstar	512	7,299
factorial	468	4,838
freshteam	146	3,851
gem	213	2,615
erecruiter	30	2,586
senior	82	2,437
radancy	6	1,647
cornerstone	4	1,068
successfactors	4	973
deel	60	609
wpyoast	1	402
traffit	14	397
avature	1	389
clinch	1	384
comeet	16	268
rippling	17	163
ashbygraphql	3	136
huntflow	19	112
recruitingsolutions	102	43
careerspage	1	24
adp	1	19
vouch	1	11
Other (aggregators, boards, direct feeds, Telegram)	48,370	234,301

Adding a source

Adding a company is one entry in the provider's board file (sources/<provider>.yml, or the mixed sources/custom.yml) — company + board (and provider when an entry overrides the file's). Adding an ATS platform is a new adapter in internal/sources plus one line in sources.All — every adapter speaks the same Source interface, and cmd/ingest validates the file against the registry before any crawl.

For most companies the platform is already supported, so adding them is just one line in the board file. Only when a company runs on an ATS we don't cover yet does it need a new provider (a new adapter). Either way, if you want a source added, start by opening an issue — name the company and its careers URL, and we'll confirm whether it's a one-line add or a new provider before any code.

Frontend

A Svelte SPA lives under web/ and consumes the API (same-origin; a dev Vite proxy forwards /api to the backend).

Contributing

freehire's core is a small pipeline; the extension point is the source (one entry in a sources/ board file, or a new adapter in internal/sources). New contributors: open an issue first — issues and PRs from unapproved accounts are auto-closed by default. See CONTRIBUTING.md for the workflow and AGENT.md for the architecture and conventions. Questions and ideas go in Discussions.

Security

Found a vulnerability? Report it privately — see SECURITY.md. Do not open a public issue for security-sensitive reports.

License

MIT