Hire on the same graph as the rest of your business.

Public job pages, a candidate pipeline, immutable scorecards, and resumes — a local-first applicant tracking system where candidates ARE people in your one directory.

Append-only pipeline

Move a candidate through the pipeline in one honest transaction.

Drag a candidate from Screen to Interview and Excellent closes the old stage row, opens the next, updates status, and writes an activity — all in one transaction. The pipeline is a history, not a status column you overwrite.

application_move · append-only, one txn

One record, every surface

Hire someone and they're already in your directory.

A candidate is a person, a resume is an attachment, an interview note is a note — the same primitives as everywhere else. Dana Ruiz is a candidate here and a lead in Customers because she's one record, not three copies that quietly drift apart.

a candidate IS a person · zero copies

A real audit trail

Submitted scorecards lock — the hiring record can't be edited after the fact.

Structured interview scorecards are editable while you write them and immutable the moment you submit. Once submitted_at is set, the record freezes — so a hiring decision rests on what the interviewer actually said, not on what got tidied up later.

scorecards lock at submitted_at

A clean front door

Public apply pages that keep the pipeline clean on their own.

Post a job to a public page with an apply form. Excellent enforces one application per (job, person), rate-limits public applies to five per IP per hour, and drops bot submissions with a honeypot — so what lands in your pipeline is real, deduplicated, and yours.

one per (job, person) · 5/IP/hr + honeypot

Your ATS isn't a separate database.

A candidate is a person, a resume is an attachment, an interview note is a note — the same primitives as everywhere else. When you hire someone, they're already in your directory.

Bring your whole business home.

Download Excellent and run your whole business on your own machine.