docs.dev vs Rezmatch.ai

Point your coding agent at your repo and your docs; it opens a docs branch, your team reviews on the rendered page, publishing is a commit. Runs on your Cloudflare, no...

The parse-and-match API for hiring products. Turn résumés and job descriptions into clean JSON and score candidate-role fit with calibrated, explainable results. Résumés...

About docs.dev

Point your coding agent at your repo and your docs; it opens a docs branch, your team reviews on the rendered page, publishing is a commit. Runs on your Cloudflare, no platform fee, no metered AI. Reviews, branches, and rollbacks come free, because it is just git. Your content in their database, and an export button you hope works when you leave. Writing AI is the agent you already have; reader-facing AI runs on your Workers AI.

About Rezmatch.ai

The parse-and-match API for hiring products. Turn résumés and job descriptions into clean JSON and score candidate-role fit with calibrated, explainable results. Résumés are never stored. Calibrated scores that hiring teams can defend, that's the hard part, and it's the part we obsess over. Met and missed requirements with evidence, and hard gates that similarity can't sweet-talk: a missing must-have caps the score, period. Every requirement verdict is grounded in quoted résumé evidence, and automated parity tests verify that name, age and ethnicity signals never move a score.