Arcjet
UNCLAIMEDGUARDRAILS AND FILTERINGCOMPLIANCE AND GOVERNANCEPRIVACY AND PII
Arcjet — Runtime security for AI apps and agents: prompt injection detection, tool-call authorization, sensitive-data redaction, bot protection, and rate limiting. Drop it into your JS/TS code. Listed under Guardrails and filtering in the Security / Governance layer. 3 of 16 comparison attributes are recorded, each with the page it was read from.
Arcjet is the AI agent runtime security platform. Discover the agents running in your organization, enforce policy across every action, prompt, and tool call, and keep the evidence to prove what happened. Detect prompt injection, authorize agent tool calls, redact PII, and block bots and abuse.
4 OF 4 SIGNALS HELD
What it runs on, and what runs on it
0 cited edgesComputed from the stack graph, both directions. Every cited edge links the page it was read from; a vendor-added one links the vendor’s own source — this is the reason to be here rather than on the vendor’s own site.
No edges on record for Arcjet.
Nothing in the directory documents depending on it, and its own docs do not name what it runs on. An edge is only stored when a source states it.
Submit a documented integration →From Arcjet? No claim is needed for this: a link to your docs that names what Arcjet runs on is enough.
Open-source signals
A HOLLOW RING IS UNMEASURED, NOT ZERO · WE DO NOT SUBSTITUTE A PARENT COMPANY’S REPOSITORY FOR A PRODUCT THAT HAS NONE
Price
We hold no price for this product.
This is open-source software: you can run it yourself and the licence costs nothing. If the project also sells a hosted service, we do not yet hold the page it prices it on. If that changes — or if you publish /.well-known/pricing.json — it appears here with a capture date.
How we read prices →What its categories ask
3 answered · 13 unanswered16 questions declared by Guardrails and filtering and Compliance and governance and Privacy and PII. Most rows across the directory read like these.
“Checks: prompt injection, sensitive info, bot signals, action policy, run history.”2026-09-29
“agent/support.ts 1 const arcjet = launchArcjet ( { 2 key : process . env . ARCJET_KEY ! , 3 } ) ; 4 // rampart() detects on device: 5 // names, addresses, IDs, banking 6 const pii = 7 localDetectSensitiveInfo ( { 8 backend : rampart () , 9 } ) ; 10 11 // Screen the record before it 12 // becomes con”2026-10-20
A ROW WITH NO ANSWER IS NOT A ROW WITH A “NO” · A VENDOR MAY ANSWER A BLANK ONE, MARKED VENDOR CLAIMED WITH ITS SOURCE · A DOCUMENTED VALUE IS DISPUTED, NOT OVERWRITTEN, AND STAYS VISIBLE WHILE WE RE-READ THE SOURCE
Practitioner reviews
Nobody has written one yet.
A review here is structured, not a star: hardware, scale band, what broke in production, and whether you would choose it again.
NO PERCENTAGE IS SHOWN UNDER FIVE REVIEWS · NO STAR RATINGS, EVER
Also in this category
38 products in Guardrails and filtering. Comparison defaults to within the category — pairing this with a GPU cloud would produce a page that means nothing.
USED BY = LISTED PRODUCTS DEPENDING ON IT, IN THIS DIRECTORY
Frequently asked
Is Arcjet open source?
What does a blank mean on the Arcjet page?
Where do the Arcjet figures come from?
Can Arcjet change what this page says?
Something here is wrong — how do I fix it?
Is this listing run by Arcjet?
Cite this page
A model that quotes us should quote us correctly. The reading and its date sit inside the citation rather than beside it, because a quotation carrying only a URL goes wrong the week the URL changes.
infratoapp, “Arcjet — Guardrails and filtering”, read 29 September 2026. Checks: prompt injection, sensitive info, bot signals, action policy, run history as published at arcjet.com. https://www.infratoapp.com/products/arcjet-js
What Arcjet can and cannot change here
Claiming the organisation lets its admins and editors change the tagline, description, logo, docs link and deployment model of every product that org owns — live, labelled as theirs, and logged. Answers to blank questions and dependencies go live too, marked as the owner’s and sourced; a documented answer cannot be overwritten. Everything else on this page is a stated fact with a dispute route: price, licence and OSS figures. Those columns are ungranted at the database level, so they are not a feature we withheld — they are a write that cannot happen. Name, category, website, pricing page and package names can be changed by the owner only through our review. A dispute never deletes a value; it marks it and publishes the correction.