About Codex

Codex is a portfolio intelligence dashboard. Every project Philip Rehberger has built — demos, packages, client engagements — is catalogued in one place, tagged along five axes (capability, technology, industry, architecture, deliverable), and rendered as a heatmap + gap report.

Why capability-led, not technology-led

Buyers don't hire freelancers for a stack — they hire for a job. "I need a customer portal with reporting and payments" sells better than "I need Laravel." The capability vocabulary (Authentication, Payments, Search, Reporting, Real-time, Document Generation, Multi-tenant, …) is the load-bearing layer. Technologies are how; capabilities are what.

What the heatmap is, and isn't

It's a portfolio map. Each cell means "this project carries this capability." The count next to each capability is the project count — concentration of shipped work, not a skills certification or a ranking.

Client work is redacted by client identity (RedactedScope on the Laravel side) but tagged at full fidelity. Industry stays visible because that's the proof-of-portfolio shape; the client's name is private to the engagement.

About the package representation

Philip's open-source library covers ~630 packages across PHP, TypeScript, Python, and Go. Listing each as its own row would drown the heatmap. Codex represents the package collection as cluster-per-language rows (PHP / Laravel — Feature Flags, TypeScript — Caching, Go — Resilience, …) — about 25 rows. The full list lives at philiprehberger.com/open-source-packages.

Stack

• Laravel 13 + Filament v5 + MySQL 8 (read API + admin)
• Next.js 16 + React 19 + Tailwind 4 (this dashboard)
• Apache + mod_php + PM2 (deploy)
• Sentry + BetterStack + Plausible (observability)
• All sub-$0.50/mo in cloud cost at Phase 1 traffic

Source at github.com/philiprehberger/codex.