The Right Substrate for Your Use Case
Five opinionated starting points — each backed by V2 runtime entities, lineage, and governance.
14 agents. Zero custom state tables.
Replace hand-rolled document processing pipelines with governed runtime entities. Every extraction, validation, and decision is tracked with full lineage — no custom Postgres tables, no orphaned state.
See the Meridian Story →Processing latency
Custom state tables
Decision explainability
False-positive escalation
SOLUTION TEMPLATES
Deploy in Hours, Not Quarters
Pre-built templates with governed runtime wiring. Clone, configure, ship.
Agent Memory + Lineage
< 30 minPersistent memory with full causal traceability for every agent decision.
Minimum tier: CloudReviewable Workflow Runtime
< 2 hoursTask lifecycle with human gates, evidence bundles, and SLA enforcement.
Minimum tier: TeamBranch-Safe Speculative Execution
< 1 hour5 visibility modes for safe speculative execution with merge provenance.
Minimum tier: TeamModel Routing with Shadow Evaluation
< 3 hoursCost-optimized model selection with shadow policy replay and reward tracking.
Minimum tier: EnterpriseCUSTOMER STORY
From 42 Tables to Zero Custom Control-Plane
A Series B fintech runs 14 AI agents to process mortgage applications — extracting data, validating compliance, routing to underwriters, and generating decision memos. Before V2, each agent needed its own state table, retry logic, and audit trail. After migrating to HatiData V2, they replaced all of it with platform entities.
3s → 180ms
Document processing latency
42 → 0
Custom state tables eliminated
100%
Decision explainability via ExplainBundle
65% → 22%
False-positive escalation rate
“We were spending 40% of engineering time maintaining state machines and retry logic. V2 gave us that time back — and the lineage graph caught two compliance gaps we didn't know existed.”
— VP Engineering, Series B Fintech
Ship Smarter Agents. Start in 60 Seconds.
Persistent memory. Isolated state. Verifiable reasoning. Through standard SQL.