Dawiso can run in your own Kubernetes cluster instead of the Dawiso cloud. This page describes the environment that a self-hosted Dawiso needs. It applies to the latest release that Dawiso makes available to self-hosted customers. Dawiso agreements for self-hosted deployment refer to this page as the Supported Environment.
The step-by-step installation documentation is available to customers after the agreement is signed. It also lists the exact supported versions of the platforms below.
What Dawiso delivers
Dawiso delivers the container images and the Helm chart of the platform from its container registry, and an installation repository with the release files and the installation documentation. You receive access to both after signing.
| Component | What it does |
|---|---|
| Dawiso Core | The data catalog your users work in. |
| Data Ingestion | Reads metadata from your data sources into Dawiso. |
| Identity | Sign-in, users, licences and multi-factor authentication for the Dawiso platform. |
| Dawiso Access Gate | Data access requests: reviewers approve them and Gate grants the access. Only if you licence it. |
| Agent Studio | Building, running and scheduling AI agents that work with Dawiso and your other systems. Only if you licence it. |
| Supporting services | Messaging, search, cache and database services. They are deployed with the platform. |
Kubernetes cluster
| Requirement | Supported |
|---|---|
| Kubernetes | A CNCF-conformant distribution, in a version within its vendor’s support period |
| Nodes | Linux, x86-64 (amd64) |
| Gateway | Envoy Gateway, with the Gateway API resources. Other ingress controllers are not supported. |
| PostgreSQL operator | CloudNativePG |
| Storage | A default StorageClass for SSD block storage (ReadWriteOnce) with volume expansion |
| Cluster policies | The policies of the Dawiso namespace let the platform’s containers run as delivered. No privileged containers, host paths or host networking are needed. The installation documentation lists the settings. |
| Exposure | A load balancer for the gateway on TCP 443 |
Sizing
The sizing covers the Dawiso namespace for up to about 260 contributors and millions of metadata objects. Your cluster add-ons, such as the gateway and the operator, need their own capacity. Where a range is given, the lower value is the minimum. Dawiso sets the size within the range for your data volume before installation. Dawiso sizes larger installations individually.
| Requirement | Supported |
|---|---|
| Compute | 8–12 vCPU and 64–96 GiB memory, on 2–3 nodes with at least 4 vCPU and 32 GiB each. One node has at least 16 GiB free for the search service. |
| Persistent storage | 300–600 GiB, of which at least 128 GiB for the search service |
Memory, not CPU, limits Dawiso. The memory that Data Ingestion needs grows with the size of the data sources it reads.
SQL Server
Dawiso’s main database runs on your SQL Server, outside the cluster.
| Requirement | Supported |
|---|---|
| Version | Microsoft SQL Server in a version within Microsoft’s mainstream support, on Windows or Linux |
| Edition | Standard or Enterprise |
| Authentication | SQL Server authentication enabled (mixed mode) |
| Installation | A login with the sysadmin role, during installation only. Dawiso then uses its own login, limited to the Dawiso database. |
| Network | Reachable from the cluster and from the installation workstation |
Managed database services, such as Azure SQL Database, Azure SQL Managed Instance or Amazon RDS, are not supported.
| Sizing | Supported |
|---|---|
| vCPU | 4–8 |
| Memory | 32–64 GB |
| Data disk (SSD) | 256–500 GB |
| Log disk (SSD) | 128 GB |
| tempdb | On a local SSD |
DNS and certificates
Dawiso uses six hostnames under your domain: Dawiso, Data Ingestion, Gate, and three for Identity (the service, its administration and your sign-in page). Agent Studio, if you licence it, adds one more. Each needs a DNS record and a TLS certificate.
- The hostnames must resolve from your users’ network and from inside the cluster, because the components call each other through them.
- The pods must trust the certificates. Use a public certificate authority, or make your private certificate authority trusted in the cluster.
- If you use Let’s Encrypt through cert-manager, open TCP 80 from the internet for the certificate checks.
Network
| Direction | From | To | Purpose |
|---|---|---|---|
| Inbound | Users | The Dawiso hostnames, TCP 443 | Using Dawiso, Gate, Agent Studio and Identity |
| Outbound (optional) | Users’ browsers | embed.diagrams.net, TCP 443 | The diagram editor in rich text fields |
| Outbound | Cluster | SQL Server | Dawiso’s main database |
| Outbound | Cluster | Your data sources | Reading metadata |
| Outbound | Cluster | The container registries below, or your mirror of them | Downloading the images, at installation and whenever a component restarts |
| Outbound (optional) | Cluster | Your AI models, such as your Azure OpenAI deployment | AI features of Dawiso Core, Agent Studio, and other platform modules and services |
| Outbound (optional) | Cluster | Your identity provider: Microsoft Entra ID (TCP 443), LDAP or LDAPS (TCP 389 or 636), Kerberos (TCP/UDP 88) | Single sign-on and user synchronisation |
| Outbound (optional) | Cluster | Your e-mail service, TCP 25 or 587 with STARTTLS. Implicit TLS on port 465 is not supported. | Password-reset e-mails and notifications |
| Outbound (optional) | Cluster | Microsoft Graph, TCP 443 | Exporting documents to OneDrive |
| Outbound (optional) | Cluster | Dawiso’s licence server | Licence verification, if you allow it. Dawiso works without it. |
The registries are:
dawiso.azurecr.io, with the access token Dawiso issues to you,docker.io,ghcr.io,cloudnative-pg.github.io, for the CloudNativePG operator chart,quay.io, only if you install cert-manager.
For metadata sources outside the cluster’s network, you can run Dawiso Integration Runtime (DIR).
Installation workstation
Docker, kubectl and Helm, with access to the cluster, to SQL Server and to the registries.
Browsers
Users work in the latest stable Microsoft Edge or Google Chrome, on Windows or macOS, with a screen resolution of at least 1024x768.
Your data
- Your data stays in your environment. Dawiso sees data only when you share it with support.
- AI features use the AI models you connect, such as your own Azure OpenAI deployment, under your own contract with the model provider.
- You back up the SQL Server database, the PostgreSQL databases and the persistent volumes. They hold the only copy of your data.
- Keep the passwords and keys generated during installation in a safe place. Without them the stored data cannot be decrypted, and Dawiso cannot restore them.
- AI assistants connect through the Dawiso MCP server only if you turn it on, and act as the user who signs in.
Updates
You install new releases yourself with Helm. The upgrade migrates the databases. A release replaced by a newer one keeps receiving security updates for at least six months.
Dawiso announces changes to this page that require you to upgrade or extend your environment in advance, as your agreement sets out.