// open startup
All our numbers, live.
freehire is an open, free search engine for jobs — so our metrics are open too. Every figure below is pulled live from the same public API anyone (or any AI agent) can query. No dashboards behind a login, no vanity rounding.
// the catalogue
// daily movement
/stats/jobs-activity ↗Jobs added vs. removed
New vacancies crawled in versus postings we detected as closed, per day.
// members
/stats/user-growth ↗21,176 people on freehire
Cumulative registered members over time. Early days — and that's the point of showing it.
New members per day
Same series, not cumulative — how many people signed up on each day.
// engagement
/stats/engagement ↗What people do here
Job pages opened by every visitor, signed in or not, and bot-filtered — counted only from the day we started filtering, which is why that one carries a date. Then the signed-in interactions on top, all-time: postings tracked, CVs written and tailored to a vacancy, people who turned on job alerts, and inboxes wired up for application mail.
- job views, all visitorssince Sep 4, 2026
- 28.6M
- jobs saved
- 9,399
- applications
- 13,066
- saved searches
- 4,219
- CVs uploaded
- 16,435
- CVs tailored
- 1,686
- people with job alerts on
- 2,313
- inboxes connected
- 102
// what's inside
/stats/facets ↗Top countries
Top skills
Seniority
Work mode20% remote
// open source
github.com/strelov1/freehire ↗The whole pipeline is open source. Missing a job source you use? Adding it is usually one small adapter — a PR is very welcome.
// about these numbers
- Where do these numbers come from?
- Straight from freehire's own public API at request time — the same endpoints anyone can call — plus the GitHub REST API for the repository stats. Each number links to the endpoint behind it, so you can check it rather than trust it.
- How fresh are they?
- Catalogue scale, daily movement, member growth and engagement are read live, then held about a minute on the server and five in your browser. Repository stats refresh hourly, because unauthenticated GitHub calls are capped at 60 per hour. The distribution breakdowns come from a daily rollup, so they lag by up to a day.
- Do the engagement counts expose anyone?
- No. Each one is a single integer total, and the queries behind them select no user id, email or individual row. "Inboxes connected" counts live Gmail grants plus claimed freehire addresses — never a message.
- Can I query the same data myself?
- Yes, and without an account. Job search, company data and facets are public reads; only personal features such as saving and tracking need a key. Every endpoint is documented, with an OpenAPI schema published for clients and AI agents.
- What counts as an open job?
- A posting freehire has crawled and has not yet detected as closed. Roles are never silently deleted: when a vacancy stops appearing on its source board it is marked closed and leaves the open count, which is what the "removed" bars above track. That count is not de-duplicated — the same role reposted across several boards counts once per posting — which is why it reads higher than the number of unique jobs you can actually browse.
- Why publish all of this?
- freehire is free and open source, so the numbers behind its claims should be checkable rather than asserted. Any figure quoted elsewhere on the site — or by an AI assistant citing freehire — should reconcile with this page, the live source rather than a rounded snapshot.