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

ADR 12: The build, buy, or host test

The standing framework for every new capability, and the CRM decision.

Status: adopted (2026-07-19)

Context

The same question keeps arriving with different logos on it: Sanity (CMS), Openship (deployment), Mailadept (verification), Twenty (CRM). Decide once, apply forever.

The test

For any new capability, in order:

  1. Is the problem unique to Backpack? (mapping content into legacy static markup, fleet orchestration, agent layers). Build it. This is the only thing we build.
  2. Does a complete open-source platform exist? Self-host it on our substrate, one tenant or instance per client (ADR 11), wire it into the shell (ADR 07), put our agents in front of its API. Marginal cost per client: zero.
  3. Only otherwise, or when self-host ops provably cost more than the subscription, buy the managed version. Prefer vendors whose managed product is the same software (Twenty, Postiz, Openship), so leaving is an export, not a rebuild.

Corollary: we never build record-keeping platforms (CRMs, CMSes, mail servers, schedulers). We build the layer that makes them work together and the agents that operate them.

Applied so far

Capability Decision
CMS Built (unique problem: legacy static markup)
Analytics Self-host Umami
Deployment substrate Self-host Openship (trial), Vercel for static edge
Mail Self-host (Openship/iRedMail stack), SES for bulk relay
Email verification Built layer 1; probe layer self-host later
Support inbox Self-host iese (Chatwoot fork)
Social Self-host Postiz
Bookkeeping Buy (QuickBooks); integration only
SEO data Buy (OpenSEO, $10/mo incl. usage). The metered cost is DataForSEO data, which is paid either way, so self-hosting saves nothing and adds ops. GSC data free; MCP plugs into our agents. Revisit at >$100/mo usage or white-label reporting.
CRM Self-host Twenty on ops-1; per-client workspaces; DealFlow becomes the AI layer on Twenty’s API instead of a from-scratch build

CRM notes (Twenty)

  • AGPL, Postgres + Redis, Docker Compose: a natural Openship compose deployment on ops-1.
  • Native workspaces cover per-client tenancy; its GraphQL/REST API and webhooks are the agent surface.
  • Self-host Gmail sync requires registering our own Google OAuth app (one-time verification friction). Their cloud ($9/user/mo) is the escape hatch if that or ops load ever outweighs seats saved; same software, so migration is an export.

Was this page helpful?