Skip to main content
The Medera Agentic Framework is built around two pillars: the visual canvas where you author workflows, and the care orchestrator that runs them. Both share one event bus and one tenant audit trail.

​
Stack

medera/agentic-stack.svgthree-tier architectureThree-tier agentic architectureCanvasVisual workflow editor · 16 nodes + 8 BH-OS railsWorkflow RuntimeDurable execution · WORM audit · semver versioningCare OrchestratorVoice + workflow agents · event bus · state machineINTEGRATIONSVoice provider · EHR (FHIR R4) · billingePA · clearinghouse · screenersMobile · web · embedded SDKsCOMPLIANCE PATHHIPAA · 42 CFR Part 2 · auditTenant isolation · RLS · encryptionMerkle-chain integrity · WORM

​
Workflow execution

medera/exec-sequence.svgworkflow executionClientAPIRuntimeOrchestratorLive agentsPOST /workflows//executeEnqueue execution jobDispatch agentInvoke live agentReturn resultResolve nodeStream eventsWSS events + JSON

​
Tenant isolation

Every workflow runs inside a tenant-scoped transaction. Row-level security enforces that all reads and writes are filtered by organization_id — a misconfigured tenant ID cannot reach another tenant’s data.

​
Versioned execution

Published workflows are immutable snapshots. Draft edits made after a publish never affect executions of the published version — what you run is what you signed.

​
What’s next

Core Concepts

Vocabulary and building blocks.

Orchestrator

Multi-agent runtime.

Context & Memory

Variable scopes and persistent memory.

Canvas

Build your own workflow.