Skip to content
Backpack
Esc
↑↓navigate↵open⌘Jpreview
On this page

Modules

How Inbox, Social, Money, and Tasks connect.

Inbox, Social, Money, and Tasks are shell modules rendered by components/module-page.tsx. Each reads one env var; when set, the module shows connected status and an Open button. When unset, it shows exactly what to stand up. No fake dashboards, ever.

Module Env var Platform
Inbox INBOX_URL iese (Chatwoot fork) on Railway
Social SOCIAL_URL Postiz, self-hosted (cloud tiers: $29/$39/$49/$99 per month if ever needed)
Money MONEY_URL QuickBooks Online
Tasks TASKS_URL Team’s choice (Linear, ClickUp, or self-hosted)

Deepening a module means adding API integrations (counts, statuses, per-client views) behind the same page, not absorbing the platform.

Services registry (planned next)

services.json mapping client to service instances to URLs, powering per-client module views and agent-driven provisioning. The porter pattern applied to services.

Email module: Campaign Studio (repo scaffolded 2026-07-29)

Decision: fully owned campaign experience like iese, but WITHOUT forking the engine. Listmonk stays the untouched self-hosted engine (lists, delivery via SES, bounces); Backpack-Ops/campaign-studio is the product surface: reallygoodemails.com-inspired style extraction into per-client brand kits, themed MJML block library, AI-drafted campaigns (kimi-k2 via gateway), visual composer, push-to-Listmonk send flow. Full sub-agent brief lives in the repo’s AGENTS.md; architecture and brand-kit schema in docs/architecture.md. Prereq when implementation starts: create a Listmonk API user (Settings > API) for the studio. Style extraction takes tokens and patterns only, never another brand’s content or identity.

Was this page helpful?