System requirements for PanDev Metrics on-prem
PanDev Metrics on-prem ships as a self-contained stack — backend, workspace, and PostgreSQL 16 — that you run from the distribution archive with Docker Compose or the bundled Helm chart. By default everything runs on a single host; for larger installs you can move the database to a dedicated host or a managed service. This page lists the hardware, supported operating systems, the CPU-instruction baseline, and required software versions.
At a glance
| Property | Value |
|---|---|
| Topology | Single host by default (database bundled); external/managed database optional |
| Deployment options | Docker Compose or Kubernetes 1.28+ |
| OS family | Linux — x86_64 or arm64 |
| Database | PostgreSQL 16 (bundled); 17 also supported |
| Backend API port | 8080 |
| Workspace UI port | 8090 |
| Actuator port (internal) | 9090 |
Hardware
The shipped Docker Compose stack runs the backend, the workspace, and PostgreSQL on one host, so provision for the combined load. The two profiles below let you size the application and the database separately — useful when you split the database onto its own host or a managed instance for production.
Application components (server + workspace)
| Component | Minimum | Recommended |
|---|---|---|
| CPU | 4 cores | 8 cores |
| RAM | 8 GB | 16 GB |
| Disk | 30 GB | 50 GB SSD |
PostgreSQL
| Component | Minimum | Recommended |
|---|---|---|
| CPU | 8 cores | 16 cores |
| RAM | 12 GB | 24 GB |
| Disk | 50 GB | 100 GB SSD |
Disk growth scales with the number of engineers, integrations, and retention. Plan for additional capacity if you connect Jira, multiple Git providers, and large IDE plugin populations.
CPU and architecture
The backend is published as a GraalVM native image, compiled ahead of time for a specific CPU architecture. This is why the distribution ships two image variants — pick the one that matches your host:
| Architecture | Image tag | Notes |
|---|---|---|
| x86_64 / amd64 | default (e.g. :5.8.0) | Requires the instruction baseline below |
| arm64 | -arm suffix (e.g. :5.8.0-arm) | Native arm64 build, including Apple Silicon |
On x86_64, the native backend requires a modern instruction baseline. The host CPU (and any virtualization layer in front of it) must expose:
CX8, CMOV, FXSR, MMX, SSE, SSE2, SSE3, SSSE3,
SSE4_1, SSE4_2, POPCNT, LZCNT, AVX, AVX2, BMI1, BMI2, FMA
Verify on a candidate x86_64 host:
lscpu | grep -E "avx|avx2|fma|sse4"
If these instructions are missing — typically because a hypervisor masks them — the native backend aborts at startup with Illegal instruction. On arm64 hosts, use the -arm image tags; the x86_64 instruction list above does not apply.
Virtualization settings
If the x86_64 backend fails to start on a virtual machine, the hypervisor is most likely masking required CPU instructions from the GraalVM native image. Pass the host CPU through to the guest using the setting for your platform.
| Platform | Setting |
|---|---|
| Proxmox VE | cpu: host in VM config |
| VMware ESXi | VM compatibility 7.0+, CPU passthrough |
| VirtualBox | Enable VT-x, Nested VT-x, PAE/NX. Run VBoxManage modifyvm "VM" --cpu-profile host |
| Hyper-V | VM generation 2, disable CPU compatibility mode |
| XCP-ng / XenServer | CPU mode host-passthrough |
| QEMU / KVM | -cpu host or explicit flags +avx2,+fma,+bmi2 |
Operating system
PanDev Metrics on-prem runs on any current Linux distribution that ships a supported Docker Engine.
| Distribution | Tested versions |
|---|---|
| Ubuntu Server | 22.04 LTS, 24.04 LTS |
| Debian | 11 (bullseye), 12 (bookworm) |
| RHEL / Rocky / AlmaLinux | 8, 9 |
| SUSE Linux Enterprise Server | 15 SP4+ |
Other Linux distributions that meet the kernel and Docker requirements also work, on both x86_64 and arm64. Windows Server is not supported.
Software
| Component | Required |
|---|---|
| PostgreSQL | 16 (bundled); 17 also supported |
| Docker Engine | ≥ 20.10 |
| Docker Compose | ≥ v2.0 (v2.20+ recommended) |
| Kubernetes | ≥ 1.28 (Helm path) |
| Helm | 3.x (Helm path) |
PostgreSQL 16 ships inside the distribution, so you do not install it yourself unless you choose an external database. The backend is compatible with both PostgreSQL 16 and 17 — use 17 if your external or managed database runs that version. An external cache (such as Redis) is not part of the distribution and not required — the backend caches sessions and rate-limit counters in-memory.
Network
Inbound and outbound network requirements are documented separately in Network and ports. Summary:
- Public inbound on 8080 (backend API) and 8090 (workspace UI) — or behind a reverse proxy on 443
- Internal inbound on 9090 for the actuator (health and metrics)
- PostgreSQL on 5432 — published to the host by the bundled Compose file; bind it to localhost or firewall it off for non-local installs
- Outbound HTTPS to your configured Git provider and task tracker (egress is minimal and cannot be disabled)
Browser support
The PanDev Metrics frontend is a modern single-page React application. Recent versions of Chrome, Edge, Firefox, and Safari are supported. The team targets the latest two major releases of each browser.
Constraints and edge cases
- Single organization per installation. On-prem does not support multi-tenant separation. One install equals one organization.
- No air-gapped deployment. Minimal outbound network access is required for integrations.
- Horizontal scaling of the backend is not part of the on-prem distribution. Run a single backend instance per installation; vertical scaling via larger hosts is the supported path.
Related
- How-to: Install PanDev Metrics on-prem
- Reference: Network and ports
- Concept: On-prem architecture