Server + VM inventory
Bare-metal + XCP-ng VMs, registered, monitored, agent-aware. SSH operations from the dashboard.
NIP Platform is a Kubernetes-native private cloud management platform: register servers, run VMs on XCP-ng, ship deployments, monitor health and manage security posture — from one AI-assisted dashboard, self-hosted or managed.
A private cloud management platform is more than a XenServer/XCP-ng console: it bundles server inventory, VM lifecycle, container deployments, monitoring, backup and security posture under a single, role-aware control plane.
NIP Platform is built Kubernetes-native and AI-first. The platform itself runs on a small K8s cluster; your servers, VMs and apps are managed via SSH + APIs from one dashboard.
Bare-metal + XCP-ng VMs, registered, monitored, agent-aware. SSH operations from the dashboard.
Zero-downtime deploys with rollback. GitHub / GitLab webhooks. Per-site lock + audit.
Auto-provisioned protections, weighted score (NONE → MAXIMUM), 10 protection categories.
Natural-language ops: "show me the failing pods on prod" → audited tool call, role-checked.
A single K8s cluster runs NIP. Helm chart or NIP-managed.
Bare-metal + XCP-ng hosts registered via SSH key. Agent-based heartbeat.
Apps + sites onboarded to deploy pipelines. Per-tenant isolation.
Auto-provisioned protections (firewall, backup, TLS, monitoring, IAM).
A hypervisor console manages one cluster of VMs. NIP Platform manages the entire stack: bare-metal hosts, VMs, K8s pods, CI/CD, monitoring, backups and security posture — across multiple sites, tenants and clouds.
Yes. NIP is shipped as a Helm chart that runs on any Kubernetes cluster (k3s, RKE2, EKS, AKS, on-prem). Air-gapped deployments supported.
Yes — first-class XCP-ng support: VM lifecycle, snapshot, clone, live migration, template management. See the XCP-ng landing page.
Built-in zero-downtime deploys with rollback. GitHub Actions / GitLab CI webhooks land here; the platform locks per-site, runs healthchecks and rolls forward or back.
30-minute walkthrough on a sample cluster, architecture review, rollout plan at the end.