Hiring

Hiring is a local-first applicant tracking system and candidate CRM, modeled on the way modern recruiting tools work — but running on your machine, against your database.

Candidates are people

The load-bearing idea: a candidate is a person in the shared schema, a resume is an attachment, and a note is a note. There's no separate "candidate" silo — the same person can be a candidate here and a contact in the CRM, on one timeline.

From application to hire

• Public job pages. Each open role gets a public page with an apply form. Submissions are rate-limited and honeypot-protected, and they land straight in your workspace.
• A candidate pipeline. An internal board moves candidates through stages. Each move is atomic and append-only — the old stage closes, the new one opens, status updates, and an activity is written, all in one transaction — so the history is never rewritten.
• Immutable scorecards. Once a scorecard is submitted it's locked, so interview feedback can't be quietly edited after the fact.
• One application per role. A given person can hold only one application against a given job.

In the app, Hiring surfaces under the Human Resources section, but the data — jobs, applications, scorecards — is all yours, in the same local file as everything else.