Frequently asked field notes.
Short answers to the questions teams tend to ask before planting a hiring workflow.
Hiregrove is a static-first applicant tracking interface for small teams. It helps the hiring organization track candidates, organize pipelines, coordinate interviews, publish careers pages, and use structured scorecards.
No. Hiregrove does not make automated hiring decisions or automatically screen out candidates. Structured scorecards are tools to support human discussion and consistent documentation. Automated filtering that discriminates is prohibited.
Yes. Every monthly plan includes a 14-day trial. The checkout flow should show the applicable renewal terms before activation.
This project is designed for Cloudflare Pages. The included pages are static assets; a production integration can connect the front end to your chosen payment or data service.
The public pages are static and can load without a server-rendered backend. Dynamic storage such as the demo basket uses browser localStorage, so it is not a substitute for a production database.
Use a current evergreen browser such as Chrome, Edge, Firefox, or Safari. The interface includes keyboard focus states, semantic controls, responsive layouts, and reduced-motion support.
Sprout supports 2 active jobs and 200 candidates. Sapling supports 10 jobs, 1,000 candidates, scheduling, and a custom domain. Grove supports 30 jobs, unlimited candidates, structured scorecards, reminders, embeds, and 5 seats. Orchard adds unlimited jobs, talent pools, unlimited custom fields, multi-brand pages, and 15 seats.
Yes. In a production billing connection, the billing provider should prorate or schedule the change according to the subscription terms shown at checkout. This static demo does not process a live subscription.
Monthly subscriptions are designed to be cancellable. A live implementation should expose the provider's cancellation flow and effective date clearly.
See the Refund Policy for the governing terms. The static demo does not collect real payment information, so no real refund is processed by these files.
Candidate data belongs to the hiring organization and must be handled under applicable privacy laws, including GDPR where applicable. The hiring organization is responsible for responding to deletion requests and other data-subject rights.
They are shared prompts and fields that help interviewers record evidence consistently. They are not an automated score that decides who advances or gets hired.
Sapling and above describe interview scheduling with calendar sync. The static project presents the interface and plan details; a production deployment needs a supported calendar integration.
Talent pools are available on Orchard. They provide a place for the hiring organization to organize candidates for future human follow-up. They are not an automated candidate-ranking system.
Sprout and Sapling include 1 seat, Grove includes 5 seats, and Orchard includes 15 seats.