Comparison
Heedeo vs Arcjet: an Arcjet alternative for signup abuse.
Arcjet is a developer-first security SDK: bot protection, rate limiting, signup form protection, email validation and a WAF, set up as code in your app, and since September 2026 a runtime security platform for AI agents. Heedeo is narrower and deeper on one problem: who is behind each signup, and whether they have already signed up under other names.
Key takeaways
- Arcjet judges requests: is this a bad bot, is this email valid, is this IP over its limit. Heedeo judges actors: has this browser already opened other accounts.
- A farm with fresh Gmail addresses on a residential VPN passes request checks. It doesn't pass an identity count.
- Arcjet has a free tier and self-serve setup across many frameworks. Heedeo is set up with you on a call.
- They do different jobs and run well side by side.
The short answer. Arcjet is a good fit for request-level protection across many frameworks: block bad bots, rate-limit routes, validate emails, and govern what your own AI agents do. Heedeo fits when the abuse is many accounts from one actor, which request-level checks miss: it recognises the browser behind each signup, counts its identities and gives you a score with reasons.
Heedeo vs Arcjet, side by side
| Heedeo | Arcjet | |
|---|---|---|
| Focus | Who is behind a signup: multi-account and free trial abuse, and agents signing up | Request protection in code, and runtime security for your own AI agents |
| Recognises the browser behind a signup | Yes, and survives cleared cookies by its characteristics | No visitor recognition; rate limits key on IP or an ID you pass |
| Links accounts from one actor | Distinct emails and accounts per browser, linked browsers, email aliases | Not a documented feature |
| Email checks | Disposable, no mail server, domains under 30 days old, aliases, generated-looking bursts | Syntax, mail server and disposable checks |
| Bot protection | Agent and automation findings feed the signup score | Allow or deny 600+ known bots by category; verifies good bots by IP and reverse DNS |
| Web Bot Auth | Verifies signatures and names the operator | Not a documented feature as of October 2026 |
| What comes back | A score with weighted reasons, and your rule's outcome | Allow or deny decisions with reasons, no visitor score |
| Limits | Per account or device, not per IP, through your restrict rules | Fixed and sliding window, token bucket, by IP or any key you pass |
| WAF | No | Yes: Shield WAF |
| Pricing | Pilot pricing on a call | Free 10,000 requests a month; from $25 a month plus $5 per million web requests |
Arcjet details from its public docs, pricing and announcements, checked 27 October 2026. Sources are listed at the end.
One trial farmer, five signups: what each one sees
Someone wants your free trial five times. They use one laptop, a new Gmail address for each signup, and a VPN that gives them a new IP address every time. No disposable domains, no bot, no script: a real browser, typed by hand or by an AI agent.
What Arcjet sees
Arcjet's signup protection checks each signup on its own. Five valid Gmail addresses pass the email checks. A real browser passes bot detection. A rate limit by IP never fires, because the VPN gives each signup a new address. All five trials go through, and each looked fine.
What Heedeo sees
| Signup | Reasons | Score | Your rule |
|---|---|---|---|
| 1st signup | VPN +20 | 20 | allow |
| 2nd signup | 2nd email on this browser +50, VPN +20 | 70 | challenge |
| 3rd signup | 3rd email on this browser +100, VPN +20 | 120 | block |
| 4th signup | 4th email on this browser +150, VPN +20 | 170 | block |
| 5th signup | 5th email on this browser +200, VPN +20 | 220 | block |
Heedeo's default weights. Example rule: challenge at a score of 60, block at 100. The thresholds are yours to set.
Heedeo sees the same browser behind all five, as the table shows: the first gets in, the second is challenged, and from the third your rule blocks.
What is Arcjet, and what does it do well?
Arcjet puts security in your code. Its SDKs cover Next.js, Node.js, Bun, Deno, Python, Go, SvelteKit, Remix, NestJS, Astro, Nuxt and more. A WebAssembly module makes many decisions locally in under a millisecond and calls Arcjet's cloud API for the rest, typically in 20 to 30 milliseconds. It fails open by default.
Its building blocks are broad: bot rules by category from an open list of more than 600 bots, rate limiting by IP, user ID or any characteristic, signup form protection that combines bot checks, email validation and rate limits, a Shield WAF for OWASP-style attacks, and sensitive information detection that runs locally. Since September 2026 it also sells agent runtime security: policies on what your own AI agents may do, prompt injection detection and audit trails.
Heedeo vs Arcjet: the key differences
Arcjet judges requests. Heedeo judges actors. A rate limit per IP stops a script on one address; a farm rotates addresses. A rate limit per user ID stops one account; a farm makes new accounts. Arcjet's signup protection catches bots, disposable emails and bursts, and a fresh Gmail address from a residential IP in a normal browser gets through it.
Heedeo looks for the thing a farm can't easily change: the browser. It counts every distinct email and account that browser has shown you, notices dot and plus aliases of addresses you have already seen, links browsers that share an account or card, and reads the network and velocity around it. Then it gives you a score with reasons. Our guide to free trial abuse explains the pattern in more depth.
- Recognises each browser that reaches a signup or other action, from a script you serve on your own domain. A browser that clears its cookies is usually still recognised by its characteristics.
- Counts the distinct emails and accounts each browser has shown you. Crossing your threshold (3 by default) is a strong reason on its own.
- Relates browsers that share an account, an email, a phone, a card or a home network, so a farm spread across many browsers still adds up to one actor.
- Adds the weights of every reason into a score, and flags the event when it reaches your threshold (100 by default). Every reason comes with one line of plain text.
AI agents: the ones you run versus the ones that arrive
Arcjet's agent product is about agents you run: what tools they may call, and whether a prompt is an injection. Its bot rules can allow or deny AI agents by category and verify well-known bots by IP and reverse DNS. Heedeo's agent work is about agents that arrive at your signup: it verifies Web Bot Auth signatures, names the operator, and judges the signup by what the browser behind it has done.
Pricing: Arcjet vs Heedeo
Arcjet publishes self-serve pricing: a free tier of 10,000 requests a month, and paid plans from $25 a month plus $5 per million web requests.
Heedeo prices on a call. Page loads are free: you pay for the actions you send it, like signups.
Which one to choose
Choose Arcjet if
- You want rate limiting, a WAF and bot rules in code across many frameworks.
- You run your own AI agents and need policy, prompt injection detection and audit.
- You want a free tier and self-serve setup today.
Choose Heedeo if
- Your abuse is one actor opening many accounts: trials, credits, promo codes.
- You need to see who is behind a signup, with a score and reasons, and review it.
- You want to verify agents that sign their requests and let real customers' agents in.
Can you use both?
Arcjet in front of your routes for rate limits, the WAF and bad bots; Heedeo at signup and other valuable actions to catch the actors who pass request checks. One handles traffic, the other identities.
Frequently asked questions
Is Heedeo an Arcjet alternative?
For signup and multi-account abuse, it is the deeper tool. For rate limiting, a WAF and bot rules across many frameworks, Arcjet covers more, and the two can run together.
Can Arcjet detect multiple accounts from one person?
Arcjet's documented features are request-level: bot detection, email validation and rate limits by IP or an ID you pass. It does not document recognising one browser across accounts. Heedeo does that and counts the identities.
Does Arcjet verify Web Bot Auth?
As of October 2026 its docs verify well-known bots by IP and reverse DNS, and do not list Web Bot Auth signature verification. Heedeo verifies Web Bot Auth signatures.
Is Arcjet free?
Arcjet has a free tier of 10,000 requests a month. Paid plans start at $25 a month plus usage.
See it on your signups.
Heedeo is ready. Book a 30 minute demo, and we set it up for your site with you.
How we compared
We build Heedeo, so we are not neutral. To keep this fair we read Arcjet's own docs, pricing and announcements on 27 October 2026, link every claim about it below, and say what it does well before where we differ. Heedeo's claims match its current product. Spotted something out of date? Tell us and we'll fix it.
Arjan Chaudhary, Founder, Heedeo. Arjan builds Heedeo. He is a security researcher who has reported vulnerabilities to Google, EA and xAI.
Sources
- Arcjet
- Arcjet docs
- Arcjet docs: bot protection concepts
- Arcjet docs: rate limiting configuration
- Arcjet docs: signup protection
- Arcjet docs: architecture
- Arcjet pricing
- Help Net Security: Arcjet agent runtime security (Sep 2026)
Arcjet is a trademark of its owner; this page is not affiliated with or endorsed by it.