stackrox

What the platform covers

The StackRox Kubernetes Security Platform performs risk analysis of the container environment, delivers visibility and runtime alerts, and gives recommendations to improve security by hardening the environment. The README states it integrates with every stage of the container lifecycle: build, deploy, and runtime. That breadth is the core pitch, because a control that only checks images at build time misses a pod that drifts at runtime, and a control that only watches runtime cannot stop a bad image from being admitted. By covering all three stages, StackRox aims to catch issues where they appear rather than in a single narrow window. The README also notes the product was built on the foundation of a tool formerly known as Prevent, which itself was called Mitigate and Apollo, so older names may appear in code or docs. For an operator, the practical effect is a single place to see what is running, what is wrong, and what to change. The platform is written in Go and is released under the Apache 2.0 license. The build, deploy, and runtime coverage is what lets a security team move from scattered point tools to one policy surface, and the README's frank note about former product names helps a reader who meets those names in the codebase understand they refer to the same lineage rather than a separate dependency.

Installing into a cluster

Deployment is done through Helm, the Operator, or scripts, and the README walks through each. For Helm, the user adds the stackrox/helm-charts/opensource repository and installs stackrox-central-services, which brings up Central and Scanner. The install needs an admin password, generated with openssl in the example, and a single instance of central-services is enough even when multiple clusters are protected. The README gives a default command for reasonably sized clusters and a reduced resource command for single node or resource limited clusters, with the caveat that the smaller settings are not for production. It also documents Kubernetes distributions such as EKS, AKS, GKE, OpenShift, and local options like Docker Desktop, Colima, or minikube, so the install path matches the environment a team already runs. After installation, the StackRox UI is reached through the central-services endpoint, and the Scanner component checks images. The variety of install routes is meant to fit both a quick local test and a managed production cluster. The reduced resource command is a practical concession to developers who want to try StackRox on a laptop, while the note that it is not production grade keeps expectations honest. Documenting EKS, AKS, GKE, and OpenShift in one place saves an operator from hunting through separate guides for each cloud they might use.

Community and development

The project keeps a community presence on the Cloud Native Slack in the #stackrox channel and points to a community hub at stackrox.io for events, blogs, and resources. For contributors, the README has a development section with a quickstart that covers build tooling, cloning the repository, local development, common Makefile targets, and productivity setup, including GoLand configuration and running sql_integration tests. A debugging subsection and a portable installer generation section round out the contributor guidance. The README also lists a table of contents that maps the install options to specific Kubernetes distributions, which helps a new operator jump to the right commands. Because StackRox is open source under Apache 2.0, the full source is available to read, modify, and self host. The combination of documented install paths, a public community channel, and a development quickstart is what lets a team move from reading about the platform to running it in their own cluster without a sales conversation. The sql_integration tests and the Makefile targets show the project expects contributors to actually run the code locally, and the portable installer section indicates the maintainers care about reproducible deployment artifacts rather than only a happy path that works on their own machines.

Editorial conclusion

The platform is released under the Apache 2.0 license, written in Go, and developed at github.com/stackrox/stackrox.