Welcome to In a Box Tools
Why the In a Box family exists and how its twelve open-source infrastructure projects fit together.
After twenty-five years in infrastructure, I have seen the same story play out hundreds of times: capable teams spending weeks connecting observability and security tools before those tools answer one useful question.
The answer is not another opaque platform. It is a better starting point.
Updated July 2026: the family has grown from five projects to twelve. This post now reflects the complete suite.
What In a Box means
In a Box Tools is a family of inspectable, self-hosted infrastructure blueprints. Each project starts with an operational question, packages proven open-source components, and keeps the configuration and trade-offs visible.
The goal is not “zero complexity.” Infrastructure does not work that way. The goal is visible complexity with useful defaults: something an engineer can deploy, inspect, change, and still understand when it fails.
The complete family
Context and operations
- AIB — Assets in a Box turns infrastructure configuration into a dependency graph for blast radius, drift, and security analysis.
- OIB — Observability in a Box packages metrics, logs, traces, profiles, dashboards, and working examples.
- DIB — Database in a Box provides five database engines, six web interfaces, monitoring, backup and restore, migrations, and sample data.
Detection and response
- SIB — SIEM in a Box uses Falco runtime signals, routed alerts, searchable events, and security dashboards.
- SIB-K8s — SIEM in a Box for Kubernetes brings the runtime-detection stack to Kubernetes through Helm.
- NIB — NIDS in a Box combines Suricata network inspection, CrowdSec behavioral detection, dashboards, and deliberate blocking modes.
Posture and prioritization
- VIB — Vulnerability in a Box discovers and scans running container images while retaining vulnerability history.
- TIB — Threat Intelligence in a Box correlates those findings with CISA KEV and EPSS to prioritize exploitation risk.
- CIB — Compliance in a Box checks container runtime policy, SBOM licenses, and operating-system end-of-life status.
Trust and access
- IIB — Identity in a Box packages Authentik with generated secrets, health metrics, and an operational dashboard.
- PIB — PKI in a Box packages step-ca, ACME support, trust bootstrap, certificate probing, and expiry monitoring.
Unified suite
- Security Posture in a Box (XIB) composes VIB, TIB, CIB, IIB, and PIB with pinned submodules and a unified Grafana security-posture view.
Every project remains independently deployable. XIB unifies the decision surface; it does not flatten five security domains into a fake single database.
The principles
- Outcomes first — begin with the question, not the container list.
- Opinionated, not opaque — provide useful defaults without hiding how the system works.
- Local by default — keep telemetry, findings, identities, and asset data under the operator’s control.
- Honest boundaries — a blueprint reduces integration toil; it does not replace backups, capacity planning, threat modeling, or responders.
- Open source — inspect it, fork it, run one project, or combine several.
Browse the complete toolkit or inspect every repository on GitHub.