Coverage
Works with your stack
Connect Nova to the systems your team already runs instead of replacing them.
Kubernetes
AWS
Google Cloud
Azure
Helm
Terraform
GitHub
Slack
Datadog
AI operations: from diagnosis to action
The trust layerfor AI operations
AI runs your production operations. You stay in control.
Human approvals. Policy guardrails. Audit trails. Rollback.
or start from your terminal
astroctl
$ astroctl novathe problem
Nobody standardized the platform.
Kubernetes made the primitives standard. The layer above them never was, and it now has to answer a question it was never built for: what is allowed to run.
Kubernetes made pods, services and volumes one API. That part is finished.
- 01
Kubernetes made pods, services and volumes one API. That part is finished.
- 02
The layer between those primitives and your customers was never standardized.
- 03
So every company builds it again. And then keeps building it, because day two never ends.
- 04
Standardize that layer and it stops being something you maintain.
- 05
And it becomes the one place that can decide what is allowed to run.
the platform
Your infrastructure. Your blueprint.
A standard runtime and trust layer under the platform you compose. Nova operates through it for deeper context and safer execution.
- Provision
- Compose
- Deploy
- Operate
- Upgrade
- Secure
- Account
- Govern
Create a cluster in your account, or join one you already run.
nova
An AI platform engineer that runs across every stage above, and keeps working on the systems you already run.
Astro PlatformAWSGoogle CloudAzureGitHubSlackDatadogTerraform & Helm+ any MCP server you add
the category shift
AI can diagnose. Production needs control.
AI expresses intent. The runtime decides what runs.
Read the thesis: The AI SRE race is running the wrong way
your environment
- 01
You ask, in plain language, from the browser, terminal, editor, or Slack.
- 02
Nova reads your clusters, apps, rollouts, CVEs, and spend as first-party state. It is not holding a tool that can change anything.
- 03
A scoped plan: steps sequenced, dependencies stated, approval points marked.
- 04
One approval, and the runtime is the thing that holds it, not the model.
- 05
It runs inside a scope it cannot exceed, in your own cloud account.
- 06
Every revision stays on the record, including the ones the platform made on its own.
how teams use it
Work with Nova wherever your team operates
Browser, terminal, editor, and Slack over one managed backend. Start in one, continue in another, with the same session throughout.
prompt to production · preview
Ship from your editor.
Describe what you want from Claude Code, Cursor, or VS Code. Your repository is read, a blueprint is resolved, and the deployment is written with the production settings most services only get after an incident.
›/deploy this service to dev
local → dev → staging → prod
Deploy builds for the entry environment. Promotion moves the image that was already validated rather than building a new one, and an environment will not take a release until the one before it is healthy.
read from your repository
language TypeScript · framework Next.js · port 3000 · stateful no
blueprint resolved
Server-rendered web apps with a backend. Standard infrastructure.
installs ingress · TLS certificates · DNS records
2 nodes · Deployment
written for you
Dockerfile · Helm chart · GitHub Actions
production defaults you did not have to know
liveness probereadiness proberesource requests and limitsruns as non-rootseccomp RuntimeDefaultno privilege escalationall capabilities droppedpod disruption budgetrolling update, maxUnavailable 0autoscaling (opt-in)
The difference between a service that deploys and one that survives its first bad night.
claude
$ claude mcp add astro-deploy -s project -- mcp-server-astro-deploydeploy on your terms
Keep control of your environment
Your clusters connect out, never in. Access is issued one time and never held.
Your cluster opens the connection. Nothing dials in from our side.
- 01
Your cluster opens the connection. Nothing dials in from our side.
- 02
Access is issued one time and expires. Nothing long-lived to leak, nothing to rotate by hand.
- 03
Scoped to your organization, and revocable from your cloud provider at any time.
- 04
You choose how data is handled, including local execution that keeps it inside your boundary.
Security
Credentials encrypted at rest and in transit
Role-based access control and approval-aware workflows
Audit trails for platform operations
Organization-scoped access: operators see only their environment
Scoped cloud access, revocable at any time from your cloud provider
How it works
- 1Connect AstroPulse to your cloud account with scoped access
- 2Operate through Nova, the Astro Platform console, or CLI
- 3Keep operational data in your environment when using local model execution
- 4Revoke access or change policy boundaries at any time
pricing
Start free. Expand for teams
Every plan includes Nova and Astro Platform, with governance and execution limits by plan.
Individual
Developer
For individual developers exploring Nova and connected workflows.
$0/month
Nova access
Get started quickly
No credit card required
Free · Fast start · No card
Enterprise
Enterprise
For teams that need production operations and enterprise rollout support.
Custom
Deployment guidance
Enterprise controls
Commercial support
Controls · Support · Rollout
Start with Nova
Start running production with Nova
Connect the systems you already use and expand into deeper operational control when the team is ready.