AI · alternatives · 2026
24 alternatives to Custosa
Permission and compliance layer for Enterprise AI
Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes.
- 1
Fine-Grained Permissions for AI-Powered Applications
2025 · permit.io · its alternatives →
- 2
- 3
We needed something like --dangerously-skip-permissions that doesn’t nuke your untracked files, exfiltrate your keys, or install malware. Claude Code's permission system is allow-or-deny per tool, but that doesn’t really scale. Deleting some files is fine sometimes. And git checkout is sometimes not fine. Even when you curate permissions, 200 IQ Opus can find a way around it. Maintaining a deny list is a fool's errand. nah is a PreToolUse hook that classifies every tool call by what it actually does, using a deterministic classifier that runs in milliseconds. It maps commands to action types…
Mar 2026 · github.com · its alternatives →
- 4
- 5
Deep Work Plan▲114Models matter. Context matters more. Give your agent a plan.
Jun 2026 · deepworkplan.com · its alternatives →
- 6
1Security▲21AI-ready permission visibility for Microsoft 365
2025 · 1security.ai · its alternatives →
- 7
The modern standard in AML compliance through AI agents
2023 · flagright.com · its alternatives →
- 8
Flagright AI▲103Supercharge your AML compliance ops with Flagright AI & GPT
2023 · flagright.com · its alternatives →
- 9
Cyris▲98"Cyris is the orchestration layer your AI agents are missing. Whether you're a two-person startup or a 10,000-employee health system — connect agents from OpenClaw, Claude, GPT-4o, Ollama, EPIC, or any platform and have them coordinate, hand off, and escalate across your entire organization. Self-hosted. Auditable. Human-governed" Just a side project I've been working on, and was curious whether people would actually find something like this useful! I'd recommend checking out the sandbox as well.
Apr 2026 · cyrisai.dev · its alternatives →
- 10
AI Hive ▲53Build, deploy, and run all your AI agents in one platform.
May 2026 · app.aihive.global · its alternatives →
- 11
Hey HN, I’m Austin, founder of Salestrics (salestrics.com). The Problem: > Most AI agents today are trapped in chat windows. While models are smart enough to run complex multi-step workflows, giving them production access to business context (CRM, support, billing) usually means managing unsafe local API keys or hacking together fragile point-solution scripts. What We Built: We built Salestrics to serve as both an all-in-one revenue workspace (CRM, service desk, billing, docs, email) and a production-grade Model Context Protocol (MCP) execution proxy. How It Works: Unified Context: Instead…
Aug 2026 · salestrics.com · its alternatives →
- 12
Your agent team, on your machine. Open-source harness for multi-user Claude agents. - yaodub/cast
Jun 2026 · github.com · its alternatives →
- 13
Stop AI agents from doing things they shouldn't.
Aug 2026 · sanjaynandanj.github.io · its alternatives →
- 14
MCP Guardian▲12You can read more about EQTY Lab's enterprise-focused usage of this tooling here: https://www.eqtylab.io/blog/securing-model-context-protocol
Dec 2025 · guardianmcp.dev · its alternatives →
- 15
Discover secure AI from Bastio AI Security. Govern Shadow AI and ensure EU AI Act compliance with our enterprise platform. Start your AI security audit today.
2013 · bastio.com · its alternatives →
- 16
At my last company, we connected Claude Code and Cursor to almost all our internal services via MCP. It made the team incredibly fast, but we hit a wall: permissions. If you give an agent "Read Only" access, it can’t actually fix anything. If you give it "Write" access, it’s only a matter of time before a hallucination or a bad prompt results in a deleted database or a nuked production bucket. We had a few "close calls" that convinced us that simply reducing IAM permissions makes agents useless. I built Armour (https://github.com/fuushyn/armour) to solve this. It’s a…
Jan 2026 · github.com · its alternatives →
- 17
I started using Claude Code (claude --dangerously-skip-permissions) and Codex (codex --yolo) and realized I had no reliable way to know what they actually did. The agent's own output tells you a story, but it's the agent's story. logira records exec, file, and network events at the OS level via eBPF, scoped per run. Events are saved locally in JSONL and SQLite. It ships with default detection rules for credential access, persistence changes, suspicious exec patterns, and more. Observe-only – it never blocks. https://github.com/melonattacker/logira
Mar 2026 · github.com · its alternatives →
- 18
We’ve been building visual rule engines (clear spreadsheet interfaces -> API endpoints that map incoming data to a large number of potential outcomes), and had the fun idea lately to see what happens when we use our decision table UI with Claude’s PreToolUse hook. The result is a surprisingly useful policy/gating layer– these tables let your team: - Write conditional, exception-friendly policies beyond globs/prefixes (e.g. allow rm -rf only in */node_modules/*, deny / or $HOME, ask if --force or network call; gate kubectl delete / SQL DROP with a clear reason) -…
Jan 2026 · github.com · its alternatives →
- 19
We're excited to launch compliant-llm: an open-source toolkit that helps infosec and compliance teams audit AI agents against regulatory frameworks like NIST AI RMF, ISO 42001, and OWASP Top 10. Infosec and compliance teams are now responsible for tracking security and compliance risks of a growing number of AI agents across external and internal apps and third-party vendors. compliant-llm gives you a way to: - Define and run comprehensive red-teaming tests for AI agents - Maps test outcomes to compliance frameworks like NIST AI RMF - Generate detailed audit logs and documentation -…
2025 · github.com · its alternatives →
- 20
AI Safeguard▲14Prevent sensitive data leaks in popular LLM's like ChatGPT
2025 · aisafeguard.co.uk · its alternatives →
- 21
- 22
Built this around one simple idea: the workflow that wants to execute should not be the same place that decides whether execution may continue. This project puts an external allow/deny boundary before action. Public entry points: * live pilot * commercial request * private deployment There is also a GitHub Marketplace action install surface, but the main point is the boundary model itself: decision stays outside the workflow that is asking to proceed. Looking for feedback from people working on CI/CD, security controls, approval boundaries, and automated execution.
Apr 2026 · ai-admissibility.com · its alternatives →
- 23
Give AI agents your company data. Only what they can see.
Sep 2026 · warehousd.com · its alternatives →
- 24
Hi HN, I'm Jiasheng, co-creator of ZenStack. Access control usually ends up scattered across app code instead of living with the data model — and that's riskier when the code is written by an agent, since it's easy to ship a query with a missing or incomplete authorization check. ZenStack enforces policy (RBAC/ABAC/relation-based) directly at the ORM layer, on top of Kysely, so every query gets checked the same way regardless of who wrote it and who is calling it. Postgres RLS is an option too, but it's hard to maintain and scale, and it's Postgres-only — ZenStack's approach is…
Jul 2026 · zenstack.framer.website · its alternatives →
Also compare
Ranked by how close each launch is in meaning, then by votes. Prices were read from each product’s own site when checked and can change. Refine with your own description →