orkivaKUBERNETES CONSOLE Discuss an evaluation ↗

SECURITY & DATA OWNERSHIP

Orkiva security and data ownership.

Orkiva runs on infrastructure you control. Understand what the installation stores, which connections you enable and what your team remains responsible for.

Where data lives

Installation settings, users and cluster connection records are stored in the database configured for your Orkiva installation. Delivery artifacts use the configured local or object storage.

Your team manages access, retention and backups for that infrastructure. Storage and database encryption at rest depend on your deployment configuration.

How credentials are protected

Selected sensitive database fields, including stored kubeconfig content and configured AI API keys, are encrypted before persistence. This does not mean every database field or backup is encrypted.

Protect the installation encryption key separately from database backups, restrict access to it and plan key recovery alongside your restore process.

Who can perform operations

Authentication, Orkiva roles and Kubernetes permissions govern access. Configure identities and permissions around the operations each team member needs.

Audit records help investigate activity. Configure retention and access to those records as part of your operating routine.

Which services receive data

Cluster operations connect to your configured Kubernetes environments. GitOps, chart repositories, registries and identity providers connect to their configured services when used.

When AI features are enabled, requests can send prompts and relevant conversation or tool context to the configured inference provider. Review provider settings and data policies before enabling them for sensitive workloads.

Analytics and diagnostics

Product web analytics are disabled by default. Enabling the product analytics setting loads an external Umami analytics script. Optional tracing sends diagnostic spans to the configured collector when enabled.

The public marketing and documentation websites separately include Vercel Web Analytics. Website analytics are distinct from the customer-hosted console.

What your team controls

Configure HTTPS, network access, storage, database credentials and cluster permissions. Keep the host environment patched, restrict administrative access and test backup restoration and upgrades.

Confirm the security settings and supported configuration for the exact software package you will receive.