LockLLM
Scans prompts for jailbreaks, injection attacks, and sensitive data before sending to AI models.
≈ 18visits/mo
Emerging · estimate, read 2026-09-19
- For
- Teams building AI applications who need to secure and optimize LLM usage costs.
- Price
- Free plan · From $0.00 per usepricing page, read 2026-09-20
- Activity
- Actively maintainednothing dated on the site
- Company
- founding year not on record
- Runs as
- API
- Detect prompt injection attacks and jailbreak attempts automatically
- Route requests to optimal AI models to reduce inference costs
- Compress prompts to lower token usage and API expenses
- #143
Mindgard
Discovers, red-teams, and protects AI agents and systems against security vulnerabilities and attacks.
1.2kMaintained— - #392
Struct
Monitors production changes, triages alerts, and automatically fixes issues with pull requests.
23ActiveFrom $200/mo - #432
Cloudback MCP Server
Backs up GitHub, GitLab, Azure DevOps, and Linear repositories with customer-managed encryption and fast recovery.
114not readFrom $10/mo - #627
Scout AI
Analyzes web applications for performance, security, SEO, and accessibility issues with real-time reports.
20Maintained— - #659
Safeguard
Finds and fixes software vulnerabilities and zero days autonomously across dependencies and containers.
1.2kMaintainedFrom $9/mo2025 - #924
AI Modularity
Verifies autonomous agent behavior before deployment, authorizes payloads at execution, and measures economic value after execution.
1Active—
What is LockLLM?
Scans prompts for jailbreaks, injection attacks, and sensitive data before sending to AI models.
Who is LockLLM for?
Teams building AI applications who need to secure and optimize LLM usage costs.
How much does LockLLM cost?
LockLLM has a free plan; paid plans start at $0.00 per use, per its pricing page on 2026-09-20.
Do people use LockLLM?
Emerging: ≈ 18 visits a month · estimate, 2026-09.
Is LockLLM still maintained?
Actively maintained.
What are alternatives to LockLLM?
In Developer tools, by use: Mindgard, Struct, Cloudback MCP Server, Scout AI, Safeguard, AI Modularity.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one row at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.