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.
Authorization
Authorisation through central policies, not limited to roles.
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
Component licensing terms
Kauzas brings together components under different open source licences. The effect of the versions used and of the distribution method on licence terms has to be assessed separately.
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.