Inside Arcjet: context before the verdict
A recent model-family launch separates general prompts, coding tools and security-agent content, with documented SDK and cloud boundaries.
Product Hunt records Arcjet AI security models on 9 November 2026; its product page showed day rank #4 and 224 points when checked 10 November. That is a dated popularity signal, not an independent accuracy result.
Documented components, not a complete production inventory.
- Arcjet SDK + WebAssembly
- Documented in-application request analysis; not proof every feature is local
- Arcjet Cloud API
- Documented remote prompt-injection evaluation and decision records
- Himalia / Thebe / Carme
- Named custom model family; specialist models in early access
- Application decision handling
- Developer integrates the returned decision and error path
A new model release from an existing product
Product Hunt shows the model-family launch on 9 November 2026, with #4 and 224 points observed on 10 November. Arcjet’s announcement was first published 5 November, and the platform had previous launches. This study concerns the recent model release; it does not call the company or platform brand new.
Confirmed components and their different roles
Official architecture documentation names an in-application SDK and a Cloud API. The SDK includes WebAssembly for local request analysis where applicable; decisions can also be cached. Those general architecture features do not mean prompt-injection text stays local. FreeStack has not installed the SDK or verified its behaviour in a running application.
Specialisation is a product choice, not a universal guarantee
The announcement names Himalia 1 for general prompt injection, with Thebe 1 for coding agents and Carme 1 for security agents in early access. The provider describes classifier scanning followed by contextual decision review for coding tool results. This is provider documentation, not an independent validation of model accuracy or a disclosed complete training pipeline.
The boundary includes data and error handling
Prompt-injection documentation says text goes to Arcjet Cloud and is stored with decisions by default; disabling text retention requires contacting support. Dry run logs without blocking. Error results need explicit handling in the application; the quick-start pattern denies unchecked requests. A reader must review the chosen integration rather than assume a detector result alone authorises the next action.
Paid access is kept separate from the free toolkit
Current displayed pricing starts at $25 per month for one member and one-hour log retention, with a 15-day trial and usage charges of $5 per million web requests or $50 per million agent requests. No general ongoing-free service allowance was verified, so Arcjet is studied here but not added as a free product.
A smaller learning workflow
The companion guide uses VS Code, LibreOffice and Git to prepare synthetic document cases and an expected-behaviour sheet. These are editorial learning tools, not Arcjet’s production stack. Keep actual results not run until evaluated. Consider a provider only when a named volume, integration, review or retention requirement justifies it.
Sources & further reading
Follow the source for current details. Product Hunt is used for discovery and launch history; technical claims use provider documentation or the project repository.