HomeAll ToolsCompare CategoriesFind My Tool Submit Your Tool →
Coding Freemium Free Tier

Arcjet

Secure AI agents at runtime: block prompt injection, authorize tool calls, and control spend before abuse hits production.
★★★★✦ 4.4 Human verified
Last updated: September 2026 · Free trial available

What is Arcjet?

Arcjet is a runtime security platform that ships inside the AI code you are already writing. Where traditional WAFs sit at the edge, Arcjet sits next to agent tool calls: detect prompt injection, authorize what an agent is allowed to do, redact sensitive data, and throttle bots or spend before a model-driven action hits production. The pitch after its strong Product Hunt launch around 21 September 2026 is simple — observe, enforce, audit.

Developers wrap tools with guard() (or SDK rules), map trusted application context as inputs, and get an ALLOW or DENY decision before email, refunds, database writes or web fetches execute. Security teams can define versioned remote policies (including Rego / OPA-style rules) by label without redeploying app code, while local detectors cover PII that should never leave the process. It also covers classic request protection alongside agent-specific guards.

Editor score ~4.4/5 in Coding. Pricing starts with a free trial, then roughly $25/month and a higher ~$299/month tier (confirm live numbers). Choose Arcjet if you are putting agents into production with consequential tools; skip it if you only run read-only chatbots with no side effects.

Best for:
  • Teams shipping AI agents that call tools, email or APIs in production
  • Security and platform engineers who need deterministic guardrails
  • Developers who want prompt-injection and PII controls inside the app
Not ideal for:
  • Teams that only need a chat UI with no tool-calling agents
  • Organisations unwilling to put enforcement points in application code

Pricing Plans

PlanPriceWhat's Included
Trial$015-day free trial — confirm on arcjet.com
Business~$299/monthHigher limits for production apps — check site for details

Pros & Cons

✓ Pros

  • ✓ Runtime guards before tool calls, not after the damage
  • ✓ Prompt injection, PII redaction, bot and spend controls in one SDK
  • ✓ Remote Rego policies security teams can change without redeploying

✕ Cons

  • ✕ You must instrument agents — it is not a passive network appliance
  • ✕ Policy design (Rego / remote guards) needs security ownership
  • ✕ Paid plans after the trial for serious production traffic

Ratings Breakdown

Ease of Use
4.2
Value for Money
4.4
Features
4.6
Support
4.3
This page contains affiliate links. If you sign up through our link, we may earn a small commission at no extra cost to you. This helps us keep the directory free for everyone.

Human-verified · How we score →