Comparison
openfirma vs Aegis
Verdict
Unverified catalog guidance: openfirma: Openfirma is a policy-enforcing sidecar for AI agents that uses Cedar policies to gate outbound calls, built in Rust under the GPL-3.0 license. Aegis: Aegis provides runtime policy enforcement for AI agents with cryptographic audit trails and human-in-the-loop approvals, supporting zero-code deployment switches suited for various compliance needs.
Markdown twin · openfirma alternatives · Aegis alternatives
GraphCanon updated Oct 21, 2026
Trust & integrity
| Signal | openfirma | Aegis |
|---|---|---|
| Maintenance | Very active (1d since push) As of Oct 21, 2026 · github_public_v1 | Active (10d since push) As of Oct 19, 2026 · github_public_v1 |
| Provenance | Not a fork · Organization account As of Oct 21, 2026 · github_public_v1 | Not a fork · Personal account As of Oct 19, 2026 · github_public_v1 |
| OSV dependency advisories | No lockfile (source not queried) As of Jul 15, 2026 · osv@v1 | No lockfile (source not queried) As of Jul 15, 2026 · osv@v1 |
| deps.dev advisories | Not queried deps.dev@v1 | Not queried deps.dev@v1 |
| OpenSSF Scorecard | Not queried openssf-scorecard@v1 | Not queried openssf-scorecard@v1 |
Tagline
- openfirma
- Runtime enforcement boundary for AI agents with local sidecar
- Aegis
- Runtime policy enforcement for AI agents with cryptographic audit trail and human-in-the-loop approvals.
Stars
- openfirma
- 140
- Aegis
- 542
Forks
- openfirma
- 9
- Aegis
- 52
Open issues
- openfirma
- 6
- Aegis
- 4
Language
- openfirma
- Rust
- Aegis
- TypeScript
Adopt for
- openfirma
- Unverified catalog guidance: Openfirma is a policy-enforcing sidecar for AI agents that uses Cedar policies to gate outbound calls, built in Rust under the GPL-3.0 license.
- Aegis
- Unverified catalog guidance: Aegis provides runtime policy enforcement for AI agents with cryptographic audit trails and human-in-the-loop approvals, supporting zero-code deployment switches suited for various compliance needs.
Persona
- openfirma
- -
- Aegis
- -
Runtime
- openfirma
- -
- Aegis
- -
License
- openfirma
- GPL-3.0
- Aegis
- MIT
Last pushed
- openfirma
- Oct 19, 2026
- Aegis
- Oct 9, 2026
Categories
- openfirma
- AI Agents, Evaluation & Observability
- Aegis
- AI Agents, Evaluation & Observability
Trust and health
Maintenance
- openfirma
- Very active (96%)
- Aegis
- Active (82%)
Days since push
- openfirma
- 1d
- Aegis
- 10d
Open issues (recorded)
- openfirma
- 6
- Aegis
- 4
Stars delta
- openfirma
- +5 (30d)
- Aegis
- +202 (30d)
Open issues delta
- openfirma
- -2 (30d)
- Aegis
- +1 (30d)
Owner type
- openfirma
- Organization
- Aegis
- User
Full report
- openfirma
- Trust report
- Aegis
- Trust report
Choose openfirma if…
- openfirma is primarily Rust; Aegis is TypeScript.
- License: openfirma is GPL-3.0, Aegis is MIT.
- Tags unique to openfirma: access-control, agentic-ai, ai-agents, authorization.
- openfirma has Docker configuration in its repository.
- Unverified catalog guidance: When you need deterministic and call-level runtime enforcement that specifically leverages Cedar policies tailored for your needs.
When NOT to use openfirma
- Unverified catalog guidance: Avoid if you prefer a solution not tightly coupled to Cedar policies, as Openfirma exclusively supports this policy framework.
- Unverified catalog guidance: Do not use if licensing is critical and you need permissive licenses, since Openfirma uses the GPL-3.0 license.
Choose Aegis if…
- Aegis is primarily TypeScript; openfirma is Rust.
- License: Aegis is MIT, openfirma is GPL-3.0.
- Tags unique to Aegis: ai-safety, anthropic, audit-trail, llm-observability.
- Unverified catalog guidance: You need cryptographic assurance of the audit trail to meet high-security standards.
When NOT to use Aegis
- Unverified catalog guidance: The project does not require a zero-code deployment switch and can manage changes directly in the codebase.
- Unverified catalog guidance: Minimal regulatory requirements mean that elaborate configurations like Aegis's strict retention policies are unnecessary.
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (Firma-AI/openfirma) · observed Oct 21, 2026
- GitHub forks (Firma-AI/openfirma) · observed Oct 21, 2026
- Last push (Firma-AI/openfirma) · observed Oct 19, 2026
- License file (GPL-3.0) · observed Oct 21, 2026
- Decision facts (enrichment) · observed Jul 16, 2026
- Trust scan (lockfile / OSV) · observed Jul 15, 2026
- GitHub stars (Justin0504/Aegis) · observed Oct 19, 2026
- GitHub forks (Justin0504/Aegis) · observed Oct 19, 2026
- Last push (Justin0504/Aegis) · observed Oct 9, 2026
- License file (MIT) · observed Oct 19, 2026
- Decision facts (enrichment) · observed Jul 16, 2026
- Trust scan (lockfile / OSV) · observed Jul 15, 2026
GitHub stars on cards: openfirma 140 · Aegis 542 (synced Oct 21, 2026).
Common questions
- What is the difference between openfirma and Aegis?
- openfirma: Runtime enforcement boundary for AI agents with local sidecar. Aegis: Runtime policy enforcement for AI agents with cryptographic audit trail and human-in-the-loop approvals.. See the comparison table for recorded GitHub metadata and shared categories.
- When should I choose openfirma over Aegis?
- For openfirma, compare these recorded points with Aegis: openfirma is primarily Rust; Aegis is TypeScript; License: openfirma is GPL-3.0, Aegis is MIT; Tags unique to openfirma: access-control, agentic-ai, ai-agents, authorization; openfirma has Docker configuration in its repository; Unverified catalog guidance: When you need deterministic and call-level runtime enforcement that specifically leverages Cedar policies tailored for your needs.
- When should I choose Aegis over openfirma?
- For Aegis, compare these recorded points with openfirma: Aegis is primarily TypeScript; openfirma is Rust; License: Aegis is MIT, openfirma is GPL-3.0; Tags unique to Aegis: ai-safety, anthropic, audit-trail, llm-observability; Unverified catalog guidance: You need cryptographic assurance of the audit trail to meet high-security standards.
- When should I avoid openfirma?
- Unverified catalog guidance: Avoid if you prefer a solution not tightly coupled to Cedar policies, as Openfirma exclusively supports this policy framework. Unverified catalog guidance: Do not use if licensing is critical and you need permissive licenses, since Openfirma uses the GPL-3.0 license.
- When should I avoid Aegis?
- Unverified catalog guidance: The project does not require a zero-code deployment switch and can manage changes directly in the codebase. Unverified catalog guidance: Minimal regulatory requirements mean that elaborate configurations like Aegis's strict retention policies are unnecessary.
- Is openfirma or Aegis more popular on GitHub?
- Aegis has more recorded GitHub stars (542 vs 140). Stars measure visibility, not whether either tool fits your constraints.
- Which licenses are recorded for openfirma and Aegis?
- openfirma: GPL-3.0. Aegis: MIT. Check each repository's current license and terms before use. Public GitHub hosting alone does not establish open-source licensing.
- Where can I find alternatives to openfirma or Aegis?
- GraphCanon lists candidates at openfirma alternatives and Aegis alternatives (openfirma markdown twin, Aegis markdown twin). The discovery order uses stored relationship proposals and shared categories; it is not a verified replacement ranking.
- Is there a machine-readable version of this comparison?
- Yes. The markdown twin at this comparison mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.
- Which is better maintained, openfirma or Aegis?
- openfirma: Very active. Aegis: Active. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.
- Where are the full trust reports for openfirma and Aegis?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: openfirma trust report; Aegis trust report.