# IaaS FAQ

Your data resides entirely in Switzerland. Our data centre is located in Basel and is fully managed by Phoeniqs, with no third-party operator handling your infrastructure. Backups are held separately at Mount10, a high-security facility in the Swiss Alps. This keeps both your live workloads and your backup copies under Swiss jurisdiction at all times, which is a key requirement for organisations bound by data-residency and sovereignty mandates.

The Phoeniqs Portal displays and bills memory and storage in GB. The capacity you actually receive is the same number in GiB. If you purchase 10 GB, you are allocated 10 GiB. Because 1 GiB is larger than 1 GB, the delivered capacity is slightly greater than the GB figure suggests, never less.

Isolation happens at the Namespace level. A Namespace is a governed slice of a Capacity Pool with its own resource quotas and access controls, so multiple teams or environments can share the same pool while staying separated through ResourceQuota limits and RBAC policies. A common pattern is one Capacity Pool with separate dev, staging, and production Namespaces. If you need stronger separation than shared-cluster multi-tenancy provides, a dedicated Hosted Cluster is the alternative.

The current offerings are NVIDIA H100 (80GB) and H200 (141GB), purchased as subscriptions and assigned to a Capacity Pool like any other resource. GPUs are allocated as whole units and are not shareable across Namespaces: unlike CPU, a GPU assigned to one workload cannot be partially consumed by another. This matters for capacity planning, since you cannot oversubscribe a single GPU the way you might with compute. They are used for AI inference and other accelerated workloads.

Run in a Namespace when you want workloads on Phoeniqs' shared, managed clusters with quota and access controls handling separation. Choose a Hosted Cluster when you need a dedicated OpenShift cluster with full administrative access and your own control plane, while Phoeniqs manages the underlying control-plane infrastructure. A Hosted Cluster gives you a dedicated etcd, API server, and scheduler, worker nodes sized to your needs, a stable cluster API hostname, and Ceph-backed storage. The trade-off is the added control-plane fee versus the lighter-weight, lower-cost Namespace model.

In-region failover between availability zones is included at no extra cost. Multi-region disaster recovery (geographically distinct) is available for an additional cost.

High availability (HA) requires parallel, dedicated resources, billed at the same rate as primary workloads. Architecture and HA planning (for example, active/active) can be delivered as a consulting engagement at CHF 1,500/day, depending on complexity.

Target availability is 99.9%. Support is available during European business hours as standard, with optional 24×7 global support. See Support for plan details and response times.

Yes. Backups can be archived to out-of-region object storage hosted by Mount10 to support long-term retention and geographic isolation for disaster recovery.

Yes. Phoeniqs can assist with backup architecture and provide the required infrastructure. More complex scenarios are supported via consulting at CHF 1,500/day.

Flux Status is a web UI for the GitOps engine that runs your workloads. Phoeniqs clusters reconcile your deployments from a Git source, and Flux Status shows you what is currently running, what is failing, and the error behind each failure, in real time. See Monitor GitOps State for full documentation.

Each cluster has its own URL: flux.basel.phoeniqs.com for Basel, and flux.ai-3.phoeniqs.com for AI-3. Log in with your Phoeniqs SSO credentials. You will only see the namespaces your account has been granted access to.