Services

Three engagements. Each ends with evidence.

MapleAI services are sold around a bounded workflow, named deliverables, and an acceptance gate. We begin with the authority problem, prove one lifecycle, and expand only after the evidence supports it.

01

Available / 5 business days

Agent Governance Readiness Review

A decision-ready map of one agent workflow: authority boundary, capabilities, risk classes, evidence requirements, and a prioritized adoption plan.

Included

  • Current-state workflow and trust-boundary map
  • Threat and failure-mode review
  • Capability, approval, and receipt contract
  • Readiness scorecard with next-step estimate

Acceptance gate

Your team can identify who authorizes each consequence, what evidence survives, and which gaps block a pilot.

Scope this engagement
02

Booking / 3-6 weeks

Governed Workflow Pilot

One consequential action runs through explicit model proposal, deterministic authorization, controlled execution, receipt capture, and evaluation.

Included

  • Self-hosted Maple AI OS pilot environment
  • One integrated workflow and capability policy
  • Receipt, denial, and rollback test cases
  • Evaluation report and operator runbook

Acceptance gate

The agreed happy path and denial path are reproducible, evidence is inspectable, and rollback is exercised before handoff.

Scope this engagement
03

Limited design partners / Scoped after pilot

Self-Hosted Production Design Partnership

Harden a successful pilot for your identity, deployment, observability, incident, retention, and compliance environment.

Included

  • Production architecture and control ownership
  • Deployment, backup, restore, and incident runbooks
  • Security and integration backlog with release gates
  • Go-live review against jointly approved criteria

Acceptance gate

Production readiness is determined by the agreed gates. This engagement does not imply certification, regulatory approval, or an unconditional SLA.

Scope this engagement

How We Work

Practical operating rules

  • One named workflow and owner before architecture expands
  • Measurable acceptance criteria before implementation begins
  • Fail-closed handling for missing policy, identity, or approval
  • Evidence and rollback tested as product behavior

Not Included

Boundaries we will not blur

  • Unsupervised financial, medical, legal, or safety-critical decision making
  • Claims that a model is accurate without a task-specific evaluation
  • Automatic production deployment without the customer's authorization path
  • Certification, audit opinion, or regulated approval by implication

Bring the workflow, not a blank transformation mandate

Tell us the action, current operator, systems touched, data boundary, and consequence of failure. We will recommend the smallest responsible engagement.