RENKER
No liveness check has reached it yet; it is registered on GitHub and has been in the index since 11 Oct 2026. How this is checked
RENKER is a shared security foundation for autonomous AI systems, covering capabilities, permissions, identity, policy, and audit. Its projects include a desktop agent, an evidence-aware research architecture, and content-blind secure communication infrastructure for developers and security teams.
Inferred · not functionally tested
Overview
6 featuresPurpose: Controlling and auditing autonomous AI agent actions without relying on the agent's own claims.
Inferred · not functionally tested
Audience: AI security engineers and developers building autonomous agents
Inferred · not functionally tested
Functions: agents, monitoring
Inferred · not functionally tested
Interfaces: API: unknown · MCP: unknown · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)
Recorded constraints: pricing: open_source · license: Open Source · platforms: CLI, WEB · deployment: browser, cli, self_hosted
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: sebastianrenker.github.io · github.com. These links do not verify the individual claims.
RENKER sits in PulseGate's AI security & guardrails category. Inferred · not functionally tested: It focuses on controlling and auditing autonomous AI agent actions without relying on the agent's own claims. Inferred · not functionally tested: RENKER is an open-source project aimed at AI security engineers and developers building autonomous agents. Basis unknown · not verified: RENKER is open source under the Open Source license. Basis unknown · not verified: It runs on the web and the command line, and it can be self-hosted.
Sebastian Renker builds and maintains RENKER, and it first shipped in 2026. The project is developed in the open on GitHub with 14 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include capability grants, permission policies, and agent identity.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Capability grants
- Permission policies
- Agent identity
- Action auditing
- Evidence categories
- Secure communication
Topics: Inferred · not functionally tested
Built with & integrations
- Claude Code
- commit 5eb10b286742 · since Sep 2026
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
- Indexed11 Oct · 13:50 UTCGuardrails outside the model: authorizing AI agent actions seen via DEV.to articlesSource: DEV.to articles · Open
Frequently asked questions about RENKER
- What does RENKER do?
- Inferred · not functionally tested: RENKER focuses on controlling and auditing autonomous AI agent actions without relying on the agent's own claims. It is catalogued under AI security & guardrails on PulseGate.
- Who should use RENKER?
- Inferred · not functionally tested: RENKER is an open-source project built for AI security engineers and developers building autonomous agents.
- Is RENKER free?
- Basis unknown · not verified: Yes — RENKER is open source under the Open Source license and free to use.
- What platforms does RENKER run on?
- Basis unknown · not verified: RENKER runs on the web and the command line. It can also be self-hosted.
- Is RENKER still maintained?
- The GitHub repository shows 14 commits in the last 90 days.
- Who makes RENKER?
- RENKER is developed by Sebastian Renker.
- How long has RENKER been around?
- RENKER first shipped in 2026.
- Is RENKER open source?
- Basis unknown · not verified: Yes — RENKER is open source under the Open Source license, developed on GitHub.
Similar projects
Closest matches by what these projects do