Podman is a container engine that runs OCI containers without a central root-owned daemon: containers run as ordinary user processes, rootless by default, with a CLI that's drop-in familiar to anyone who knows Docker. That security posture matters most exactly where we use containers — sandboxing services and agent workloads on shared development machines — and pods give it a natural on-ramp to Kubernetes shapes when needed.
How We Use It
- Rootless containers for services on shared development VMs
- Docker-compatible workflows without a privileged daemon
- Local pods that mirror Kubernetes deployment shapes
Backend & Runtime
Why this matters: Choosing the right runtime and hosting improves reliability, security, and developer velocity from day one. We choose runtimes and hosting that balance security, developer experience, and performance. Our defaults favor fast iteration locally and reliability in production, with growing adoption of secure-by-default platforms. Preferred defaults: Bun for local dev, Node.js for production, Vercel for hosting and edge.