AI Workflow Orchestration

Deploy AI Workflows
In Your Cloud

Grove is the enterprise orchestration platform for production AI. Build multi-step workflows as DAGs, run autonomous agents in sandboxed workspaces, route across LLM providers — all in your own infrastructure, with first-class multi-tenancy and the durability and auditability your organization demands.

Why Grove

Built for Enterprise AI

Your Cloud, Your Control

Deploy in your own infrastructure. No data leaves your environment. Air-gap compatible for the most sensitive workloads.

DAG-Based Orchestration

Define workflows as directed acyclic graphs. Automatic parallel execution, fan-in/fan-out, conditional routing, and bounded refinement loops for generator-critic patterns.

Autonomous Agents

Goal-driven loops with allowlisted tools, per-run sandboxed workspaces, durable turn history, and budget caps. Sub-agent delegation with depth and fan-out limits. Resume from any crash.

Multi-Provider LLM Routing

Anthropic Claude, OpenAI, Google Gemini, Azure OpenAI, and Vertex AI in a single workflow. Named model groups with automatic failover. Route per node. Prompt caching and per-token cost accounting keep spend visible and low. No vendor lock-in.

Multi-Tenant by Design

First-class tenant entity with Postgres row-level isolation. Per-tenant secrets, LLM credentials, quotas, rate limits, and budget caps. Tenant lifecycle API with provision-and-key in one call.

Production Durability

PostgreSQL-backed crash recovery. Resume from the last checkpoint. Every execution persisted and auditable. Per-tool-call idempotency keeps side-effecting work at-most-once across crashes.

Platform Architecture

How Grove Works

Define workflows as DAGs or autonomous agents. Grove handles execution, parallelism, streaming, durability, and tenant isolation — in your infrastructure.

Callers
TypeScript SDK
Graph Builder + Streaming
REST API + SSE
Any Language
Arborist UI
Embedded operator SPA
MCP Clients
Claude Desktop · Code · Cursor
GROVE CORE
Rust · Tokio · Axum · sqlx
DAG Scheduler Agent Runtime LLM Broker Tool Registry MCP Server Tenant Isolation Session · Memory Workspace Sandbox Crash Recovery Audit Log
In-process companions
grove-scheduler
Cron triggers · HA-safe Postgres claims
Trailhead
Knowledge graph + pgvector RAG
PostgreSQL
Durability · RLS
LLM Providers
Claude · GPT · Gemini · Azure · Vertex
Blob Storage
S3 · GCS · Azure · Local
External Tools
MCP servers · Connectors · Your APIs
Secrets
AES-256-GCM · HashiCorp Vault
Sandbox
Container backend for agent ws_*/git_*
Deploys to: AWS (EKS) · Azure (AKS) · GCP (GKE) · On-Premise · Air-Gapped
Context Graph

Context is necessary.
Verified execution is the proof.

Every context layer can tell an agent what your data means. None can tell you whether the agent then did the right thing. Grove maps every workflow, run, agent, tool, and the data it touches into a living, governed graph — and scores each path by whether its runs actually passed verification.

Context graph — interactive preview live operator view

Drag nodes to explore · click a node for detail

Execution-grounded, not crawled

Projected from what your workflows and agents actually did — runs, tool calls, connector queries, outputs — not scraped from schemas. Rebuildable from the source of truth and eventually consistent with every execution.

GroveRank — authority from outcomes

Each path is scored by the one signal a data ontology can't compute: the fraction of its runs that passed acceptance, weighted by usage and freshness. Ask "what's the trusted way we do X" — get the verified answer first.

Beside your lakehouse, not against it

Grove imports business meaning from the context layer you already own — Unity Catalog, Genie Ontology — and emits lineage back. Portable across Databricks, Snowflake, and Microsoft.

Governed retrieval, everywhere

Every read is tenant-scoped and authorized through the same policy decision point as the rest of Grove. Query it from the operator console, from your agents as tools, or from external systems over MCP.

Capabilities

Everything You Need for Production AI

External Tool Execution

LLM workflows pause while your application executes tools locally. Credentials never leave your environment. Persisted pending calls survive crashes.

Crash Recovery

PostgreSQL-backed checkpointing. Workflow runs resume from the last completed node; agent runs resume mid-turn with per-tool-call idempotency markers that keep side-effecting work at-most-once.

Real-Time Streaming

SSE event streams deliver node-by-node progress to your UI. Live agent-run replay across replicas. No polling required.

Encrypted Secrets

AES-256-GCM encryption at rest, plus a pluggable backend that can delegate to a HashiCorp Vault KV v2 mount for org-managed secret stores. Per-tenant namespace; never returned through the API.

Control-Flow Primitives

Conditional branching, bounded refinement loops, and a Map node for fan-out over collections. Generator-critic patterns are first-class, not client-side hacks.

Knowledge Graph & RAG

Built-in semantic search and entity-aware retrieval via Trailhead. Ground every workflow in your organization's documents and data.

Provider-Agnostic Blob Storage

S3, GCS, Azure Blob, or local — behind one trait. Operators register named storage profiles; workflows reference them by name. Swap providers with zero workflow changes.

Scheduled & Webhook Triggers

The grove-scheduler workspace member runs cron triggers with HA-safe Postgres claims. Inbound webhook endpoints fire a workflow on every POST. Multi-replica safe; retries with exponential backoff.

Autonomous Agent Runtime

Define an agent once — name, system prompt, tool allowlist, model — then run it against goals. Per-run sandboxed workspaces for file/shell/git tools, plus your own external MCP servers from a per-tenant catalog. Sub-agent delegation with depth and fan-out caps. Tenant-scoped git credentials.

Grove as MCP Server

Workflows and skills surface to MCP clients (Claude Desktop, Claude Code, Cursor) as tools and prompts. grove__* provisioning built-ins let an MCP client author workflows and agents over the protocol. Two-key Invoke/Provision pattern keeps the LLM's authoring rights bounded.

First-Class Multi-Tenancy

Real tenant entity in Postgres with row-level isolation across workflows, runs, sessions, agents, skills, and secrets. Per-tenant quotas, rate limits, and budget caps. POST /tenants provisions a tenant and mints its first key in one call.

Sessions & Memory

Multi-turn conversation context with rolling summarization and hierarchical memory namespaces. Tool-based prompt enrichment lets agents promote relevant memories into the system prompt on demand.

Case Study

Lead deduplication on the lakehouse

Salesforce, HubSpot, and event leads land in Databricks as the same people, spelled a dozen different ways. Deterministic SQL resolves the obvious duplicates cheaply; Grove brings an LLM to bear only on the ambiguous matches a rule engine can't settle — and writes nothing it can't defend.

  • Blocking and rule-scoring run in Databricks SQL — Grove is invoked only for the low-confidence band.
  • The LLM adjudicates the fuzzy matches at 100% precision on the hard cases, with a reason for every call.
  • A human-in-the-loop review queue writes corrections back to the lakehouse to tighten the next run.
Explore the live case study →

Runs against real data in Databricks, through Grove.

41% 77%
duplicate-match recall, rules alone vs. rules + Grove
99.8%
precision held while recall nearly doubled
2,392
leads unified across three sources
One workflow
Grove orchestrates ingest → block → adjudicate → resolve
  • AES-256-GCM Encryption
  • Air-Gap Compatible
  • Audit Logging
  • Self-Hosted — Your VPC
  • Enterprise License Tiers

Ready to deploy AI workflows in your cloud?

Contact Sales