Context + Puppet

Puppet is the infrastructure automation platform where operations teams define the desired state of their entire infrastructure as code -- server configurations, package installations, service definitions, file permissions, and security policies. Over time, Puppet codebases accumulate a deep repository of infrastructure intelligence: why specific configuration parameters were chosen, how modules evolved to handle different operating systems and environments, which node classifications reflect production topology, and how Hiera data hierarchies encode environment-specific overrides. But this knowledge is scattered across module repositories, Hiera data files, node classifiers, and Puppet Enterprise console reports, disconnected from the Jira tickets that drove configuration changes, the Confluence runbooks documenting infrastructure standards, and the Slack channels where infrastructure decisions were debated.

Context connects to your Puppet Enterprise instance and associated code repositories to extract the organizational knowledge embedded in manifests, modules, Hiera data, node classifications, report histories, and RBAC configurations. Using permission-aware indexing that respects your Puppet Enterprise role-based access controls and node group permissions, Context builds a knowledge graph that maps relationships between modules, node configurations, infrastructure components, teams, and the broader context from your entire tool stack.

Unlike cloud-based search tools that require your infrastructure configuration data to be processed externally, Context deploys entirely on your network -- on-premise, in your VPC, or in air-gapped environments. Your Puppet manifests, node classifications, and Hiera data never leave your control. For defense contractors managing classified server fleets, aerospace companies operating safety-critical ground infrastructure, and financial institutions governing regulated server environments, infrastructure configuration data reveals system topology, security hardening decisions, and compliance posture. Context ensures this intelligence remains within your security boundary while making it searchable and actionable. Every answer is backed by citations to specific Puppet modules, node reports, or Hiera configurations, maintaining full traceability.