Security

Their cloud. Their keys. Their data.

Every instance runs in the customer's own project — with their encryption keys, their storage, and a full audit trail on every AI request.

Data boundary

Nothing leaves their project

Your app calls our engine. The engine reads and writes only inside the customer's cloud account.

web
Your app
hub
You Can Ask
cloud_lock
Customer cloud
Document scanningSearchAI modelsAudit logsTheir infrastructure
Guarantees

What procurement teams ask for

Plain answers to the questions that block deals — not marketing claims.

key

Their keys, not ours

Encryption keys and service accounts stay in the buyer's cloud account — we never hold production keys unless explicitly contracted.

storage

Documents stay in their storage

Files and search indexes live in dedicated buckets on the customer's project. No shared document pools.

shield

One customer, one cloud

Each deployment gets its own GCP project or isolated environment. No cross-tenant data paths.

visibility

Audit trail for every AI call

Security teams can trace what was asked, what documents were retrieved, and what was sent to a model.

Isolation

How tenants stay apart

Dedicated IAM, encryption, and network paths per customer deployment.

security

IAM guardrails

Dedicated service accounts per stack. GitHub Actions scoped to the customer project with least-privilege roles.

key

Customer-managed encryption

Optional CMEK for Cloud SQL and GCS on Dedicated Stack tiers. Keys rotate under the buyer's policy.

swap_calls

Private integration paths

ERP and internal tools connect inside the customer VPC. Sensitive graph data never transits through our infrastructure.

Audit

Traceability built in

Security teams can follow every question from request to document source to model response.

history

Request logging

Every chat request logged with timestamps, user context, and tool invocations — exportable for compliance reviews.

description

Source citations

Answers link back to the exact document passages used — so reviewers can verify what the model saw.

verified_user

Approved content only

Responses come from indexed company documents — not the open web. You control what goes in.

Security review checklist

  • task_altDedicated cloud project per customer instance
  • task_altCustomer-owned encryption keys and Secret Manager
  • task_altNo shared vector or document storage between tenants
  • task_altFull audit trail on LLM and retrieval calls
  • task_altNetwork egress controlled through customer VPC rules
  • task_altDWU-first document retrieval for regulated product data (CPR 305/2011)

Need help with a security review?

Book an architecture review — we'll walk through your VPC, secrets, and data flow against our reference deployment.