Unmanaged Private Cloud

In the Private Cloud offering, “unmanaged” means that Jedox Cloud Operations will not directly manage the infrastructure where the Jedox Platform is deployed. Instead, it is the responsibility of the customer to manage and maintain the underlying infrastructure, including the Kubernetes cluster and associated resources. Jedox will provide the necessary software components, such as the Helm Chart for deployment, but customers are required to handle the operational aspects of their infrastructure.

In the Unmanaged Private Cloud offering, the customer is responsible for tasks such as provisioning and scaling the Kubernetes cluster, ensuring high availability and disaster recovery measures, applying security patches, monitoring performance, and troubleshooting infrastructure-related issues.

Jedox will provide support related to the deployment of the Jedox platform within the customer’s Kubernetes cluster. This support typically includes assistance with the installation, configuration, and troubleshooting of the Jedox software. Customers should be aware that Jedox will not provide ongoing infrastructure management or maintenance. For such tasks, customers are expected to have their own technical resources, or partner with a managed service provider.

In the Unmanaged Private Cloud offering, Jedox Cloud Operations will not have direct access to your data or network. Jedox will provide the necessary software components, but the data resides within the customer’s infrastructure and is not accessible by Jedox Cloud Operations. The Jedox team does not have visibility into your data or network configuration. This is done on a best-effort basis.

We monitor the status and performance of services comprising the Jedox Application. Patches are applied automatically. New releases are communicated to the customer in advance. When the customer requests not to upgrade, Jedox puts the customer on a hold list.

Jedox is committed to continuously updating the Helm Chart with the latest Jedox version, ensuring customers have access to the most recent features, enhancements, and bug fixes. The frequency of these updates may vary based on the Jedox’ release schedule and the introduction of new versions. Customers should regularly check for updates or subscribe to notifications from Jedox to stay informed about the availability of new Helm Chart releases.

Yes, the Unmanaged Private Cloud offering is designed to be flexible and customizable. You can integrate Jedox seamlessly with your existing infrastructure, data sources, and services. The Helm Chart allows you to adjust settings to meet your specific requirements and integration needs.

While the Unmanaged Private Cloud offering provides flexibility and control, it requires technical expertise to manage the Kubernetes cluster and associated infrastructure. Customers should consider their team’s capabilities, infrastructure readiness, and ongoing maintenance requirements before opting for this offering. Additionally, customers are responsible for ensuring compliance with relevant data protection regulations and implementing best practices for securing their infrastructure and data.

Secure development: Jedox adheres to the principles of secure software development and testing along the Secure Development Lifecycle (SDLC) in all Jedox internal software development procedures.

Security patches: Jedox continuously deploys security patches overnight (local time). Thus, there is no downtime for customers and no need to schedule a maintenance window during which work on the Jedox Platform must be halted.

Jedox has partnered with HackerOne for a continuous bug bounty program. Throughout the year, potential weak spots are identified by selected security experts from a group of global “white hat hackers”. These weak spots are triaged and quality tested, and this information is shared with Jedox internal teams. Through this practice, Jedox has implemented an additional layer of quality assurance, guaranteeing the best practices in data security to protect customer data. Besides actively searching for vulnerabilities, the Jedox development pipeline implements various other security tools and methods, such as Trivy and Static Code Analysis.

Jedox does not deploy or operate a centralized logging or monitoring stack in an Unmanaged Private Cloud installation. Responsibility for observability lies entirely with the customer.

The table below outlines vendor-neutral best practices you may follow. The tools listed are examples, feel free to use any solution that meets your needs.

Jedox doesn’t include a built-in backup mechanism for Unmanaged Private Cloud deployments. Protecting your data and ensuring its recoverability is your responsibility.

The following Stop - Snapshot - Start process provides a solid foundation and can be scripted or integrated with automation tools such as Ansible, GitHub Actions, or your preferred scheduler.

Minimal procedure for the NFS‑based storage:

1. Stop all Jedox workloads

   Copy

   kubectl scale deployment --all --replicas=0 -n <namespace>
   kubectl scale statefulset --all --replicas=0 -n <namespace>

   Confirm every pod is terminated before continuing.

2. Snapshot the storage

   Use your NFS array’s native snapshot to capture the Jedox data volume.

3. Start the services

   Copy

   kubectl scale deployment --all --replicas=1 -n <namespace>
   kubectl scale statefulset --all --replicas=1 -n <namespace>

   Verify that all pods return to a Running state.

Recommended sizing guidelines:

These values are intended as baseline recommendations. You may need to scale resources based on actual load, concurrent users, and data growth over time.

To ensure stable performance, particularly during simultaneous ETL operations or high-frequency read/write workloads, use SSD-backed storage with sufficient IOPS throughput and low latency. Avoid HDDs or any other storage class with limited I/O performance, especially in production scenarios where responsiveness and consistency are critical.