Lakehouse architecture
Can Snowflake run on-premise or air-gapped? The answer, and what to use instead
No. Snowflake runs only in Snowflake-operated accounts on AWS, Azure and Google Cloud. There is no on-premises, bare-metal or air-gapped edition, and Virtual Private Snowflake is dedicated but still operated by Snowflake. Snowflake can query external tables on S3-compatible storage you run, but compute, metadata and results stay in Snowflake's cloud.
Published . Last updated
On this page
Snowflake made the data warehouse easy to adopt by removing infrastructure from the customer's hands entirely. That is also why it cannot follow your data into your own data centre. This guide sets out what Snowflake's deployment options do, where their limits sit for sovereignty, and how teams build a Snowflake-style experience on infrastructure they control.
Is there an on-premises version of Snowflake?
No. Snowflake is software-as-a-service by design. Compute (virtual warehouses), storage, metadata and the cloud services layer all run in Snowflake-operated accounts on AWS, Azure or Google Cloud. Snowflake has not released a self-hosted, bare-metal or disconnected edition.
Does Virtual Private Snowflake count as self-hosted?
No. Virtual Private Snowflake (VPS) is Snowflake's highest isolation tier: a dedicated environment with its own metadata store and compute, not shared with other accounts. It is still provisioned and operated by Snowflake in a public cloud. It answers "can we avoid sharing infrastructure with other customers?" It does not answer "can it run inside our perimeter?"
What about external tables on my own storage?
Snowflake can read data that sits in S3-compatible object storage you operate, including on-premises storage appliances that pass Snowflake's compatibility tests. The data at rest stays with you. But queries run on Snowflake compute, metadata about those tables lives in Snowflake, and results are returned through Snowflake's cloud. If your policy says data may not be processed outside your boundary, querying it from Snowflake does not satisfy that policy.
How do Snowflake's options compare for sovereignty?
| Option | Data at rest | Compute | Metadata and control | Air-gapped? |
|---|---|---|---|---|
| Standard Snowflake account | Snowflake's cloud | Snowflake's cloud | Snowflake | No |
| Virtual Private Snowflake | Dedicated, Snowflake-operated | Dedicated, Snowflake-operated | Snowflake | No |
| External tables on your storage | Your storage | Snowflake's cloud | Snowflake | No |
| Iceberg tables with an external catalog | Your cloud storage | Snowflake's cloud | Shared | No |
| DataNature on-premises | Your storage | Your hardware | Your deployment | Yes, if required |
Which Snowflake features have an open, self-hostable equivalent?
| Snowflake capability | DataNature equivalent | Open technology |
|---|---|---|
| Virtual warehouses | Interactive SQL and serving compute | Trino, DN Warehouse |
| Native tables, Iceberg tables | Lakehouse tables | Apache Iceberg |
| Snowpipe and connectors | Connect and StreamHouse | JDBC extraction; managed Kafka with CDC for the real-time hot path |
| Dynamic tables, tasks | dbt models and DataNature Jobs | dbt on Spark or Trino, scheduled job DAGs |
| Row access and masking policies | Atlas row filters and column masks | Policies enforced in Trino and the warehouse |
| Horizon catalog | Atlas catalog and lineage | DataHub-based catalog, dbt artifacts |
| Semantic views, Cortex Analyst | Atlas semantic models and Voir | YAML cubes over REST and MCP, governed agents |
| Snowpark Container Services | Apps on the DataNature Platform | Kubernetes |
| Hybrid tables | Lakebase | Managed PostgreSQL |
| Time travel | Iceberg snapshots | Apache Iceberg time travel |
How do masking policies translate?
Snowflake masking policies are SQL functions attached to columns. In DataNature, an admin chooses a mask type per column and per user or group in the Atlas Data Governance console: null, redact, show first four, show last four, hash, year only, or exempt. Hash masks are consistent, so a masked customer ID still joins across tables. Row access policies become row filters: a SQL predicate such as region = 'ON' applied to a user or group. Both take effect within about a minute and apply to the SQL workbench, JDBC clients, cubes and impersonating Superset connections.
What does migrating off Snowflake look like?
- Export tables to Parquet or Iceberg in object storage, or land source systems directly into Bronze through Connect.
- Translate SQL. Most ANSI SQL runs on Trino unchanged. Snowflake-specific functions (
FLATTEN,VARIANThandling,QUALIFYusage, stored procedures) need rewriting; dbt projects move by changing the adapter target. - Rebuild governance as Atlas grants, row filters and masks, scoped to specific schemas.
- Repoint BI. Superset, Power BI and Tableau connect to the lakehouse or warehouse; keep impersonation on so per-user rules apply.
- Reconcile and cut over domain by domain, comparing Gold metrics per period.
Frequently asked questions
Can Snowflake run in a private cloud I operate?
No. Snowflake only runs in Snowflake-operated accounts on supported public clouds.
Is Snowflake's Iceberg support a path to on-premises?
It makes your data portable, which helps, but Snowflake compute and services still run in Snowflake's cloud. Running the engines yourself is what moves processing on-premises.
Can DataNature and Snowflake share data?
Yes. Iceberg tables in shared object storage can be read by both, subject to your governance and residency rules.
Sources
Platform components in this article
Learn more about each DataNature product and module mentioned here.
Products
Platform modules
- LakehouseOpen tables in storage you control
- AtlasGovernance for data and AI in one console
- ComputeSpark and SQL engines, sized for the job
- BIDashboards on governed data
- StreamHouseReal-time data on the same tables
- ConnectEvery source, one governed landing zone
- Data Engineeringdbt and Spark, Bronze to Gold
- LakebasePostgres on the lakehouse, no ETL
See it on your own data.
Book a demoDemos and quotes are handled by Dlytica, the company behind DataNature.