Skip to content
TRRequest a demo

Kauzas Data Platform

Your data never leaves this frame.

Kauzas moves modern data and AI infrastructure into the organization's own control domain. Its Kubernetes-based architecture runs lakehouse, data mesh and AI workloads in AWS Local Zone İstanbul, the data center of your choice, or on-prem — leaving control of data, governance and infrastructure with the organization.

Request a demoSee the architecture
  • Kubernetes-based
  • Open source fit for enterprise use
  • Runs on a closed network

Product catalogue

11/11 products installed

kauzas core

control plane · always installed

  • Console
  • API / BFF
  • Cedar
  • Operator
  • State database

The components you select are brought up wired to work together. Each one can be versioned, licensed and switched off on its own.

Data sovereignty

Where data is processed matters as much as where it is stored.

In modern data platforms, data is not merely stored — it is queried, processed and served to applications. Real data sovereignty therefore requires that the query, processing and serving layers stay under the organization's control alongside the storage layer.

Central SaaS architecture

  1. 01Part of the query may be planned on the provider's infrastructure.
  2. 02Query results may pass through the provider's serving layers.
Control boundary
  1. 03Data or query results may leave the organization's control domain.

The data path is not fully under the organization's control.

Kauzas

  1. 01The query runs on the organization's own infrastructure.
  2. 02Results pass through the organization's own serving layer.
  3. 03Data reaches only the authorized user, over a data path the organization controls.
Control boundary

The data path stays under the organization's control.

With Kauzas, data sovereignty is preserved not only at the storage layer but across the entire data flow.

Layered stack

Enterprise value lies in bringing accessible technologies together in a single, scalable architecture.

Kauzas unifies proven open technologies, the ones run by the companies that lead their industries, into a single data and AI platform. Every layer is independent and replaceable, so the organization is never tied to a single technology or vendor.

  1. L1

    Control plane

    Experience, API, orchestration brain

    • L2

      Serving and query

      Interactive SQL, hot serving, batch

      • Trino — federation
      • ClickHouse — hot tier
      • Spark on K8s — batch
    • L3

      Ingestion and pipelines

      Data in, transform, schedule

      • NiFi · Debezium
      • Airflow
      • dbt
    • L4

      Catalog and governance

      Technical catalog, discovery, lineage

      • Iceberg REST → Polaris
      • OpenMetadata
      • OpenLineage
    • L5

      Table format

      Table semantics

      • Iceberg — native
      • Delta · Hudi — interop
      • Hive — compatibility
    • L6

      Storage

      Physical bytes

      • S3 API — one interface
      • External connections — PostgreSQL · SQL Server
      • NAS — via gateway

    Products

    Infrastructure grows with the need, and carries nothing beyond it.

    Kauzas starts with the management layer alone. Data and AI services are brought online as they are needed, so the organization allocates resources only for the components it actually uses — and can scale and manage each one independently.

    Platform products and user resource

    Platform products

    The base component an administrator adds to the platform and manages centrally. It is installed, configured, updated and switched off when it is no longer needed.

    User resource

    A working environment a user creates on the platform — a SQL warehouse, a notebook or a Spark job.

    Storage

    Kauzas Object Storage

    MinIO · S3 / S3-compatible

    An S3-compatible object storage layer for table data and files. It connects to whichever storage technology you prefer: S3, MinIO, NAS or any other S3-compatible system.

    Catalog

    Kauzas Catalog

    Iceberg REST → Polaris

    Manages table metadata centrally. Its Iceberg REST and PostgreSQL-backed catalog gives query and compute engines one shared catalog to reach the data through.

    Prerequisite technology
    Kauzas Object Storage

    Query

    Kauzas SQL

    Trino

    A distributed SQL query layer. It can query existing sources such as PostgreSQL and SQL Server directly, and together with Kauzas Catalog it reaches lakehouse data through the same query experience.

    Recommended technology
    Kauzas Object Storage · Kauzas Catalog

    Compute

    Kauzas Notebooks

    Jupyter · IPython

    Notebooks are kept durably in object storage. Work is preserved even when compute resources are shut down, and the compute you need can be brought up later.

    Compute

    Cluster-scoped grant

    Kauzas Spark

    Spark on Kubernetes

    Scalable Spark infrastructure for batch data processing and ETL. Workloads are created on demand, and because the user's identity is carried through, running jobs can be traced and audited per person.

    Serving

    Kauzas Hot Tier

    ClickHouse · Altinity Operator

    A high-performance query layer for dashboards and applications. With ClickHouse, the query performance served to users is optimised independently of lakehouse access speed.

    Pipelines

    Kauzas Orchestration

    Apache Airflow 2.10

    Schedule data jobs, manage their dependencies and orchestrate processes. Airflow runs underneath while day-to-day management happens in the Kauzas interface.

    Pipelines

    Cluster-scoped grant

    Kauzas Events

    Argo Events + NATS

    Starts workflows automatically from data arrivals and system events. An S3 upload, a webhook or a Kafka message can trigger a new process.

    Governance

    Kauzas Governance

    Kauzas Mesh · OpenLineage

    Manages domain-level data access, user permissions and data lineage centrally. Authorization policies are enforced through Cedar; data movement is traceable with OpenLineage.

    Governance

    Kauzas SSO

    OIDC Federation

    Integrates with the organization's existing identity provider. User and group information is mapped onto Kauzas permissions, and controlled local accounts remain available when needed.

    Observability

    Kauzas Monitoring

    Prometheus + Grafana

    Resource use, job runs, system health and audit activity are monitored from one place. Grafana dashboards are reachable directly from the Kauzas console.

    See the product catalogue live

    Let us show how Kauzas components are brought up and how they work together, against your organization's own requirements.

    Request a demo

    The console

    The whole platform is managed from one place.

    The Kauzas console brings every platform operation into a single interface — from putting products into service to running queries, from authorization to managing compute resources. An administrator brings up the components they need from here; prerequisite technologies, recommended components and install state are shown plainly on every card.

    kauzas.kurum.local
    Products

    Simple management, backed by strong orchestration.

    Kauzas does not merely switch on the components you select; it also manages the dependencies and integrations between them. Governance, query engines, orchestration and the other services are wired to one another as they are needed, and both install-time and runtime relationships are handled by the platform. Each component therefore stops being a service that runs on its own and becomes a managed, interoperating layer of the platform.

    Trust

    Auditability is part of the architecture.

    In Kauzas, authorization changes, product installs and system activity are all recorded. Every action is traceable and verifiable, so the organization can see who did what, and when.

    Traceable audit chain

    Each audit record is linked to the one before it. Any change to a record breaks the integrity of the chain and becomes visible.

    Traceable audit chain

    Chain intact

    Click a row — every hash after it becomes invalid.

    Authorization

    Permissions are managed by policy, not by role.

    In Kauzas, access rights are not defined by fixed roles baked into application code. Who may reach which data, product or compute resource, and under what conditions, is decided by central policies. Permissions can therefore be managed, audited and defined in fine detail without a code change.

    cedar policy

    permit(
  principal in Group::"data-engineers",
  action  == Action::"UseCompute",
  resource
)
when { resource.access == "public" };

    Authorization is enforced in the foundation of the system, not in the interface.

    Access controls do not stop at hiding screens; they are enforced on the server. A user can reach only the data and resources they are authorized for.

    Security

    Sensitive data is never stored in plain text.

    Connection details, access keys and SSO secrets are stored encrypted. Sensitive values are handled securely in both development and production, and are never written in the clear into application code or the database.

    Closed network

    It can run with no internet access.

    Kauzas can be installed and operated on closed networks with no external internet access. The packages and components it needs come from the organization's own controlled sources, and it depends on no external service at runtime.

    Licensing

    Open-source licences fit for enterprise use.

    Kauzas components are chosen from licences suitable for enterprise distribution and commercial use. Licence compliance is checked at the platform level, so the organization is not exposed to licence risk after the fact.

    Management

    One platform, consistent management.

    Infrastructure changes go through GitOps, while day-to-day operations are handled from the Kauzas console. Both paths resolve to the same platform state, so configuration stays consistent, traceable and reversible when needed.

    Data integrity

    Every kind of data lives in the layer it belongs to.

    Configuration lives in Git, application state in the database, runtime in Kubernetes, and durable data in object storage. Every piece of information therefore has one definite source, and restarting a service leaves durable data untouched.

    Identity

    Enterprise identity management, resilient to outages.

    Kauzas connects to the organization's existing identity provider over OIDC and maps user groups onto platform permissions. When the provider is unreachable, controlled local administrator accounts keep operations running.

    Runtime environment

    The infrastructure can change; the platform does not.

    Kauzas runs the same Kubernetes architecture on AWS, on VMware and on physical on-prem infrastructure. The platform's operating model therefore does not change with the infrastructure: the organization picks the environment that suits it and stays free of any single cloud provider.

    What changes is the infrastructure; the platform architecture stays the same. Karpenter on AWS, Cluster API on VMware, and the existing server pool on physical infrastructure.

    Scaling per infrastructure

    • AWS

      Karpenter

      Kubernetes nodes are brought up as demand requires, and capacity is reduced automatically when unused.

    • VMware

      Cluster API (CAPV)

      Virtual machines are provisioned and managed automatically as Kubernetes nodes.

    • Physical infrastructure

      Existing server pool

      Kubernetes runs on the servers already in place; workloads scale at the pod level as needed.

    Operating model

    • A

      Fully in-house

      Default

      For environments that demand the highest level of control and data sovereignty. Both the management and the data layers run entirely on the organization's own infrastructure.

      Control plane
      In-house
      Data plane
      In-house
    • B

      Managed control plane

      Kauzas operates the management layer while data and workloads stay on the organization's own infrastructure — managed-service convenience together with control of the data.

      Control plane
      Novadsa / Kauzas
      Data plane
      In-house
    • C

      Central management, distributed sites

      For organizations with several locations or facilities: management is centralized while data and workloads stay at the sites where they live.

      Control plane
      Central in-house infrastructure
      Data plane
      At the organization's sites

    Pricing

    Pay for the platform.Keep your infrastructure under your own control.

    Kauzas is offered as an annual platform licence. Compute, storage and network resources run on the organization's own infrastructure or on the cloud provider it prefers.

    Kauzas adds no margin on top of your infrastructure cost.

    Kauzas is licensed per platform, not per user.

    Licence and infrastructure

    Annual subscription

    Kauzas platform licence

    The Kauzas platform, the product catalogue, governance, orchestration, monitoring, SSO, updates and standard support all come under a single licence.

    What sets the price

    • Scale of the infrastructure under management
    • Number of production environments
    • Number of locations / clusters
    • Support level
    • Closed-network and special deployment requirements

    Directly under your control

    Your infrastructure

    • AWS
    • AWS Local Zone
    • VMware
    • Private cloud
    • Physical servers

    Compute, storage and network costs are paid directly by the organization.

    Kauzas takes no share and adds no fee on top of those costs.

    What the model means

    No surprise usage bill.

    The licence cost is separate from platform usage. Running more SQL queries, more Spark jobs or more notebooks is not billed by Kauzas on a usage basis. Your infrastructure cost is only the real cost of the infrastructure you chose.

    Evaluate it in your own environment first.

    Kauzas can be evaluated over an 8–12 week pilot, on your own infrastructure and against your real use case. During the pilot the install, the core integration and an agreed use case are delivered together.

    If you move to an annual licence, the pilot fee is deducted from the first year.

    Plan a pilot

    Scale it to what you need.

    The Kauzas licence is set by the scale of the enterprise infrastructure the platform manages, not by the number of users. The same platform architecture serves a single small production environment and a multi-site estate alike.

    Let us set the licence level for your organization together.

    Request a quote

    Frequently asked questions

    Is infrastructure included in the licence?
    No. Kauzas runs on your existing or preferred infrastructure.
    Is there a per-user fee?
    No.
    Are SQL, Spark or Notebook usage billed separately?
    Not by Kauzas. The compute cost that arises belongs directly to your own infrastructure.
    Are all Kauzas components included in the licence?
    Yes. Licence levels differ by infrastructure scale and operating requirements rather than by withholding features.
    Are on-prem and closed-network installs possible?
    Yes.
    Is a pilot possible?
    Yes. An 8–12 week pilot programme is offered, and if you move to an annual licence the pilot fee is credited against the first year.

    Get in touch for details or for a quote shaped around what you need.

    Get in touch

    Get in touch

    Would you like to see how Kauzas would work in your organization?

    Let's go through your current infrastructure, your data needs and your use cases together, and show you how Kauzas would fit your organization and which components would create value.

    Contact us directly:info@novadsa.com

    Contact