Will this add friction for real candidates?

No. A clean applicant sees nothing, and there is no captcha. Only a borderline signup or application gets a code by SMS or email, and you set that threshold by rule. The apply flow stays one step for everyone else.

Our fake applicants are people with real resumes, not bots.

Most are. A generated resume, a real inbox and a rented phone number all pass a form, and a person filling it in by hand sets off no bot check. Reuse gives them away. Rupt links profiles by the device they come from, so a new name and a new email do not make a new person.

Can it catch fake employers posting scam jobs?

Yes. Rupt reads postings and messages for intent, so an ad written to collect identity documents or an application fee is held. The device, email and network behind the employer account are linked to every other account the same operator runs.

We already run identity verification and background checks.

Keep them. They run on the candidates who reach an offer, the expensive end of the funnel. Rupt runs at signup and apply, before a recruiter spends a minute, and the rest of your pipeline sees fewer of the wrong people.

Does Rupt reject candidates on its own?

Only when you tell it to. With no policy written, every verdict is allow and you only observe. When you enforce, you choose allow, challenge, deny or suspend per rule, and every verdict comes with the checks and linked accounts behind it. Your recruiters and trust team keep the decision.

Can it catch nation-state remote worker schemes?

It surfaces the signals those schemes leave on your platform: many profiles from one device, even across fresh browser profiles, repeated VPN, proxy and datacenter use, and logins that jump between countries faster than a person can travel. Rupt flags the cluster for review, and the AI agent can investigate it. Deciding who a person is takes identity verification and a human, so treat Rupt as evidence for that review, not a verdict on the applicant.

We run a job board. Is this different from the marketplaces page?

Job boards are marketplaces, so both apply. This page covers candidate fraud in detail. The marketplaces page covers fake leads, scam listings and pro seat sharing, on the same integration.

Plans start at $99 a month with 20,000 evaluations included, then $0.005 per evaluation. An evaluation is one check at signup, login or application, so cost follows the actions you check rather than your candidate database.

Candidate fraud detection for job boards and ATS

Fake applicants

Detect fake applicants and linked profiles.

Link signups and applications by multiple signals, not just email or IP.
Catch disposable emails, VoIP numbers and numbers already used on other accounts.
Survives cleared cookies, incognito, new browser profiles, new numbers and VPNs.

On a marketplace we protect, one person made thousands of fake leads by hand with no bot signals: 19 identities shared one browser, 18 shared one IP, 6 shared one throwaway number. The same reuse is what links one operator's applications, whatever name is on each.

Read the breakdown

Stop apply bots, and choose which agents to allow.

Classify every apply session as human, declared agent or undeclared automation.
Catch headless browsers, automation frameworks and direct API submissions before they reach a recruiter.
No captcha and no extra steps for real candidates.

Rupt takes a session apart down to the browser engine, the automation driver, the network and the timing between inputs. An auto-apply agent has to get every one right to pass as a person, and you choose whether declared agents may apply at all.

Read the guide

Stop spam, scams and phishing on your platform.

Catch phishing links, application fee demands and identity document harvesting in job posts and recruiter messages.
Link each detection to the device, email and network behind the employer account.
Hold, review or take down the whole ring at once instead of one account at a time.

A property marketplace cut scam reports by around 90% and removed about 70 linked accounts in a single action. The same engine reads job postings and recruiter messages.

Read the story