FAQ
What is Forgewarden?
Forgewarden is an evidence-first security platform for inspecting and governing software changes. Its broader roadmap extends the same deterministic controls toward AI-guided threat hunting, endpoint protection, quarantine, detonation, deception, and recovery.
Does Forgewarden stop intrusions today?
Not as a production enforcement product today. Forgewarden has deterministic policy, evidence, attack-story, detection-only, network-inspection, application-control simulation, and native operator-visibility foundations. Live sensors, containment, quarantine execution, malware detonation, deception services, and recovery execution remain separately reviewed roadmap capabilities.
Will AI be allowed to block or quarantine systems by itself?
No. Forgewarden follows “autonomous security without autonomous authority.” AI may investigate, correlate, prioritize, and recommend. Deterministic policy, scoped Action Tickets, human authority, Evidence, rollback requirements, and the kill switch govern actions.
Does it deploy software automatically?
The current design is intentionally guarded. Testing and evidence collection can be automated; deployment remains disabled or explicitly bounded until the appropriate adapter and approvals exist.
Can it work with Docker and compiled software?
Yes, the testing direction covers local Docker stacks, fixture-driven services, scripts, and compiled programs. The test contract is about observable behavior and safe boundaries, not a single programming language.
Does it index my entire codebase?
Only an approved checkout should be indexed. Repository-scoped indexes record revision and file hashes, reject unsafe paths, detect stale results, and support bounded lifecycle controls.
Is Forgewarden SOC compliant?
No certification claim is made today. The product is being designed around evidence, least privilege, auditability, and fail-closed controls that can support a later formal assessment.
Who owns Forgewarden?
Forgewarden is owned by Fuzzy Holdings LLC.