Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.cloud.cdata.com/llms.txt

Use this file to discover all available pages before exploring further.

What Connect Gateway Does

For customers whose critical data lives on-premises—in databases, file systems, or internal applications—Connect Gateway provides the same live query access that cloud-connected sources receive, without requiring data to transit to the cloud first.
  • No data replication: queries run directly against the on-premises source
  • No ETL pipelines: data is accessed live at query time
  • Data never persists outside the firewall
  • The same MCP tools and relational interface used for cloud sources apply to on-premises sources through the gateway

What Connect Gateway Does Not Do

Connect Gateway addresses firewall access—it enables connectivity to sources that are not publicly reachable. It does not address data residency or regional hosting requirements. Organizations with strict requirements about where data may transit, even transiently, should evaluate their compliance requirements separately. Certified sources (Q1 2026 release)
  • Databricks
  • PostgreSQL
  • MySQL
  • SAP Gateway (any version supported by the SAP NetWeaver Connector)
  • Snowflake
  • SQL Server
Additional sources are being added. The following are planned for upcoming releases: Apache Hive, API, CockroachDB, Couchbase, Databricks Lakebase, ElasticSearch, MariaDB, MongoDB, Neo4j, OData, Odoo, and Presto. To request a source not on this list, contact CData. The typical turnaround is within one month.

Connect Gateway Setup

1
Contact CData to enable Connect Gateway for your parent account.
2
Download the Connect Gateway installer and deploy it within your customer’s network.
3
Configure the gateway to connect to the on-premises data source.
4
Register the gateway connection in the Connect AI Embed sub-account.
5
Test the connection and begin querying through MCP.