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.
Kauzas Data & AI 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.
- Kubernetes-based
- Open source fit for enterprise use
- Runs on a closed network
Product catalogue
13/13 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
DetailsWhere 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
- 01Part of the query may be planned on the provider's infrastructure.
- 02Query results may pass through the provider's serving layers.
Control boundary
- 03Data or query results may leave the organization's control domain.
The data path is not fully under the organization's control.
Kauzas
- 01The query runs on the organization's own infrastructure.
- 02Results pass through the organization's own serving layer.
- 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.
- 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.
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 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 sub-second serving layer beside the lake. It installs as a SQL catalog too, so hot and cold data join in one query. Scale out with shards, survive a node with replicas.
- Prerequisite technology
- Kauzas SQL
Serving
Kauzas BI
Apache Superset
Dashboards and charts over the platform's own SQL front door. Every chart query is a governed query: it runs through Kauzas SQL, with grants, row filters, masks and the access log applying exactly as they do for a laptop tool.
- Prerequisite technology
- Kauzas SQL
Governance
Kauzas Governance
Kauzas Mesh · Cedar
Governs the data mesh: domain access control (open or restricted), need-to-know membership and native lineage, enforced by Cedar. Without it the mesh is flat and everything is discoverable.
Governance
Kauzas Metadata Engine
OpenMetadata
Metadata discovery, tag curation and lineage. It feeds the platform's own mirror; authorization decisions never depend on it and the mesh works without it. An opt-in layer, not a tax.
- Prerequisite technology
- Kauzas Governance
Governance
Kauzas SSO
OIDC Federation
Integrates with the organization's existing identity provider. User and group information is mapped onto Kauzas permissions, and local accounts keep working, because SSO is added alongside them rather than instead of them.
AI
Kauzas AI
Model endpoint · Connection
An assistant beside every screen and in the SQL editor. It speaks to a language model you register under Connections: an endpoint of your own or a hosted provider. It sees what the person sees, writes into the editor, opens pages and explains — and runs nothing itself; the person does.
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.
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
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
DefaultFor 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
Platform licence from$10,000 a year
Kauzas is not licensed per user or by infrastructure consumption. The final licence scope is set against the platform architecture, the independent deployments, the continuity requirements and the scope of operations.
Kauzas can bring environments as different as AWS Local Zone Istanbul, an organisation's own data centre, private cloud and external GPU estates together under one data and AI architecture.
What the model means
Unlimited users
Kauzas is not licensed per user. As adoption spreads across the organisation, no per-user licence cost appears.
Infrastructure freedom
AWS Local Zone Istanbul, AWS, on-prem, private cloud and separate compute/GPU estates can all sit inside one architecture.
Predictable licensing
CPU, GPU, storage, query or token consumption does not determine the Kauzas platform licence.
Grow and combine your infrastructure however you like.
Kauzas charges no usage fee on users, CPU, GPU, storage, queries or tokens. Choose the infrastructure you need and run it together under one platform architecture.
The licence covers the platform and management scope defined at the quotation stage.
Build my Kauzas architecture
Choose where the platform will run, which lifecycle environments you need and which operational services matter. We will shape your Kauzas scope around those choices.
Your Kauzas scope
Licences start at $10,000 / year
Work through the steps; the scope summary appears at the end.
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
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