Skip to main content
CoreBase gives you four ways to connect data to the agent, each with a different perimeter. The strictest mode keeps every row physically inside your network; the lightest pastes a DSN into our panel. Pick the one that matches your compliance posture.

​
The four deployment modes

Cloud-direct

Paste a database DSN into the panel. CoreBase Cloud opens the connection, runs read-only queries, returns rows to the LLM. Fastest onboarding; rows traverse the wire.

Cloud-relay (CoreMCP)

CoreMCP agent runs inside your perimeter and holds credentials. CoreBase Cloud orchestrates the chat; rows still cross to the cloud over TLS but credentials never leave your network.

Self-hosted

Deploy CoreBase + CoreMCP inside your VPC. Rows stay in your network; the LLM call can be routed to a hosted provider or a model you run yourself.

Air-gap (Enterprise Container)

The whole stack — CoreBase, CoreMCP, and a local LLM — runs inside the customer perimeter. No outbound network. Raw rows physically cannot leave.
In every mode, anything CoreBase persists is encrypted per tenant and isolated at the database — see the storage table below.

​
What CoreBase sees — by deployment mode

​
Cloud-direct

When you paste a DSN into the panel: The connection is opened from our infrastructure using credentials you provide. CoreBase enforces read-only at the session level — the database itself refuses mutating SQL, no parser hack required. Credentials are encrypted per tenant before being stored. This is the fastest path. Use it when your buyer accepts “another SaaS vendor with database access” as part of their compliance model — the same posture you’d accept for any analytics or BI tool you’ve already onboarded.

​
Cloud-relay (CoreMCP-based)

When the orchestrator is CoreBase Cloud and a CoreMCP agent runs in your perimeter: Database credentials live on the CoreMCP agent and never reach our cloud. Connections originate inside your network. Rows still traverse the wire over TLS 1.2+ to reach the LLM. Anything CoreBase persists is encrypted per tenant. Use this mode when credentials staying on-prem is a hard requirement but rows in transit (under TLS) are acceptable.

​
Self-hosted

When you deploy the CoreBase Cloud component inside your own VPC:
  • Same protocol, same code
  • Rows stay inside your VPC — they reach your CoreBase pods, not ours
  • LLM call still goes to whichever provider you configure; for a fully internal model, point CoreBase at a self-hosted vLLM / Ollama / Together endpoint

​
Air-gap (Enterprise Container)

The strictest mode:
  • The entire stack — CoreMCP + CoreBase + a local LLM (Llama 3, Mistral, your choice) — runs inside your perimeter
  • Outbound network can be fully blocked
  • Raw rows physically cannot leave — there is no remote endpoint to send them to
For regulated industries — defense, healthcare, banking. Contact sales for the Enterprise Container bundle.

​
What’s stored on the orchestrator (any deployment with a cloud control plane)

​
Compliance posture summary

​
Verifying it yourself

CoreMCP is open source. Read the MCP request handlers — query execution is bounded to a small surface and readonly: true is the default on every source. For CoreBase Cloud, the encryption pipeline derives a per-tenant AES-GCM key from a master key and applies it to every persisted field with sensitive content. The cloud control plane is closed source; security architecture details are available under NDA — contact us if you’re evaluating for regulated use.

See the source

Audit the agent’s protocol, write your own driver, or vendor the binary into your release process.