Skip to main content
โ† All products
๐Ÿญ

FactoAI Studio

Beta

Author governed, source-grounded domain AI agents once and run them identically anywhere, including fully air-gapped.

The problem

Enterprises in regulated domains cannot send sensitive data to hosted AI services, and generic LLM apps produce answers with no verifiable provenance, no access controls, and no defensible record of what happened. Governance, attribution, and auditability are typically bolted on after the fact, if at all. That leaves teams unable to trust, deploy, or defend AI in the environments where it matters most.

What it is

FactoAI Studio is an agentic AI platform for building specialized domain agents that deploy cleanly into a customer's own environment, whether on-prem, private cloud, hybrid, or fully air-gapped. Each agent is a versioned, declarative Agent Bundle of prompts, tools, retrieval, guardrails, governance, evals, and model requirements, authored once in the Studio and executed identically by the Runtime. Every answer is grounded in sources and verified claim by claim, every decision is policy-checked, and every step is written to a tamper-evident audit log. No customer data has to leave the environment.

Why it matters

What you get

๐Ÿ”’

Zero data egress runtime

The data plane runs fully self-contained and air-gappable, with embeddings and optionally models running locally so data stays in place.

๐Ÿ“Ž

Provenance by construction

Every answer is decomposed into atomic claims and each is verified against the exact source span retrieved, not just tagged with a citation.

๐Ÿ›ก๏ธ

Governance built in

No-code guardrails, Open Policy Agent access rules, eval gates, and a hash-chained audit log are part of the core rather than add-ons.

๐Ÿ“ฆ

Author once, run anywhere

An agent is a versioned, immutable bundle that executes identically across on-prem, private cloud, hybrid, and air-gapped environments.

Capabilities

Everything FactoAI Studio does

๐Ÿ“ฆ

Declarative agent bundles

An agent is a versioned, immutable spec pairing prompts, tools, retrieval, guardrails, governance, evals, and model requirements. Author it once and run it identically in any environment.

๐Ÿ”

Hybrid grounded retrieval

Dense semantic embeddings are fused with sparse lexical BM25 ranking, and layout-aware ingestion turns PDF, DOCX, PPTX, and HTML into section-aware chunks carrying human-readable source locations.

๐Ÿค–

Bring your own model

Register connections to Anthropic, OpenAI, Gemini, or local vLLM and Ollama with credentials encrypted at rest, and bind any model that satisfies a bundle's declared requirements.

โœ…

Eval-gated quality

Faithfulness, answer relevancy, citation coverage, and attribution coverage are scored by an in-environment judge plus deterministic checks. A bundle ships only if it passes the thresholds in its spec.

๐Ÿงพ

Tamper-evident audit

Every policy, guardrail, plan, tool call, attribution, and finalize decision is written to an append-only, hash-chained log, so altering any earlier record invalidates every later hash.

๐Ÿ”—

Multi-agent workflows

Chain bundles into stages that run sequentially, in parallel, or conditionally with typed data flow, executed durably as independently governed and audited child runs.

๐ŸŽ“

Per-customer domain models

LoRA fine-tune a small base model on the customer's own data inside their environment, producing an adapter the gateway serves and a bundle binds to, with eval-gated promotion.

๐Ÿ–ฅ๏ธ

Studio console

Create and edit agents, configure models, guardrails, and policies with no code, run agents in a Playground, and review the audit trail from a web console.

How it works

From start to value

STEP 01

Author a bundle

In the Studio, define the agent as a versioned bundle of prompts, tools, retrieval, no-code guardrails, plain-English access policies, evals, and model requirements.

STEP 02

Ground and evaluate

Ingest documents into the hybrid index, run the agent in the Playground, and trigger the eval gate that must pass before the bundle ships.

STEP 03

Run durably with attribution

The Runtime executes the agent loop, checking policy, grounding each claim to a source span, and writing every decision to the hash-chained audit log.

STEP 04

Export for deployment

Package the agent, or a whole workflow, into a self-contained air-gap artifact bundling its policies, guardrails, and model connection as a Helm chart.

STEP 05

Deploy into the environment

Install the zero-egress data plane on-prem, private cloud, hybrid, or air-gapped, binding a local or provider model that meets the bundle's requirements.

Use cases

Where teams use it

โœ“Summarize insurance claims with citations while redacting PII before the model ever sees the text.
โœ“Review contracts and surface clauses with each finding traceable to the exact source span.
โœ“Draft credit memos and financial analysis grounded in indexed source documents inside the customer environment.
โœ“Produce investment and asset-management research where every claim is verified against its source before the answer is allowed.
โœ“Automate back-office RFP responses as governed, audited multi-agent workflows.
โœ“Stand up a document-QA agent that cites its sources and refuses when it cannot ground an answer.

Who it's for

Regulated and data-sensitive enterprises, and the partners who deploy for them, that need defensible, source-grounded AI agents running inside their own on-prem or air-gapped environments.

Works with

TemporalLangGraphLiteLLMvLLMOllamaQdrantFastEmbedDoclingModel Context ProtocolOpen Policy AgentFastAPIDockerHelmKubernetesOpenTelemetry

What sets it apart

  • โ—† Governance, span-level attribution, and a tamper-evident hash-chained audit log are built into the core rather than bolted on afterward.
  • โ—† The runtime enforces zero data egress and is fully air-gappable, with local embeddings and optional local models so nothing leaves the environment.
  • โ—† One-click export packages an agent or an entire multi-agent workflow, with its policies, guardrails, and model connection, into a single self-contained air-gap artifact.
  • โ—† Open standards such as MCP, OPA, and OpenTelemetry with permissively licensed components avoid lock-in and let the platform be embedded and resold.
FAQ

Common questions

Can it run fully air-gapped without sending data out?

Yes. The data plane runs self-contained on-prem, private cloud, hybrid, or air-gapped, and a network policy denies outbound traffic while embeddings and optionally models run locally, so customer data stays in place.

How does it prove an answer is actually supported by its sources?

Every answer is decomposed into atomic factual claims, each claim is verified against the specific source span the agent retrieved, coverage is recorded, and answers carrying unsupported claims are blocked.

Can I use my own models?

Yes. You can register Anthropic, OpenAI, Gemini, or local vLLM and Ollama connections with credentials encrypted at rest, and a bundle declares requirements so any model that satisfies them can be bound, with the eval gate re-run on the swap.

Build a governed, source-grounded agent and deploy it into your own environment, air-gap included.

Reach out for early access, a live demo, or a partnership conversation.

More from MetaVector Labs