Home / Governance and security

Built to pass your security review, not to fight it.

Discovery reads your warehouse read-only, and Semantics builds its dbt models into its own ekai schema, separate from your source tables. Run ekai self-hosted, as ekai SaaS or as a Snowflake Native App, listed on the Snowflake Marketplace. Your raw rows never leave your warehouse, AI traffic can route through your own endpoints, and ekai's SOC 2 Type II audit found zero exceptions.

Book a demo Request the SOC 2 report

Discovery › Sales warehouseOwner: FN

Connection DetailsOnboardingSchema & Relationships

Sales warehouse5 tables linked · 2 context files · Modified 20 Oct 2026

Direct modeView Connection Parameters

Tables · Link the tables you choose · 5 linkedSALES 48CRM 112REF 23FINANCE 64MARKETING 89OPS 156PRODUCT 71LEGACY 204SANDBOX 517

Data Profile · SALES.ORDERSView Profile

ColumnData typeNullsDistinctFlags

ORDER_IDnumber0%48,201,663primary key

CUSTOMER_IDnumber0%3,114,908joins CRM.CUSTOMERS

ORDER_DATEdate0%5,113

AMOUNTnumber0%41,882,004gross or net? undeclared

TAXnumber0%2,214,880

DISCOUNTnumber12.4%998,12012.4% null

REGION_CODEtext0%412joins REF.REGIONS

← Data SourcesOnboarding →

ekai product · demo data

What runs where?

Your raw rows stay in your warehouse.

Where each piece runs

Your warehouseSnowflake, Databricks, BigQuery and more

ekaiSelf-hosted, ekai SaaS or Snowflake Native App

Your GitGitHub, GitLab or Bitbucket

Your LLM endpointsOptional private routing through Vertex AI, Azure OpenAI or AWS Bedrock

Raw rows never leave your warehouse

Deploy where it fits

Self-hosted, ekai SaaS or a Snowflake Native App, listed on the Snowflake Marketplace.

Raw rows stay put

Profiling runs in place, and the dbt models are built inside your own warehouse.

Your LLM endpoints

Multi-LLM by design, with optional private routing through Vertex AI, Azure OpenAI or AWS Bedrock.

Warehouse neutral

Snowflake, Databricks, BigQuery and more.

Git native by default

GitHub, GitLab or Bitbucket.

Open, portable artifacts

Use ekai to build them and keep them for good.

Is ekai SOC 2 Type II compliant?

Yes, with zero exceptions across every control tested. The audit was conducted by Johanson Group, an independent CPA firm.

Read the announcement

AICPA SOC for Service Organizations seal

0exceptions

Type IItested over time

CPAindependent audit

Does ekai lock you into a platform?

No. Everything ekai builds is standard and lives in your Git, yours to keep on any warehouse.

Semantics › Sales and revenueOwner: FN

Model DetailsBusiness RequirementsAI ModelingData TransformationCode Sync

IntegrationsPush to Git

Configure Git Integration

Connect a single code repository to enable push and sync capabilities for this semantic model.

GitHub AppGithub App

GitLabProject Access Token

BitBucketProject Access Token

GitHub PATPersonal Access Token

← Data Transformation

Code SyncYour Git, your artifacts

Common questions

Last updated October 28, 2026

Does ekai move or copy my data?

No. Discovery profiles your tables in place, and the dbt models are built inside your own warehouse, in an ekai schema, separate from your source tables. Your raw rows never leave your warehouse; ekai works from metadata and statistical summaries.

Where does ekai run?

Self-hosted, as ekai SaaS or as a Snowflake Native App, listed on the Snowflake Marketplace. Discovery reads only, Semantics writes its dbt models to its own ekai schema, separate from your source tables, and your raw rows stay in your warehouse.

Is my data safe with ekai?

Yes. Discovery reads only, ekai never edits your source tables, and your raw rows never leave your warehouse. AI traffic can route through your own endpoints, your data is never used to train models, and ekai's SOC 2 Type II audit found zero exceptions.

Is ekai SOC 2 compliant?

Yes, SOC 2 Type II. Request the report from the team, or read the announcement for what the audit covered.