Alternatives
Products that do what BoaOps Authorization Engine does
Authorization delayed? Lives wait. We end that.
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9KA
A large part of our (Real Kinetic's) business is helping organizations implement platform engineering, but we've found the existing tooling to be lacking. For IaC, Terraform state becomes a pain because TF treats infrastructure as "one-shot" commands. The Kubernetes controller model provides a nicer approach to managing infrastructure, but the tooling here is also lacking. For configuration management, Helm just doesn't really scale with complexity, nor does Kustomize. For resource orchestration, Crossplane is a step in the right direction but still has challenges and limitations. As a…
2025 · koreo.dev
- 10RT
This project (Agents Observe) started as an exploration into building automation harnesses around claude code. I needed a way to see exactly what teams of agents were doing in realtime and to filter and search their output. A few interesting learnings from building and using this: - Claude code hooks are blocking - performance degrades rapidly if you have a lot of plugins that use hooks - Hooks provide a lot more useful info than OTEL data - Claude's jsonl files provide the full picture - Lifecycle management of MCP processes started by plugins is a bit kludgy at best The biggest takeaway is…
Apr 2026 · github.com
- 11
- 12OS
Hi everyone, We have just released an open-source case management dashboard for manually approving/rejecting KYC requests (know your customer) with built-in OCR & face-matching functionalities. Next steps: - Enable KYB (business onboarding) documents and personas approval. - Connected backend between our KYC flow and the case management dashboard. - Releasing an open-source rule engine, to help automate decisions. We’d love for you to try it out, give us feedback, and suggest features that would make it applicable to you. And if the rest of the project is relevant or interesting to you,…
2022 · backoffice-demo.ballerine.app
- 13
- 14
- 15
- 16LE
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
- 17
- 18
- 19KD
Every AI agent that does something useful - opening a PR, posting in Slack, updating a ticket - needs to call an API on behalf of a user. That means OAuth. Authorization flows, token storage, refresh logic, per-user credential isolation. Today, most teams solve this with a long-lived API key in an .env file, shared across every user and every session. As everyone in an organization becomes a software engineer - whether they know it or not - you can't expect each of them to roll their own OAuth. Secure credential handling needs to be baked into the infrastructure. The core issue: agents are a…
Mar 2026 · kontext.dev
- 20
- 21PE
Show HN: Runtime authorization for Claude Code, Cursor, and Codex Hi HN, Fernando and I built Kastra. Kastra intercepts AI agent tool calls and evaluates them against deterministic policies before they execute. This is aimed at developers using coding agents like Claude Code, Codex, Cursor, and OpenClaw. We built Kastra after one of our Cursor agents almost executed DELETE FROM customers WHERE status='test' against a production database. We caught it before it ran, but it made us realize that nothing in our stack actually decided what the agent was allowed to do. What mattered for us wasn't…
Jul 2026 · kastra.ai
- 22
- 23ZA
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
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →