CONSTELLATION / KUBERNETES SECURITY EARLY ALPHA

Know your clusters. Prove it.

Constellation is a Kubernetes-native security platform. See what is running, know what is exposed, control what is allowed and prove what happened, from one console installed in your own clusters.

Constellation is in early alpha and not production-ready. Interfaces can change without notice. We are looking for teams who will evaluate it in a lab and tell us what they find. Screens are from an AlphaBravo test environment.

+ RUNS IN YOUR CLUSTERS+ OBSERVE FIRST, ENFORCE BY CHOICE+ EVERY CHANGE AUDITED
CLUSTER / DASHBOARDCONSTELLATION
Cluster dashboard: A cluster’s risk score, open and accepted findings, image and host CVEs, fixable-now counts, privileged and root workloads, exposed services and top network denies.Cluster dashboard: A cluster’s risk score, open and accepted findings, image and host CVEs, fixable-now counts, privileged and root workloads, exposed services and top network denies.
A cluster’s risk score, open and accepted findings, image and host CVEs, fixable-now counts, privileged and root workloads, exposed services and top network denies.

FROM IMAGE TO EVIDENCE

Follow one workload through Constellation.#

Select a stage. Each shows the console screen and the specifics behind it, including what is on by default and what you have to turn on.

01 / INVENTORY

Find it

Start from what is actually deployed. The discoverer records each cluster’s workloads, images, nodes and platform, and the dashboard rolls them up into a risk score and the counts that need action.

  • Workloads linked to the images they run.
  • Privileged, root and host-network workloads called out.
  • Every registered cluster in one console.
Constellation screen for Find itConstellation screen for Find it

IN PRACTICE

Built for the people who answer for the cluster.#

Security, platform and audit teams look at the same findings, the same policies and the same record.

01 / CORRELATE

CVEs with a blast radius

A CVE page lists the images, deployments and clusters it touches, with EPSS and fix advice, so the question is “which workloads” rather than “how many CVEs”.

Prioritization
02 / REHEARSE

Simulate before you enforce

Run a manifest or a live resource through admission rules without changing anything. Keep rules in monitor mode until the warnings are what you expect.

Simulation
03 / LEARN

Baselines, not guesswork

Each workload learns its normal processes. Freeze the baseline to alert on drift, then enforce it for the workloads that are ready.

Baselines
04 / SEGMENT

Policy from observed traffic

Candidate network policies come from the flows Constellation saw. Approve, apply, demote and roll back, with every step audited.

Policy lifecycle
05 / ACCOUNT

Exceptions that expire

Accepting a risk or exempting a control needs a reason and an end date, and leaves a record in a hash-chained audit log.

Exemptions
06 / RESTRICT

Works without the internet

Scanners run from pre-loaded databases or internal mirrors, and the KEV and EPSS feeds can point at your own copies.

Offline scanning

WORKS WITH ASTRONOMER

Astronomer runs the fleet. Constellation secures it.#

Constellation is a curated application in Astronomer’s catalog. Install it on the clusters Astronomer manages through its GitOps path, with admission policies that stay strict for tenant namespaces.

Constellation + Astronomer
ASTRONOMER / CATALOG / INSTALL CONSTELLATIONASTRONOMER
Install Constellation from Astronomer: Astronomer’s catalog install form for Constellation, with its curated settings and the recommended astronomer-constellation namespace. Captured in the Astronomer console.Install Constellation from Astronomer: Astronomer’s catalog install form for Constellation, with its curated settings and the recommended astronomer-constellation namespace. Captured in the Astronomer console.
Astronomer’s catalog install form for Constellation, with its curated settings and the recommended astronomer-constellation namespace. Captured in the Astronomer console.

STRAIGHT ANSWERS

Questions evaluators ask first.#

Is Constellation ready for production?

No. It is in early alpha: APIs and data formats can change without notice, and there are no stability, security or support guarantees. Evaluate it on non-production clusters and tell us what you find. #

Where does it run?

In your own Kubernetes cluster, installed with a Helm chart. It needs Kubernetes 1.27 or later and stores its data in PostgreSQL, bundled or your own. A Docker Compose demo is available for a first look at the console. #

Will installing it break our workloads?

The runtime agent only detects and alerts by default, and no network policy is applied until someone approves it. The admission webhook does reject privileged, host-network and host-PID pods by default outside its own namespace, so exempt the system namespaces you trust first. It fails open if it is unavailable. #

Does it certify compliance?

No. Constellation maps its checks to framework controls and keeps the evidence and audit trail. A mapped check supports a control; it does not certify a cluster. #

Do we need Astronomer?

No. Constellation runs on its own. If you already use Astronomer, you can install Constellation from its catalog. #

See status and known limits

NEXT STEP

See Constellation with your environment in mind.

Tell AlphaBravo what you run today. We will show you the workflows that matter to your team.

Find your next step

12 pages

Tab through results · Enter to open · Escape to close