Starter
Start hereGood for a small engineering team running its first debugging assessment.
- 5 candidate starts per 30-day period
- 1 active assessment at a time
- 1 hiring-team member
Buglyst Hiring pricing
Choose an assessment allowance, create your workspace, and start inviting candidates. Drafting is free; you pay when you are ready to invite.
Plan for one 30-day period. Count candidate starts, not annual hires. Team members include the workspace owner and reviewers.
Starter fits these limits at ₹4,999 for 30 days.
Includes 5 candidate starts, 1 team member and 1 live assessment. This is the lowest-priced plan that fits these three limits. Compare features below.
Review StarterUnused starts do not roll over. An invite reserves one start until it is revoked or the candidate begins. A new payment starts a fresh period and allowance; it does not top up the current one.
Good for a small engineering team running its first debugging assessment.
For a team hiring for a couple of roles with reviewers sharing the work.
For an engineering org running assessments across many roles in the same month.
For high-volume hiring or a repository-informed library-selection pilot that needs review.
Recommendation is based on who each plan is sized for, not on sales volume. Buglyst Hiring is in beta.
| Assessment | |
|---|---|
| Access period | 30 days, one payment |
| Candidate startsA candidate counts once they start the assessment. | 5 |
| Active assessments at a time | 1 |
| Verified Buglyst library | Included |
| Time limit and AI policy per assessment | Included |
| Custom generation from requirementsBeta. Drafts need technical review before use. | — |
| Evidence | |
| Candidate evidence report | Included |
| Deterministic visible and private checks | Included |
| Integrity signals (repeated-patch, exposure) | Included |
| Reports readable after the period ends | Included |
| Candidate workflow | |
| Private, expiring invite links | Included |
| Consent screen before recording | Included |
| Browser workspace, no local setup | Included |
| Team | |
| Hiring-team members | 1 |
| Reviewer and admin roles | — |
| Exports | |
| Print or save report as PDF | Included |
| CSV export of results | — |
| Integrations | |
| Repository-informed GitHub pilotApproved repository structure selects Buglyst library exercises; candidates do not execute connected repository code. | — |
| Support | |
| Support | |
| Purchase | Self-serve checkout |
| Feature | Starter | Growth | Scale | Business |
|---|---|---|---|---|
| Assessment | ||||
| Access period | 30 days, one payment | 30 days, one payment | 30 days, one payment | 30 days, one payment |
| Candidate startsA candidate counts once they start the assessment. | 5 | 20 | 60 | 200 |
| Active assessments at a time | 1 | 5 | 25 | 100 |
| Verified Buglyst library | Included | Included | Included | Included |
| Time limit and AI policy per assessment | Included | Included | Included | Included |
| Custom generation from requirementsBeta. Drafts need technical review before use. | — | 1 per period, Beta | 5 per period, Beta | 15 per period, Beta |
| Evidence | ||||
| Candidate evidence report | Included | Included | Included | Included |
| Deterministic visible and private checks | Included | Included | Included | Included |
| Integrity signals (repeated-patch, exposure) | Included | Included | Included | Included |
| Reports readable after the period ends | Included | Included | Included | Included |
| Candidate workflow | ||||
| Private, expiring invite links | Included | Included | Included | Included |
| Consent screen before recording | Included | Included | Included | Included |
| Browser workspace, no local setup | Included | Included | Included | Included |
| Team | ||||
| Hiring-team members | 1 | 3 | 10 | 25 |
| Reviewer and admin roles | — | Included | Included | Included |
| Exports | ||||
| Print or save report as PDF | Included | Included | Included | Included |
| CSV export of results | — | Included | Included | Included |
| Integrations | ||||
| Repository-informed GitHub pilotApproved repository structure selects Buglyst library exercises; candidates do not execute connected repository code. | — | — | — | Approved pilot |
| Support | ||||
| Support | Priority email | |||
| Purchase | Self-serve checkout | Self-serve checkout | Self-serve checkout | Arranged with Buglyst |
Every figure on this page comes from the same plan configuration the server uses to grant access.
No. One payment buys 30 days of Hiring access. It does not renew automatically and nothing is charged later. A new payment starts a fresh period and allowance.
Your workspace, assessments, and reports stay. Publishing assessments, new candidate invites, new candidate starts, and CSV exports pause until you buy another period.
A candidate who already started before the period ended can still finish and submit.
Yes. Reports stay readable to your workspace members after the access period ends. Unused candidate starts do not roll over.
One candidate start. Creating an invite reserves a start from your allowance; revoking an invite nobody has started releases it again. The start is used when the candidate accepts the consent screen and begins.
Reviewer seats are not charged per person; each plan lists how many hiring-team members it includes.
You choose per assessment. With AI allowed, the Buglyst assistant is available and its requests are recorded. Candidates who report using AI must consent to share an AI-use disclosure before submitting on AI-allowed assessments. With AI not allowed, the Buglyst assistant is switched off for the attempt. Assistant requests and candidate disclosures provide context on the report; AI use is never a score.
You assemble an assessment from up to three verified library items and set the title, candidate instructions, time limit, AI policy, availability window, and attempt limit.
Generating a draft from your written requirements is included on Growth, Scale, and Business (Beta, eligibility required). Drafts need technical review, and Buglyst does not publish unverified generated challenges.
With Business eligibility and Buglyst approval, approved repository structure helps select verified Buglyst library exercises. Candidates do not receive or execute the connected repository. The exact repository, commit, and paths need approval; only personal GitHub installations are supported in this pilot.
Uploaded company projects are a separate controlled pilot. Candidate runs require runner readiness and a reviewed immutable release; production company execution is not yet verified.
Standard library checks run in the configured managed sandbox, currently E2B in production, with time and output limits. Uploaded company projects use a separate Docker runner; production company execution is not yet verified and remains a controlled pilot. Private checks stay server-side.
No. Buglyst records evidence and runs deterministic checks. It does not rank, reject, or advance anyone. Hiring decisions remain with your reviewers.
Cashfree issues a payment receipt. If your company needs invoice details or other procurement paperwork before purchase, contact Buglyst first so we can confirm what can be arranged. If you have already purchased and need company details on an invoice, contact Buglyst with the order reference from your billing page.
Checkout is in Indian Rupees through Cashfree and is set up for Indian payment methods. Buglyst does not promise that every international card will work. If you are paying from outside India, talk to Buglyst first.
Repository-informed library selection and uploaded company projects have separate pilot scopes. For security reviews, procurement, larger volumes, or payment questions, talk to Buglyst.