First met in aicp-c3-session-14 · Productivity & source apps · Backend, hosting & code
Containerized app runtimes: package a service (like Postgres) with everything it needs and run it identically anywhere.
A build needs real backing services locally (databases, queues) — the enterprise-grade default the course's plans reach for.
The reason 'enterprise-grade' prompts pull in Postgres locally
Isolates dependencies so installs don't pollute your machine
Runs databases and services in containers for local dev
Ships identical environments across machines
Doesn't come free on laptop resources — the s14 trainer skipped it live ('it would crash my computer for a minute')
The step between single-file demos and production backends.
Productivity & source apps · Backend, hosting & code
KB pipeline is static; no service dependencies.
current
supabase: hosted Postgres vs run-your-own
| Session | Coverage | Moment | What happened |
|---|---|---|---|
| Bonus + Demo Day: Self-Hosting n8n with Docker (Cloud vs Local Decision, the n8n_data Volume, Credentials, ngrok) and How the Hackathon Was Judged | demonstrated | Docker Desktop + Docker Hub image; volumes; containers as sandboxes | |
| Session 14: Claude Code — Advanced Workflows | explained | 1:55:46 | Chosen by the plan for enterprise-grade Postgres; skipped live to protect the demo laptop |
| Session 29: Build Always-On Assistants — Autonomy Is Designed, Not Switched On (OpenClaw on a VPS, Hermes on the Desktop) | explained | Defined for the cohort as a container - 'a jail for your agent' - not a deployment tool. | |
| Office Hours XII: Building Paul's Second Brain — the Full Project-Management System, Live | mentioned | 0:35 | Workspace self-host path, delegated to the agent |
| AI Sprint: Vibe Coding to Production — Day 1 (Deployment, DNS, and the Five Locks) | mentioned | Explicitly NOT needed for MVPs — with Kubernetes, deferred to money-in-pocket scale |