Skip to Content
Aionis currently ships as a local-first Lite Runtime for developer machines and self-managed deployments.
ProductsOverview

Product Surfaces

Aionis exposes product surfaces around one Runtime loop:

observe -> guide -> agent action -> feedback -> measure -> snapshot

The main public surfaces are ordered by product role:

SurfaceRoleUse it when
Execution MemoryCore Runtime capabilityAgents need to continue work across sessions, roles, failures, and handoffs.
Memory FirewallGovernance entry pointYou already have Mem0, Zep, vector DB, markdown, or another backend and need safe admission before prompt use.
Agent Flight RecorderAudit and replayYou need to know what the Agent could see, what was blocked, and why.
Loop EngineeringLoop memory layerYour Agent already plans, acts, validates, repairs, and needs memory across iterations.
Controlled ForgettingLifecycle controlYou need suppression, archival, rehydration, and deletion without silent memory drift.
Admission Dataset ExportLearning flywheelYou want to export admission, usage, outcome, and feedback data for analysis or learned policy training.

Product Positioning

Execution Memory is the primary Aionis memory system. It records task evidence, adjudicates active state, isolates failed branches, and compiles a governed Agent context.

Memory Firewall is the fastest adoption path. It lets teams keep their existing memory backend while using Aionis as the admission layer. That makes Firewall a strong entry point, but not the ceiling of the product.

The other surfaces build on the same substrate: decision traces, feedback attribution, lifecycle state, and auditable context compilation.