System architecture

Keenpix is a pnpm and Turborepo monorepo with a deliberate split between deployable applications and reusable packages.

Internet / CDN
      │
      ├── dashboard and management API ──▶ apps/app ──▶ Postgres
      │                                      │
      │                                      └── BullMQ ──▶ Dragonfly
      │                                                        │
      ├── /img/* and custom domains ──▶ apps/transform ◀──── apps/worker
      │                                      │
      │                                      ├── memory → Dragonfly → R2/MaxIO
      │                                      ├── ClickHouse analytics (optional)
      │                                      └── customer image origins
      │
      └── documentation ──▶ apps/docs

The transform runtime is separate because image decoding is CPU- and memory-heavy and scales differently from dashboard traffic. The pure image behavior stays in packages/transform, so HTTP ownership does not duplicate transformation logic.

Design rules

• apps/* are independently deployable runtimes with their own lifecycle and health checks.
• packages/* are flat capability boundaries. Only framework integrations are nested under packages/frameworks/*.
• @keenpix/core owns URL, loader, and responsive-image behavior. Every framework adapter extends it.
• The app follows route → function → action → data-access; only data-access talks directly to Postgres.
• Queue data and transformed-image cache data use separate configuration and eviction policies.
• Node runtimes log through packages/logger, backed by evlog.

Continue with services, package boundaries, and queues, cache, and analytics.