Open source job board software: 4 real options and what they cost to run

Open-source job board software is free to license and never free to run. The code is on GitHub; the hosting, the maintenance, and the listings are on you. That trade is worth it when you want full control and have the engineering hours to spend - and a bad deal when you just wanted a board live this week. Here are the options that are actually maintained, grouped by stack, plus the running costs that never make it onto a pricing page.

1. WP Job Manager - the maintained default

On WordPress, this is the one real product: an actively maintained, open-source plugin with a deep add-on ecosystem, and a non-developer can stand it up. The base plugin is genuinely free. The pieces you will actually want - applications, resume management, paid listings, alerts - are premium add-ons, and you still pay for WordPress hosting. Best when you value a proven ecosystem over a clean codebase.

2. WordPress plus a custom theme

A step further: WP Job Manager or a listings plugin under a theme you control. You trade code cleanliness for speed and a plugin for almost any feature you can name. The ceiling is WordPress itself - fine for a content-and-listings board, frustrating if you need bespoke product behavior.

3. Roll your own: Django, Rails, Laravel, or Next.js

Outside WordPress, most “open-source job boards” are starter repos, not maintained products. Forking one is a legitimate head start - you inherit the schema, auth, and CRUD - but be honest about what it saves. It saves the boring 20%. The hard 80%, keeping listings fresh and deduplicated, is not in any starter repo. Pick the framework your team already knows; the language matters far less than the data pipeline you bolt on next.

4. The cost open source does not remove

Whichever you choose, the board ships empty and the recurring bill is real:

Licensing: $0. This is the part everyone quotes.

Hosting and maintenance: ongoing. Servers, upgrades, security patches, and your own time when an add-on breaks.

Listings: the real cost. Direct employer posts start at zero and stay near zero until you have traffic. Scraping means you run and repair proxies, parsers, and dedup - see our scraper comparison. An aggregation API returns normalized postings from many sources without the pipeline, which is usually cheaper than one engineer’s time maintaining scrapers - the aggregator guide lays out the math.

Open source is the right call when control is worth the operations burden. If it is not, a hosted platform or a full custom build may fit better. Either way, the listings still have to come from somewhere.