Private Deploy

The whole stack. Inside your cloud.

All five engines. Your own Context Graph instance. Customer-trained on your precedents. Air-gappable.

Decision aid

When private is the right answer.

Private deploy is the heaviest surface we ship. It's worth it for a specific set of conditions — and overkill if none apply.

Choose Private if
  • You're in BFSI, pharma, defense, or another regulated sector
  • Your data has a sovereign-cloud or in-region residency requirement
  • You need a customer-tenant graph trained on your own precedents — not shared with anyone
  • You operate in an air-gapped environment or one where outbound traffic to a SaaS is a non-starter
  • Your CISO requires SOC 2 / GDPR-aligned deploy inside your VPC
  • You want to BYO LLM (Azure OpenAI / Bedrock / Vertex / on-prem) and identity provider
If none of those apply

Private deploy is overkill for you. Use one of the lighter surfaces instead:

Surface 1 · Featured
Connect Your AI →
MCP servers — ChatGPT, Claude, Perplexity, Copilot, Gemini, Azure AI.
Surface 2
Connect Your Browser →
Chromium extension. Side panel + capture-to-Graph.
Why private

Four reasons. One decision.

Data sovereignty

Your data never leaves your perimeter. Customer-tenant graph. BYO LLM endpoint. BYO IdP.

Customer-trained graph

Fine-tune the Context Graph on your own institutional precedent — without contributing back.

Regulated industries

BFSI, pharma, defense, sovereign-cloud — SOC 2 / GDPR aligned, air-gappable.

BYO everything

BYO LLM (Azure OpenAI / Bedrock / Vertex / on-prem). BYO identity. BYO observability.

Deployment shape

Helm charts. K8s. Your cloud.

Stack
  • Helm charts → K8s on Azure / AWS / GCP
  • Customer-tenant Context Graph instance (self-hosted Neo4j HA)
  • Azure Confidential Compute or equivalent
  • BYO LLM routing (Azure OpenAI / Bedrock / Vertex / on-prem)
  • SOC 2 / GDPR alignment · audit lineage
What's included
  • Deployment + integration with your identity + observability
  • Ingest of customer precedents into the graph
  • Customer-specific fine-tuning
  • 12 months of support + quarterly architecture review
Engagement model

Three steps. One price band.

01

Discovery

2 WEEKS

Scope the deployment, the precedent corpus, the regulatory envelope.

02

Pilot

60 DAYS

Stand up the customer-tenant graph. Ingest the first cohort of precedents. Validate.

03

Production

ONGOING

Full five-engine production deployment. Quarterly reviews. Fine-tune cycles.

Talk to us

Private deploy is a conversation, not a checkout.

Email the founder directly. We'll come back with scope, fit assessment, and a discovery call — typically within 48 hours.

Not sure private is the right fit? See the other three surfaces or compare on /how.