Products

Buy the governed workflow, not the entire roadmap

Maple AI OS is the MapleAI product. Hermon, Wish, and OpenIBank have separate product boundaries. DOGMA and Hermon DNA are open research. Each line below states what can be used now and what remains unproven.

Portfolio

One commercial wedge. Clear product boundaries.

Maple AI OS is MapleAI's flagship. Hermon and Wish are independent Hermon products. OpenIBank is a governed finance application. DOGMA and Hermon DNA are research programs with public evidence gates.

Availability is a contract.

A public page is not the same as a production service. Open the readiness record for working scope, current limits, and evidence.

Review product readiness

Where To Start

Choose by operational need

Maple does not require an ecosystem-wide commitment. Start at the smallest layer that resolves a real constraint.

01

You are evaluating the architecture

Self-hosted developer preview

Build the source, run the quickstart, and inspect the resulting receipts.

02

An agent can create a real consequence

Governed Workflow Pilot

Put one action behind policy, approval, evidence, and rollback acceptance gates.

03

You need a local model gateway

Hermon Engine

Adopt Hermon directly; add Maple only when actions need durable authority.

04

You are studying DNA-native intelligence

Maple DNA research

Use the code, books, and frozen evaluations. Do not treat research checkpoints as production models.

Inside Maple AI OS

Subsystems are capabilities, not extra product brands

Registry, Guard, Kernel, and WorldLine stay inside the operating system vocabulary. They are not separately purchasable cloud services, and their maturity is governed by the Maple AI OS status.

Maple Brain

Interprets intent and selects intelligence without receiving permission to execute consequences.

Guard + Kernel

Validate capabilities, policy, budgets, approvals, and commitments through a fail-closed authority boundary.

WorldLine

Preserve signed proposals, decisions, executions, outcomes, and rollback history as verifiable receipts.

Packs and contracts

Describe agent, policy, model, and driver artifacts through explicit schemas and versioned package contracts.

Start with one governed action

Prove the Maple lifecycle around one consequential workflow. Add adjacent products only where they create measurable value.