Most vendors are strong at one layer and silent about the rest — a query engine with no model operations, a warehouse with no unstructured data, a storage platform that tells you to bring your own model. Here is the feature-by-feature breakdown against cloud platforms, hyperscalers and the on-premises field, sourced from publicly available documentation.
"Move all your data to Delta Lake."
Requires migrating your data estate to Delta Lake storage format and running on cloud compute.
"Move all your data to Snowflake SaaS."
Requires centralising data in Snowflake's cloud database on consumption-based pricing.
"Move all your workloads to OCI."
Encourages consolidating data and database engine licences inside Oracle Cloud Infrastructure.
"Move your business data to Datasphere."
Promotes funnelling enterprise data through the SAP Business Data Cloud ecosystem.
"Re-architect into our ontology."
Requires building enterprise data workflows inside Palantir's proprietary Foundry ontology.
"Why move the data at all?"
Leave your data where it lives. Federate intelligence, security and AI across all your existing systems.
| Capability | Nexaris | Databricks | Snowflake | Oracle | SAP BDC | Palantir |
|---|---|---|---|---|---|---|
| Core philosophy | ||||||
| Data strategy | Leave in place | Move to Databricks | Move to Snowflake | Move to Oracle | Move to SAP | Ontology-centric |
| Vendor neutrality | High | Moderate | Moderate | Low | Low | Low |
| Works with existing investments | Amplifies all | Replaces many | Replaces many | Oracle-preferred | SAP-preferred | Bypasses existing |
| Deployment & infrastructure | ||||||
| On-premises — native | Yes | Limited | — | Yes | Yes | Yes |
| Air-gapped / sovereign / classified | Native | — | — | Limited | Limited | Yes |
| Edge deployment | Yes | — | — | Limited | Limited | Limited |
| Data architecture | ||||||
| No data movement required | Always | Typically required | Typically required | Typically required | Encouraged | Partial |
| Open formats (Iceberg / Delta / Parquet) | Yes | Delta-preferred | Partial | Oracle formats | SAP formats | Proprietary |
| Real-time federated access | Yes | After movement | After replication | OCI-centric | SAP-centric | Partial |
| AI & machine learning | ||||||
| AI / ML studio built in | Wa-Sul | Yes | Cortex only | Yes | Joule | AIP |
| AI works across all systems & data | Yes | Databricks data | Snowflake data | Oracle data | SAP data best | Palantir ecosystem |
| Cost structure | ||||||
| Predictable non-consumption licensing | Yes | Consumption | Consumption | Tiered + licensing | Enterprise licence | Large contracts |
| No mandatory data migration cost | Yes | — | — | — | — | Partial |
Based on publicly available documentation 2025–2026. Contact us to validate specifics for your environment.
| Capability | Nexaris | Azure / GCP / AWS | Cloudera | Confluent + IBM | Infrastructure platforms |
|---|---|---|---|---|---|
| Architecture & connectivity | |||||
| Multi-cloud native orchestration | Yes | Single-cloud bias | Yes | Event-centric | Hardware-bound |
| Zero data movement federation | Yes | — | Partial | Streaming only | — |
| Air-gapped deployment parity | Yes | — | Yes | Partial | Yes |
| Governance & AI integration | |||||
| Unified Zero Trust policy engine | Guardiuum | Cloud IAM | Ranger | Tool-specific | Partner dependent |
| Native AI & RAG workflow studio | Wa-Sul | Cloud ML APIs | CML | — | Partner dependent |
The three platforms most often shortlisted alongside Nexaris for data that will never leave the building. Every cell below is sourced from vendor documentation — references are listed under the table.
| Capability | Nexaris iiDrak | Starburst Enterprise | Dell AI Data Platform | Cloudera (Base on prem) |
|---|---|---|---|---|
| Deployment & footprint | ||||
| Runs fully on-premises | Yes | Yes — self-managed1 | Yes | Yes7 |
| Hardware independence | Any x86 / GPU estate, mixed vendors | Hadoop or object store — MinIO, Dell ECS1 | Dell PowerScale, ObjectScale, PowerEdge4 | Commodity clusters per reference architecture8 |
| Single vendor for the whole stack | Yes — five first-party products | Query engine only | Dell + Starburst + Elastic + NVIDIA4,5,6 | Yes — ~50 OSS projects packaged7 |
| Kubernetes-native operations | Yes | Yes, for autoscaling1 | Yes — Data Engines Foundation4 | Data Services on K8s; Base is YARN-lineage7 |
| Data access | ||||
| Query in place, no movement | Yes | Yes — core strength2 | Yes — via Starburst5 | Partial — data lands in the cluster9 |
| Connectors | 150+ pre-built | 40+ on prem, 50+ claimed1,2 | Inherits Starburst connectors5 | Runtime ecosystem + NiFi |
| Unstructured data & vectors | Native — Guardiuum governs vector stores | Not addressed1 | Yes — Elastic search engine4 | Via add-on services |
| Open table formats | Iceberg, Delta | Iceberg2 | Iceberg v3, Delta; Parquet / Avro / ORC4 | Iceberg, Hive, HBase7 |
| Governance | ||||
| Fine-grained access control & masking | Guardiuum policy engine | Yes3 | Per-engine | Apache Ranger7 |
| One policy plane across every engine | Yes | Engine scope only | Per-engine, four vendors4 | Ranger across Runtime services |
| Plain-English policy preview | Yes | — | — | — |
| Regulation mapping — GDPR, HIPAA, SOX, CCPA | Built in | — | — | Via Atlas tagging |
| AI lifecycle | ||||
| Experiment tracking & model registry | AI Factory | Not addressed1 | Bring your own model4 | Cloudera AI |
| Model serving & deployment | AI Factory — Models & Deploy | Not addressed1 | No deployment infrastructure4 | AI Inference with NVIDIA NIM10 |
| On-prem GenAI inference maturity | Generally available | — | Partner supplied | Technical preview, Aug 202511 |
| Guardrails & AI compliance ledger | Guardrails Hub + Compliance | — | — | — |
| Low-code AI app studio | Wa-Sul AI Studio | — | — | — |
| Human annotation workflow | Annotation Studio | — | — | — |
| Catalog | ||||
| Federated catalog across all sources | Data Catalog | Engine metadata | Built-in metastore4 | Apache Atlas7 |
| Ontology explorer | Yes | — | — | — |
| Data quality, incidents, observability | Built in | Query monitoring3 | Platform metrics4 | Via add-on services |
Federated SQL at scale.
Enterprise-hardened Trino is the best-known federation engine there is, with a mature optimiser, caching and audit. If all you need is one SQL surface over many sources, it does that extremely well. Nexaris differs in scope rather than in that claim — Starburst stops at query consumption, so model operations, app building, annotation and a federated catalog come from other vendors.
Storage and throughput engineering.
PowerScale and ObjectScale are exceptional at feeding GPUs, and the Kubernetes lifecycle layer makes the rack turnkey. The trade-offs are vendor count and coupling: the analytics, search and acceleration layers come from Starburst, Elastic and NVIDIA, so governance is per-engine, and the platform assumes Dell hardware. Nexaris is software that runs on the estate already racked, Dell included.
The regulated data centre.
Two decades of Hadoop-lineage operations, Ranger and Atlas, and a real private-AI push with NVIDIA NIM. The trade-offs are operational surface — roughly fifty open-source projects to run — and that the platform is a destination: data lands in the cluster. On-premises GenAI inference reached technical preview in August 2025.
Nexaris doesn't replace your lakehouse investment — it federates intelligence across it. Keep running your existing Databricks jobs while extending AI and governance to the data that can't be moved into the lakehouse: on-premises systems, regulated workloads, SAP, Oracle and air-gapped environments.
Snowflake is excellent for cloud data warehousing, and it is a destination — data has to live inside it. Nexaris lets Snowflake remain part of a broader ecosystem, connecting it in real time to SAP, Oracle, Epic and Salesforce without replication, and governing all of those sources under one policy engine.
Starburst is the best-known federated SQL engine there is and we do not pretend otherwise. The difference is scope. Starburst ends at query consumption — its own on-premises product page describes a “data consumption layer” and makes no mention of model training, model serving, guardrails or unstructured data. With Nexaris, federation is one capability inside five products on one control plane: AI Factory covers experiments, registry, deployment, guardrails and a compliance ledger; Wa-Sul AI Studio covers low-code AI apps and annotation; Data Catalog covers ontology and observability; Guardiuum governs all of them under a single policy engine. A Starburst buyer assembles those from other vendors.
Dell’s storage engineering is excellent and PowerScale and ObjectScale feed GPUs about as well as anything on the market — if you are buying a rack, it is a serious option. Two structural differences are worth knowing. First, AIDP is assembled from four vendors: Dell for storage, compute and lifecycle, Starburst for analytics, Elastic for search and vectors, NVIDIA for acceleration — so governance is per-engine rather than one plane. Second, it assumes Dell hardware. Nexaris is software that runs on the estate you already have, Dell hardware included, and Dell’s own technical overview describes model use as bring-your-own-model with no deployment infrastructure — which is precisely what AI Factory provides.
Cloudera is the incumbent in the regulated data centre and its private-AI push with NVIDIA NIM is real. Two things change. Operationally, Cloudera Runtime packages roughly fifty open-source projects for your team to run; Nexaris is five products with one console. Architecturally, Cloudera is a destination — data lands in the cluster — whereas Nexaris queries sources where they already are, including the Cloudera cluster itself. On timing: Cloudera’s on-premises GenAI inference reached technical preview with Data Services 1.5.5 in August 2025. You do not have to decommission Cloudera to start; most customers connect it as a source.
Yes. Spark engineers still write Spark, dbt developers still use dbt, Tableau analysts still open Tableau. Nexaris sits above your tools and connects what your team builds into a governed, AI-ready layer — your team keeps every skill it already has.
Partner-led platform licensing rather than consumption billing. You are not charged extra for querying data or for egress, so your enterprise data budget is predictable year over year rather than scaling with data volume.
Air-gapped deployment is a first-class mode with full feature parity — no call-home, no cloud control plane and no reduced capability set. See Security & compliance for the architecture detail.
No. Nexaris takes the position that the customer, not the vendor, should be the centre of the architecture. Those systems stay exactly where they are and Nexaris adds the intelligence and governance layer above them. See Switching platforms.