No. Alpha works with Kubernetes when it is already in place, but it is designed to manage workloads running directly on the OS, in VMs, or via Docker without introducing Kubernetes.

Each site runs an autonomous agent that continuously reconciles the local system to its target state, even when fully offline. Connectivity is only required to receive updates, not to operate safely.

Alpha manages application workloads, native services, OS configuration, and their cloud dependencies as a single system. Observability and health are assessed across all these layers.

Alpha enforces a known target state through continuous reconciliation instead of one-time, push-based execution. Unlike cloud extensions, it is designed to operate autonomously without assuming permanent connectivity.

All definitions rely on open standards and can be exported into standard manifests and configuration files. If you leave Alpha, you keep your infrastructure definitions and workloads.

Yes. Alpha integrates with existing Kubernetes resources, cloud services, and observability pipelines via standard APIs and OpenTelemetry, without requiring changes to your current tooling.

Blueprints encode security policies, disaster recovery plans, and incident detection as reconciled infrastructure — not documentation. Drift from your compliance baseline is detected and corrected continuously. Audit reports are generated from live state, so you always have evidence of your security posture.

Alpha is European-headquartered with no CLOUD Act exposure. Built on open standards: Kubernetes, and OpenTelemetry. The alphactl blueprint eject command exports standard manifests at any time — your infrastructure definitions are never locked in.