Need to keep AI knowledge and context under your control?
Private memory supports source-grounded retrieval inside an operator-controlled contour.
S.Y.S.Bennu Labs · Product systems
Modular AI systems for private memory, operator workflows, local automation and direct access
Bennu Labs builds real products with bounded responsibilities. They can stand independently and, where a specific product supports it, run under operator control. We clearly separate what is available from what is still being built.
What do you need to solve?
Start with the buyer problem, not our internal architecture.
Need repeatable AI-assisted workflows with operator control?
Operator-assisted workflows support recurring content and operational work.
IskraNeed to automate local file workflows?
A local daemon and web interface apply and monitor repeatable file rules.
ASANeed to connect payment confirmation to access?
Direct checkout-to-access infrastructure connects payment confirmation and access grants.
ANTI-GADActive products
Available now
Four products with distinct, explicitly stated maturity.
Bounded production-grade deployments
S.Y.S.
Private AI memory for retrieval and source-grounded knowledge workflows.
Internal READY; external bounded public beta
Iskra
Operator-assisted AI workflows for recurring content and operational work.
Controlled modular release readiness
ASA
Local file automation through a web interface and local daemon.
Bounded integration
ANTI-GAD
Crypto-capable direct checkout-to-access infrastructure powered by DAG.
In development
These are architecture and planned roles, not current runtime.
Not current runtime
Phase 0 — architecture and contractsIntake
Architecture being defined for structured, validated handoffs from incoming interactions.
Phase 0 — architecture and contracts
Not current runtime
Architecture / canon / in developmentAI-Mama
Architecture in development for coordinating evidence, recovery and human escalation.
Architecture / canon / in development
Why Bennu
Modular by design
Bounded products can stand independently.
Truth before claims
Implemented, bounded and planned capabilities remain separate.
Control and portability
Delivery is not defined by one Bennu VM; operator-controlled options are stated per product.
Human control
Explicit operator boundaries matter more than claims of human replacement.
How we describe maturity
We label what exists now separately from what we are building next. These labels describe maturity, not certification.
VERIFIED / ACTIVEImplemented and supported within stated boundaries.
BOUNDEDUsable through a defined beta, pilot, deployment or integration.
IN DEVELOPMENT / ARCHITECTUREA planned role; no current product runtime is claimed.
A modular system, without overstating integration
Products can be used independently. We design clear module boundaries and future integrations through explicit contracts. Not every planned connection exists in the current runtime.
Start with your problem
Discuss a pilot, deployment, integration or design partnership at the product’s actual maturity.