Kernel Priority
Maple Runtime
Event fabric, commitment gate, worldline memory, and provenance-owned execution.
Role: The governed runtime core for consequential agent actions.
Explore Maple RuntimeProducts
Six operating layers for governed agent systems
MAPLE packages the full Agent OS surface: runtime kernel, supply chain, model operations, governance, continuous improvement, and fleet orchestration.
Product Suite
The operating layers that turn models into governed agent services
Supply Chain Priority
Maple Registry
OCI-style package distribution, signing, catalogs, mirroring, and artifact lifecycle.
Role: How agent packages move safely across environments.
Explore Maple RegistryModel Ops Priority
Maple Models
Pull, serve, route, benchmark, and govern local or hosted models behind one control surface.
Role: Model-neutral inference with policy-aware routing.
Explore Maple ModelsGovernance Priority
Maple Guard
Capability firewall, approval workflows, PII controls, and compliance overlays.
Role: Deny-by-default execution for real-world agent actions.
Explore Maple GuardImprovement Priority
Maple Foundry
Trace capture, eval loops, distillation, and student-teacher routing for continuous improvement.
Role: Turn production behavior into safer and cheaper future behavior.
Explore Maple FoundryOrchestration Priority
Maple Fleet
Instance lifecycle, stacks, canary rollout, cost budgets, and multi-tenant isolation.
Role: Operate agent services like infrastructure, not hand-managed demos.
Explore Maple FleetSuite Details
What each layer is responsible for
Maple Runtime
The kernel layer: event fabric, commitment gate, worldline memory, and consequence execution.
Maple Registry
OCI-style storage, cataloging, mirroring, signing, and package distribution for agent artifacts.
Maple Models
Unified pull, serve, inspect, benchmark, and route semantics across local and hosted model backends.
Maple Guard
Capability firewall, approvals, PII handling, and compliance packs for governed execution.
Maple Foundry
Trace capture, eval pipelines, distillation loops, and quality gates for continuous improvement.
Maple Fleet
Lifecycle control, stacks, rollout policy, multi-tenant isolation, and cost boundaries for production operation.
Need help choosing where to start?
Most teams begin with Runtime plus Guard, then add Registry, Models, Foundry, and Fleet as the operating surface grows.