Guide

OpenCATS in 2026: an honest review, and where it leaves a gap

OpenCATS is the best-known free, self-hosted ATS. Here's an honest 2026 review: what it does well, where it stops, whether building your own makes any sense, and how it pairs with a sourcing layer.

OpenCATS is usually the first name that comes up when a recruiter wants an applicant tracking system without a monthly bill. It is free, open-source, self-hosted, and it has been around since the mid-2000s. Two things actually decide whether to use it: is running it in 2026 worth your time, and what does it still not do once it is set up?

This review answers both. What OpenCATS does well, where it stops, whether building your own tracker instead makes any sense now that OpenCATS is already open-source, and how to cover the one gap it cannot close on its own. If you want the full field of free options rather than a deep look at this one, the open-source ATS tools guide compares eight of them side by side.

Data as of June 2026.

What OpenCATS is, and who it fits

OpenCATS is a free, community-maintained applicant tracking system that you host yourself. The project describes itself as an ATS and a recruiting CRM. In practice it is an ATS: it manages the recruiting lifecycle from job order to placement, stores candidates and resumes, moves people through pipeline stages, and logs your notes and activity.

It fits one recruiter well: someone technical enough to run a small web app, who wants a private candidate database they fully own, and whose main need is tracking people they have already found. Solo recruiters and small agencies who have outgrown a spreadsheet but refuse to pay per seat are the core audience. If that is you, OpenCATS does the job for the price of a cheap server.

It does not fit a recruiter who wants software that works out of the box, syncs to a phone, or helps find candidates. More on that below.

Setup and cost, honestly

OpenCATS runs on the classic LAMP stack: Linux, Apache, MySQL, and PHP. You install it on a VPS, and a basic one from DigitalOcean, Hetzner, or Linode runs $5 to $15 a month. A Docker Compose deployment is available and cuts the setup from an afternoon of configuration to closer to an hour for anyone comfortable with containers.

The honest cost is not the hosting. It is the maintenance. You own security patches, database backups, and version updates. Nothing reminds you to do them. For a technically capable recruiter that is an hour here and there. For someone who has never touched a server, that ongoing load is the real price, and it is why a $29-a-month hosted ATS often wins for non-technical solo recruiters despite the sticker difference.

The project is maintained by its community on GitHub rather than a company. Development moves slowly, releases are infrequent, and the interface looks its age. None of that makes it unreliable. Slow and stable is a fair description, not a knock.

What OpenCATS does well

For core candidate tracking, OpenCATS holds up. You can import resumes, parse them into candidate records, create job orders, attach candidates to those orders, move them through stages, and log every call and email as activity. Search across your database is fast. Tagging and saved lists let you segment a pool. For a single recruiter or a small desk running a handful of active searches, this is the whole job, and it is free.

Data ownership is the other genuine win. The database is yours, on your server. No vendor holds your candidate records, no per-seat fee, no risk of a tool getting acquired and sunset. For recruiters who care about controlling candidate data, that is worth real money.

Where OpenCATS stops

The limits are not bugs. They are the edges of what the tool was built to do.

There is no mobile app, so you are at a desktop to use it. There are no native job-board integrations or candidate-facing email sequences, so posting and outreach happen in other tools. The interface is dated and will feel slow to anyone used to a modern SaaS product. And the "recruiting CRM" label oversells the nurturing side: OpenCATS stores relationships, but it does not work them with automated re-engagement or scheduled follow-ups. If candidate nurturing is your real need, the open-source recruiting CRM options cover that gap and where it stays open.

The biggest limit is the one most reviews skip. OpenCATS stores candidates you have already found. It does nothing to help you find them. It has no sourcing, no access to candidate data beyond what you import, and no read on the wider talent market. If the hard part of your week is filling the top of the funnel rather than tracking what is already in it, an ATS is the wrong place to look. The line between the two jobs is worth getting straight, and this breakdown of sourcing versus recruiting does that in two minutes.

Should you build your own ATS instead?

This question comes up a lot, usually from technical recruiters who figure they could just build exactly what they want. Since OpenCATS is already open-source and free, it is worth answering directly.

For a full tracking system, building your own rarely makes sense. Candidate tracking is a solved, commodity problem. OpenCATS, CandidATS, Reqcore, and others already give you pipelines, resume parsing, and reporting for the cost of a server. Rebuilding that from scratch means re-solving problems other people maintain for free, and then carrying all the maintenance yourself with no community behind you. The effort rarely returns more than forking an existing open-source ATS would.

There is one version that does make sense in 2026, and it is not "build an app." It is assembling a lightweight tracker from low-code parts: a structured base in Airtable, Notion, or even a spreadsheet for storage, plus an AI agent to do the work against it. The agent reads your pool against a new role, drafts outreach, and flags who to call, which is the part a static database never did. That pattern is laid out in Claude for recruiters, and for a route that runs entirely on your own machine, the open-source agent OpenClaw can do the same locally.

The trade-off is the familiar one. A low-code plus AI build fits your workflow exactly and you own every piece, but you are the integrator who maintains the seams. For most recruiters, OpenCATS or a hosted ATS is less work than either building from scratch or stitching your own. Build only if your workflow is genuinely unusual or you specifically want to own the whole stack.

Either way, none of these routes, OpenCATS or build-your-own, fills the funnel. They organize candidates. They do not find them.

OpenCATS plus a sourcing layer: the pairing that actually works

The cleanest setup is to stop asking one free tool to do two jobs. Let OpenCATS be your free system of record for tracking, and pair it with a layer that handles the part OpenCATS cannot: finding the right people and knowing who may be open to a move.

That is the role Glozo plays. It surfaces candidates from 30+ sources, reads each one's match to your role, and flags who may be open to a move, a prediction from behavioral signals rather than a self-reported status. You run the search and the market read in Glozo, then keep and track the people you choose to pursue in OpenCATS. Free tracker, real sourcing, and no per-seat bill on either side. For compensation and supply questions before you reach out, Glozo's Market Intelligence gives talent supply and pay by role and geography without a login.

If you would rather not run the search yourself for a role that can simmer, that is also where an agent earns its keep. Before trusting any "AI recruiter" with your pipeline, how to tell a real AI sourcing agent from a chatbot with a wrapper is the screen to run first.

How to choose

Pick OpenCATS if you are comfortable running a small server, you want to own your candidate data outright, and your need is tracking rather than sourcing. Accept the dated interface and the maintenance as the cost of free.

Skip it if you are not technical, in which case a $29-a-month hosted ATS saves you the setup and upkeep. Skip it too if your real bottleneck is finding candidates, because no ATS solves that, and the admin tax of doing sourcing by hand is its own problem, covered in recruiting workflow automation.

And if you are weighing OpenCATS against the rest of the free field rather than just deciding yes or no on this one, the open-source ATS tools guide is the full comparison.

Track for free, source with data

OpenCATS keeps your pipeline. Glozo fills it: candidates from 30+ sources, a read on who may be open to a move, and market pay next to each profile. Start free, no install, no candidate import.

Frequently asked questions

Is OpenCATS still maintained in 2026?
Yes. OpenCATS is maintained by its community on GitHub rather than a company. Development is slow and releases are infrequent, but the project is active and security patches still come out. The core tracking features have held up for years. Treat it as stable and mature rather than fast-moving.
Is OpenCATS really free?
The software is free and open-source, with no license fee and no per-seat cost. What it costs is hosting and time. A basic VPS runs $5 to $15 a month, and you take on setup and ongoing maintenance: security patches, backups, and updates. For a technically capable recruiter the total is roughly $120 to $180 a year in hosting plus your own hours.
Is there a good open-source ATS besides OpenCATS?
Yes. CandidATS is a cleaner-code fork of OpenCATS, Reqcore is a newer ATS on a modern stack with Docker deployment, and Horilla offers recruitment inside a free open-source HR suite. Odoo and ERPNext include recruitment modules if you already run those systems. Each trades off differently on setup effort, interface, and how actively it is developed.
Can OpenCATS find candidates for me?
No. OpenCATS is an applicant tracking system, so it stores and organizes candidates you have already found. It has no sourcing, no access to outside candidate data, and no read on the talent market. Finding candidates is a separate job that needs a sourcing tool or platform alongside the ATS.
Should I build my own ATS instead of using OpenCATS?
For most recruiters, no. Candidate tracking is a commodity that OpenCATS and similar tools already solve for free, so building a full ATS from scratch means re-solving maintained problems and carrying all the upkeep yourself. The version that can make sense is a lightweight build: a low-code base like Airtable or Notion for storage plus an AI agent to do the re-engagement work. Even then it is a project you maintain, and it still does not source candidates.