How the current OmniMemora control surface is organized.
This page translates the earlier console information architecture into a public-facing overview. It exists to explain how the demo and future control plane are structured, without turning architecture into the main selling point.
Near-term pages
Token savings summary, recent requests, active tenants, and service health.
Manual recall execution with selected memories, packed context, and short explanations.
Request-level history and detailed token savings evidence for one query.
Tenant and agent views of usage totals, trends, and savings behavior.
API reference, onboarding, and troubleshooting surfaces that support integration work.
Next layers
Browse raw memory resources by namespace, memory type, or agent for operations and debugging.
Tenant list, tenant summaries, and policy surfaces for isolated workloads.
Agent-level usage and recall comparisons across planner, executor, or supervisor roles.
Feature flags, metering options, API endpoints, and platform-level controls.
Build order
The current recommendation is to prioritize what proves commercial value first: query results, token savings, and request evidence. Full settings and admin surfaces stay behind that.