AetherLake vs OpenLake

AetherLake is a Kubernetes-native data lakehouse that brings storage, catalog, federated SQL, streaming, orchestration, BI, and identity into a web control panel. Its stack includes MinIO, Trino, Apache Polaris, Kafka, Flink, dbt, Airflow, Superset, Spark, Milvus, Prometheus, Grafana, PostgreSQL, and Keycloak. The panel shows pod health and resource use, supports service restarts, and provides workspaces for dbt, Kafka, Flink SQL, Trino queries, and Iceberg catalogs. Kafka and Flink are enabled by default; project examples describe streaming Kafka data into Iceberg tables and querying topics through Trino. Keycloak supplies OIDC single sign-on across services, with data-admin, data-scientist, and data-engineer roles. Deployment prerequisites include Kubernetes, Helm 3.12 or later, kubectl, Docker, and an NGINX ingress controller. Deployment materials cover AWS, Azure, and Google Cloud. An MCP server gives AI assistants access to platform status, logs and restarts, Trino queries, Polaris catalogs, and Airflow DAGs. The control panel is bilingual in English and Turkish. Internal, evaluation, development, testing, and non-commercial use is free; commercial use requires a separate license.

OpenLake is a managed data lakehouse platform deployed in a customer’s cloud account, with API, self-hosted, and web access. It combines Trino, Apache Spark, Apache Iceberg, Apache Polaris, Apache Superset, PostgreSQL, Neo4j, Elasticsearch, and Polars. Its browser SQL workbench uses Trino and can draft queries from natural-language prompts grounded in readable catalogs. Teams can schedule and monitor ETL jobs written in Spark, Polars, Python, or Bash, including work on temporary Spark clusters. Analysts can launch preconfigured cloud workstations through a browser or native client over a secure tunnel without public exposure. OpenLake connects Tableau, Power BI, databases, APIs, S3 feeds, and files. It describes SSO with enforced MFA, role-based permissions, managed secrets, network isolation, and audit logs. Deployments can use customer-owned buckets, open Iceberg tables, streaming ingestion, governance catalogs, and offline artifacts in networks without internet egress. AI cataloging, natural-language querying, and incident-triage proposals are included. Pricing is on request.