How We Built ZCP: Proxmox, Ceph, and CloudStack
A look inside ZCP's infrastructure stack. Why we chose open-source components, how they fit together, and what it means for reliability and performance.
Blog
Product announcements, engineering posts, tutorials, and stories from a Canadian-owned cloud platform.
A look inside ZCP's infrastructure stack. Why we chose open-source components, how they fit together, and what it means for reliability and performance.
Data residency, pricing transparency, and accountability. The case for Canadian cloud infrastructure owned and operated in Canada.
We ran OPNsense as a VM on network-defined storage and watched a single switch fault cascade into a cluster-wide outage. Two lessons we will not relearn: put your firewall on bare metal, and if you must virtualize it, keep the disk local.
CloudWatch gives you metrics. It does not give you actionable dashboards, historical trends, or alerts. We built a four-container open source stack that turns raw AWS data into full observability — no agents on app servers, no licensing costs, auto-discovery via AWS tags.
We picked SigNoz for its OpenTelemetry-native approach. A few months in, we moved to Prometheus, Loki, Alertmanager, and Grafana, with Grafana Alloy as the single collection agent. Here is the honest breakdown.
We ran our Tailscale subnet router as an LXC container on the same Proxmox host it was providing remote access to. It worked. Until Proxmox needed attention. Here is how we fixed it.