A short path from code to production
DeploymentsTLS & DNSCost
Kubernetes standardized the primitives. Nobody standardized the platform.
Compose it from shared capabilities. Run it in your own account.
Provision new clusters or register the ones you already run; deploy applications and add capabilities as your blueprint grows. Governance is built in — approvals, audit trails, rollback.
start with a cluster you already run
$ astroctl infra k8s register --name my-cluster
how it works
Four steps, one console.
clusters
Create EKS, GKE, AKS, or self-hosted clusters in your account — the UI wizard generates your cluster.yaml, no manual authoring. Or register a cluster that already exists and get the same view everywhere.
EKS · GKE · AKS · Self-hosted · Any existing cluster
applications
Ship from container images, YAML, Helm charts, or private repositories. Logs, events, history, and status live next to the deploy — same tabs, one place, not another tool.
Images · YAML · Helm · Repositories
governance
Every operation streams progress as it runs, and every revision stays on the record — including the ones the platform made on its own. Cluster access is issued as one-time credentials: nothing long-lived to leak, nothing to rotate by hand.
Progress streaming · Revision history · One-time credentials · Notifications
cost & security
Two add-ons, installed once per cluster. Both report against what is actually running.
Spend per cluster and per application, next to the capacity paid for and requested by nothing. Missing hours are shown as missing — never as $0.
Findings grouped by image, because the image is the thing you upgrade. A workload nobody scanned is shown as unscanned — never as clean.
compose
Pick capabilities; the platform installs them and keeps them healthy.
Every company's platform should be different. What shouldn't differ is the machinery underneath it — so that stays standard, and the blueprint stays yours.
a cluster you already run joins with one command
$ astroctl infra k8s register --name my-clustera capability is one more
$ astroctl infra k8s addons apply -f nginx-ingress.yamlwhere it runs
Clusters connect out, never in. Kubectl credentials are issued one-time, never held.
Every customer creates a different blueprint
Teams compose the blueprint. Nova works across its entire lifecycle through Astro Platform's governed runtime.
A short path from code to production
Private infrastructure with governed change
Inference or training with workload-specific automation
All Nova actions pass through this trust layer.
nova
Your clusters, cost, and rollout state — in context, and every action through your policy and audit trail.
the operator is one command too
$ astroctl novaA standard runtime and trust layer under the platform you compose. Nova operates through it for deeper context and safer execution.
Read: Kubernetes standardized the primitives. Nobody standardized the platform.